Administering Domains, Roles and Users > Domains

Domain Access

Domains can be thought of as separate containers for design data, to which individual user accounts can be granted read-write, read-only, or no access.

You can assign domains to design data in the following applications:

Capital Project Manager — Projects, designs, and shared objects
Capital Systems Integrator — Harnesses
Capital Component Manager — Component part numbers
Capital Logic Designer — Interface Control Documents (ICDs) and shared objects
Capital Device — ICDs
Capital Symbol Designer — Symbol libraries
Capital Workspace — Projects and designs
Capital Analysis — Component Models

You can only assign design data to the domains that the system administrator has defined access to on your user account. You can assign combinations of design data to the same domain, but you can only assign a single project or design to one domain at a time. Components, shared objects, and ICDs can be assigned to multiple domains at a time.

A design can be assigned to a domain that is different to that of its project (and the other way round).

The following table describes the access relationship between a domain assigned to a user account and the same domain assigned to a project:

Domain name	Is the domain assigned to the user's account?	Is the same domain assigned to the project?	Does the user have access to the project?
Domain A	Yes	Yes	Yes
Domain B	No	Yes	No
Domain C	Yes	No	Yes (if no other domain is assigned to the project)
Domain D	No	No	Yes (if no other domain is assigned to the project)

If a project is assigned to a domain and a user has read-only access for that domain, the following applies:

The user can open the project, read-only, in any application and export data from the project.
If a design in the project is assigned to another domain and the user has read-write access to that domain, the user can access and edit the design.
The user can perform the same tasks on a shared object as if it had been frozen.
With read-only access, you cannot make any changes to the project data, for example: The user cannot change any project-level settings.

The user cannot change any parameters within Capital Analysis, including project models and global expressions.

The user cannot edit the design folders in the project.

Project designs with no explicit domain setting are read-only for the user. The user cannot change the contents or any design-level settings.

The user cannot create any new designs in the project. Therefore the user cannot import or copy any designs into the project.

The user cannot copy any design within the project.

The user cannot create new options in the project. Therefore, bridging in data will not create new options.

The user cannot import connectivity that creates new designs.

The only way that a user can edit a project assigned to a read-only domain, is if designs within that project have been assigned to a domain to which the user has write permissions.

Domains can be deleted if no longer required, but only if they are not being used anywhere within a database. Usage checks can be performed on a domain to see where and how a domain is being used.

Parent Topic:

Domains