Defining projects

A project defines a set of related CRs and assigns roles to groups of users within that context. Therefore, user privileges vary dynamically based on the CR.

About this task

Full access to all projects is given through the Admin interface, regardless of the administrator and editor designations. This interface is the only place where top-level projects (as opposed to subprojects) can be created.

In contrast, only the projects for which a user is an administrator or editor are shown in the User interface. If the user has access to any projects, the Projects link is shown in the Action Panel.

Procedure

To define projects:

  1. Start an Admin session.
  2. On the Action Panel, click User Management.
  3. Click the Project Security tab.
  4. Click the Projects tab.
  5. Click New.
  6. In the Name field, type the project name.
  7. In the Administrators field, select the users who can administer this project.

    Administrators are users who can modify all aspects of the project. The local admin user (_change_admin) is always considered an administrator, even if it is not explicitly listed.

    Separate the list of users with commas.

  8. In the Editors field, select the users who can edit this project.

    Editors are users who can modify the members and privileges of the project and create new subprojects. Editors cannot edit the project contents.

    Separate the list of users with commas.

  9. In the Contents (CRs included in this Project) section, specify the project contents, and then add the appropriate attribute name-value pairs to match the CRs.

    Attributes within a row are ORed together. Attributes between rows are ANDed together.

  10. In the Members and Privileges section, specify the project members and their privileges.

    Each row grants the list of users or groups a particular role or privilege.

    Separate the list of users with commas.

  11. Click Save to save the changes.
  12. If necessary, edit or delete the existing roles.

Feedback