About Roles

User access to project information and permissions to perform various actions on project objects are determined by the role A Collaboration mechanism that controls access levels and permissions for Collaboration objects. Users are assigned to a role, thereby determining what that user can do within a project. to which a project user is assigned. A portal user can access a project only after you have assigned them to a role in that project.

For step-by-step instructions on how to assign roles, see Assigning Roles.

Project Roles

The three project roles are:

Project Leaders: this role has full control Project Leaders have full control for Collaboration objects. This includes Read, Write, and Edit permission for the objects, as well as the ability to set role permissions for the object. of all Oracle WebCenter Collaboration objects. Project leaders can create, modify, and delete objects, and can perform all actions on project objects. This role can also assign access privileges to projects and project objects.
Project Members: by default, this role has Write access to project objects and can participate in the project. This role can create events and tasks, add documents, attach links, and check files in and out. The access privileges for this role are configured by the Project Leader
Project Guests: by default, this role has Read access to project objects. This role cannot create objects; it is intended for users who simply want to monitor projects but not participate actively. The access privileges for this role are also configured by the Project Leader

Role assignments are project-specific. You can assign the same portal user to different roles in different projects. Additionally, you can assign a portal user to the same role in different projects. However, because Oracle WebCenter Collaboration security is set on individual projects, Project Members and Project Guests can have one set of permissions in one project and a different set of permissions in another.

Functional Area Security

Each functional area has specific actions that can be enabled or disabled for a given role. These action privileges can be granted:

For the entire project.
For a single object.

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.

Related Topics: