How to Configure Access Privileges in Communigram
Since Communigram is a system that works directly against a database, it is particularly important to be able to configure user access privileges in order to prevent users overwriting or deleting each other’s data by accident. Communigram provides powerful features to define user access privileges using access profiles and a hierarchic ordering of access nodes. The concept is rather similar to how access privileges are defined in a file system, so experienced administrators should have no problem in configuring the system.
The first important distinction to make is between Communigram and myCommunigram. In Communigram, access privileges are defined using a combination of access nodes and access profiles. Contrarily, in myCommunigram, access privileges are defined in the project plan itself, simply by drawing the dots and arrows.
Access Privileges in Communigram
Three types of access privileges exist in Communigram:
- administrative privileges that are defined system-wide using the so-called "global profiles". (e.g.: create/edit/delete resources, competencies, licenses, users, etc.),
- planning privileges that are defined by using a combination of access nodes and project profiles (e.g.: create/edit/delete projects or project nodes (Enterprise Project Structure / EPS), deliverables, dates, constraints, arrows, ...),
- execution privileges of project participants that are defined simply by planning the project by adding dots and arrows (e.g.: begin the production of a deliverable, access to the documents in the "target" column, add documents to the "finished deliverables" column, send messages to other participants, Suppliers, Clients, project manager, etc.).
Administrative and planning privileges only affect the use of Communigram, while the execution privileges are exercised using both Communigram and myCommunigram.
Special Access Privileges in myCommunigram
In myCommunigram, every user that participates in a deliverable (large or small dot of a deliverable) can:
- access all existing documentation in the target column and the finished deliverables column
- send messages to other participants
Deliverable responsibles have further access privileges:
- start a deliverable
- request additional input
- set traffic lights
- edit documentation in the finished deliverables column (as long as the deliverable is not finished)
- send messages to participants, suppliers and clients
For more information on how to configure access privileges, please consult the following pages: