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 -N -r1.50.2.10 -r1.50.2.11 --- openacs-4/packages/acs-core-docs/www/permissions.html 21 Jun 2016 07:44:36 -0000 1.50.2.10 +++ openacs-4/packages/acs-core-docs/www/permissions.html 23 Jun 2016 08:32:46 -0000 1.50.2.11 @@ -143,7 +143,7 @@
... | scope | user_id | group_id | ... |
---|---|---|---|---|
... | user | 123 | ... | |
... | group | 456 | ... | |
... | public | ... |
The first row represents an entry in User 123's personal address book, the second row represents an entry in User Group 456's shared address -book, and the third row represents an entry in the site's public +book, and the third row represents an entry in the site's public address book. In this way, the scoping columns identify the security context in which a given object belongs, where each context is either a person or a group of people or the general public @@ -175,7 +175,7 @@ forum. Then, suppose we grant every user in the system read-access to this forum. By default, they will automatically have read-access to the new message we just inserted, since the system automatically -checks permissions on the message's context. To allow the creator of +checks permissions on the message's context. To allow the creator of the message to change the message after it has been posted we grant the user write-access on the message, and we are done.