Assigning users to the groups

The basic requirement for granting the authority of the editor of project applications and projects records is to give the user the role projects.

Assigning this role is sufficient if the workflow is not used and has not been defined. Otherwise, you need to define user groups (assignment to object classes) and make a user assignment to at least one of the groups.

Defining user groups makes it easy to assign users rights related to the development of project descriptions.

In the example solution used at Warsaw University of Technology, the user groups described in User Group Management:

• Central project services (COPadministrator): [administrator].

• Central project services (COPeditor): [editor];

• Central project services (COPeditorlimited): [editorlimited].

• Projects managed at the departmental level (FacultyEditor): [editor].

• Manage centric project types (COPpptadministrator): [administrator].

• Faculty Project Type Management (FacultyPptEditor): [editor].

Assignment to a user group is specified on the user data editing form (after entering the edit mode of a user's record). In the screen below you can see the available user groups, and in the case of this user, an assignment has been made to the Central project services (COPeditor) group. This group gives permission to edit project applications and projects managed by COP.

Open

Users with broad privileges (project module administrators) can be assigned to multiple user groups, as shown in the following screen:

Open