Project Members
Enterprise Feature
Project members are only available in the enterprise edition with cibseven.webclient.modeler.enabled: true, from 3.0.0. See Enable / Disable. In the community edition every project is open to everyone who can use the modeler.
A project is a folder at the top level of the start page, Projects, together with everything below it. See Folders. Projects can have members: users and groups, each with a role. Members are kept for the project as a whole, so every folder, diagram and form in it follows them.
Open and Restricted Projects
A project without members is open: everyone who can use the modeler sees it and can work in it, as before. General, the folder that holds the models from before folders existed, starts out like this.
As soon as a project has a member it is restricted: only its members and administrators see it. Nobody else finds it on the start page, in a search or through a link, and its models cannot be opened, saved or deployed by them.
Administrators are the users granted the All permission on the System resource. They see every project and may do everything a Project Admin may, also in projects they are not a member of.
Roles
| Role | Can |
|---|---|
| Project Admin | Manage the members, rename and delete the project, and everything an Editor can |
| Editor | Create, import, change, move, copy, delete and deploy the folders and models of the project |
| Viewer | Open and look at the models, download and copy them |
A user who is a member directly and through a group gets the higher of the two roles.
A Viewer sees every model of the project, but cannot change it: the editor opens read-only, with a note saying so. There is no palette, the properties can be read but not edited, the XML source cannot be typed into, and saving and deploying are not offered. Autosave does nothing for such a model. On the start page, the project shows Viewer, and its rows offer only what a Viewer can do.
A restricted project shows a lock next to its name.
Who Becomes a Member
- Creating a project makes its creator its Project Admin. A new project is therefore restricted from the start: only you and administrators see it until you add others as members.
- Your own folder belongs to you: the first time you open the modeler after the update, it gets you as its Project Admin, so it is no longer open to everybody. You can add members to it to share it, see Managing Members.
- The first member of an open project can only be added by an administrator. Otherwise anybody could restrict a project everybody shares, such as General, and lock everyone else out of it.
Managing Members
A project’s Project Admins, and administrators, find Members… in the actions of the project’s row. It opens a dialog listing the members with their roles.
To add one:
- Choose User or Group.
- Enter the ID. While you type, the dialog suggests the users or groups you may see in the engine. If you may not look up users or groups, type the exact ID instead.
- Choose the role. The dialog describes what each role can do.
- Select Add.
Adding the first member to an open project asks first, because from then on only its members and administrators can open it.
When the modeler cannot confirm that the user or group exists — because you may not look them up — the member is still added, and the dialog says so. Check the ID if they cannot open the project.
The role of a member can be changed in the list, and a member can be removed. A project always keeps at least one Project Admin: the last one can neither be removed nor given another role. Changes apply immediately.
Group members and a remote engine
Group memberships count when the modeler knows which groups a user belongs to. With the embedded engine it always does. When the webclient talks to the engine over REST, it asks the engine with the rights of the user, so a user only counts as a member of a group they may read. Grant the users Read on their groups, or add them as users, if group membership does not seem to work.
Moving and Copying
Moves stay inside a project, so that moving something never changes who can see it:
- A folder or a model can be moved anywhere inside its project. This needs the Editor role.
- A folder can be moved to the top level, Projects, where it becomes a project of its own. It takes over a copy of the members of the project it came from, so the same people keep the same access. This needs the Editor role in the project it leaves.
- Nothing can be moved into another project, and a project cannot be moved into a folder. The Move dialog lists only the folders of the same project, and the top level.
To bring models into another project, copy them: a copy can go into any project you are an Editor or Project Admin of, and the original stays where it is. Delete the original afterwards if it is no longer needed.