Index: openacs-4/packages/acs-core-docs/www/permissions.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions.html,v
diff -u -r1.53.2.8 -r1.53.2.9
--- openacs-4/packages/acs-core-docs/www/permissions.html 13 Jul 2023 12:43:22 -0000 1.53.2.8
+++ openacs-4/packages/acs-core-docs/www/permissions.html 1 Aug 2024 08:03:41 -0000 1.53.2.9
@@ -7,7 +7,7 @@
set access control policies at the object level, that is, any
application or system object represented by a row in the
acs_objects
table can be access-controlled via a
-PL/SQL or Tcl interface. The permissions system manages a data model
+PL/SQL or Tcl interface. The permission system manages a data model
that then allows scripts to check permissions using another API call.
Although object level permissions seems appropriate, no developer or @@ -19,7 +19,7 @@ object context, which allows applications to group objects together into larger security domains.
The rest of this document discusses each of these parts, and how they fit together with the -permissions system. +permission system.
OpenACS 5.9.0 has an abstraction called a party. Parties have a recursive definition. We can illustrate how it works with the following @@ -72,7 +72,7 @@ The full details of the groups data model is beyond the scope of this tutorial. See Parties in OpenACS or OpenACS 4 Groups Design for more details.
- NOTE: Much more detailed information about the permissions system + NOTE: Much more detailed information about the permission system and how to use it is available in the OpenACS Permissions Tediously Explained document.