Project members are Constellation users enrolled in a Constellation project.
They’re usually Modelio users who can open the project, modify the model, and close the project, without being able to change its composition.
The project administrator himself is a project member to whom the domain administrator (or server administrator) has granted administration rights.
Each member of a Constellation project is necessarily enrolled in a profile which defines both the model contents they’ll have access to, and their access rights on the model.
Carefully choosing a profile for each user is therefore an essential task that depends on their functions and responsibilities within the project.
In this example, the project is composed of four different fragments, and the members are dispatched in three different profiles: one “Analyst”, four “Developers” and two “Testers”.
See Managing the project’s user profiles for more details about profiles configuration.
For the project administrator to be able to add a new member to the project, the user in question must already be part of the same domain as the project. If the user is not visible in the domain, the project administrator will have to contact the domain administrator who has the ability to create new Constellation users or welcome existing ones in the domain.
Once enrolled into the project, the new member will be able to connect to it from Modelio and access the project’s portal on the Constellation server.
See also:
When the project administrator removes a member from the project, the latter cannot connect to the project any more.
However, if the user had already been connected before, they will still be able to open their local project. But it will no longer be possible to synchronize the local project with the Constellation project. In other words, the local project will remain frozen in the same state with no possibility to benefit from the project configuration changes made in Constellation.
Also, it will not be possible to make any modification in the model, except in the local fragments (which won’t be shared).
See also:
A project administrator is usually able to modify the rights of the other members of the project. This includes managing the access rights to the model, i.e. each member’s profile, and the possibility to name other administrators to the project.
To every project administrator, Constellation offers the possibility to establish a precise list of simple rights in order to refine the role of each member of the project.
For example, it possible to grant only the possibility to manage modules to a member who is in charge with providing tools to the project. They will have access to the Constellation server as project administrator, but won’t able to add new members.
See also: