By default, non-administrative users will not be allowed to see any project content. Access control needs to be configured for each project. You manage project access on
NOTE: This topic describes settings in
There are several ways a user can have access to a project:
- The user is an administrator for the server.
- The user is a developer for the project.
- The project has the Allow Access to all Users check box selected, or the user has access to a special home project (if this feature is implemented).
- The user belongs to a group that has access to the project.
Most users will have access to projects through a group association. The following sections describe how to provide project access with each method.
Select the Administrator User check box on the Security/Licensing tab for the user.
Each administrator user you add to a DiveLine connection will have access to all projects on that DiveLine connection. Note that there is a green check mark next to each project in the Projects tab for this user, and the Access Level is Administrator for all projects.
You can grant selective administrator project access (on a per-project basis) to a user to work on specific projects by assigning that user the Developer access level.
To set a user as a project developer on a project:
Double-click the user in the Users tab, and click the Projects tab.
For the specific project, select a level (None, User/Group, or Developer) from the Access Level drop-down list.
None—The user cannot open anything in the project.
User/Group—The user or group can read and write files within the project per the normal access control rules
(see Access Control Overview). Most users fall in the User category as users of cBases and Models.
Developer—The user has full access to everything in the project and is not subject to the access control rules. Users in the Developer category can create and run Integrator and Production scripts. However, how much true administrative access this developer has depends on
the Allow non-Administrator Project Developers setting (Tools > Server Settings > General > Security > User Management). See User Management for definitions of the possible settings.
Save the tab.
To set Allow Access to all Users:
- Open the DiveLine connection. See Opening and Closing Connections.
- Click Tools > Server Settings.
- In the Server Settings tab, click the Projects tab.
- Select the project from the project list, and click Access List, which is the right-most command button. Alternatively, you can double-click the project to open the access list.
- Select the Allow Access to all Users check box. Note that there is a green check mark next to each DiveLine user for this project as shown here.
Save the tab.
Any future users added after selecting the Allow Access to all Users check box will also have access to this project.
NOTE: When the home project feature is enabled, the Allow Access to all Users check box is automatically set so that all users on the DiveLine have access to the home project and their home directories.
To set project access from the Groups tab:
Click the Groups tab.
Select the group from the list, and click Edit Group. Alternatively, you can double-click the group.
Click the Projects and Properties tab.
There is a check mark in the Access column of each project that the group can access.
Select additional project check boxes to grant the group access to additional projects.
Save the tab.