You can set the default permission for objects in Collaboration. The actions that users are able to perform are defined by the role each user is assigned in the project.
This topic discusses:
Project Roles
Functional Area Security and Object Security
Owner Privileges
Permission Matrix
System-Generated Groupings
The Collaboration roles are:
By default, Project Leaders are granted full control. Users in that role can create, modify, and delete project objects and set permissions for other roles. And only Project Leaders can post announcements and publish to portal.
By default, Project Members have write access level to Collaboration objects and Project Guests have read access level.
For step-by-step instructions on how to assign roles, see Assigning Roles.
Functional Area Security and Object Security
Each functional area has specific actions that can be enabled or disabled for a given role. These action privileges can be granted:
For example, the permission to delete discussions is granted to a role for an entire project. That is, for a given project, a role is allowed to delete discussions or it cannot delete discussions. However, the permission to update the status of tasks can be granted on a task-by-task basis. That is, for some tasks, the role can update the status; for other tasks, the role cannot update the status.
The Edit Permissions page let you grant permission on a project level. If you want to grant permission on an object-by-object basis, you must go to the security page of each object.
The owner, who is the user who created the object or uploaded the file, has full control of that object. He or she can do everything to the file except change its security.
You can remove owner privileges on documents or files from a user if he or she is no longer participating in the project and, consequently, should not have high-level access privileges to the file. To remove owner privileges of a file, configure the security page of the file.
All Collaboration objects have five possible levels of access: No Access, Read, Write, Edit, and Admin. Each access level above No Access inherits the rights from all lower access levels.
The following matrix describes what each access level will let you do in a given functional area:
|
Read |
Write |
Edit |
Admin |
Projects |
|
|
|
|
Calendar |
|
|
|
|
Tasks |
|
|
|
|
Folders |
|
|
|
|
Documents |
|
|
|
|
Discussions |
|
|
|
|
|
Read |
Write |
Edit |
Full Control |
For each portal community, the system generates the following groupings of portal users, which you can assign to one or more project roles on the Roles and Permissions page:
Community Members: All users who have the Select access privilege for the portal community.
Community Managers: All users who have either the Admin or Edit access privilege for the portal community.
Community Guests: All users who have the Read access privilege for the portal community.
By default, Collaboration synchronizes its user information with the portal once a day. If any users have been added to or deleted from the groupings of Community Members, Community Managers or Community Guests since the last synchronization, Collaboration changes the role's user information to keep it current with the portal community's user information. You can also synchronize this information manually. For more information, see the Roles and Permissions page.
Back to Top