OK I'll try again, learning how to submit a patch properly and help clean up a little bit :)
Index: security-howto.xml =================================================================== RCS file: /home/cvspublic/jakarta-turbine-2/xdocs/howto/security-howto.xml,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 security-howto.xml --- security-howto.xml 2001/08/16 05:10:12 1.1.1.1 +++ security-howto.xml 2001/09/30 18:19:55 @@ -36,12 +36,12 @@ <p> The main tables are TURBINE_GROUP, TURBINE_USER, TURBINE_ROLE and TURBINE_PERMISSION. -The Permissions are the individual actions a user is allowed to take in the system. -The Role is a container for the Permissions, in other words a Role can be made of -many Permissions. User is an account that is interaction with the System and the Group +Permissions are the individual actions a user is allowed to take in the system. +Role is a container for the Permissions; in other words a Role can be made of +many Permissions. User is an account which provides interaction with the System. +Group is a something that a User would want to do something in. In the Turbine mailing lists it has often been described in the same way as a project. In a project you have fulfill -a role, however a User doesnt "belong" to a project they merely have a role in that +a role, however a User does not "belong" to a project they merely have a role in that project ( or group ). In this manner too a User can have many Roles within the one Group. For instance a User may have the Role Developer in the Group, but may also have the Role of Administrator as well. While initially confusing at first, as there $ Yes? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
