Domains in Properties & Specifications

How to use domains in properties & specifications

1. To use domains in properties & specifications you have to create them in the project access management area first.
   

   Learn more about creating domains here: Access Management

2. To be able to assign domains you need to have access to the respective domain. So if all domains are disabled in the dropdown then you should visit the access management and assign the domains that you are responsible for to yourself, or if you do not have the rights for the access management ask someone who can do it for you.

3. You can assign domains to properties and specifications when you create or update them.

Assigning domains is always an optional step.

Inherit domains in properties & specifications

Domains can be inherited for a more efficient management of the various domains in your catalog.

• In Properties:
  Properties inherit the domain of the property group that they belong to. So if you have a property group only with properties for a specific domain you can assign the domain on the property set instead of assigning it to every property separately.

• In Specifications:
  Specifications inherit the domain from their parent specifications.

You can always overwrite the inherited domains, if you want to restrict it further:

When and why should I use domains?

We recommend to use domains when working on a project where many people with clearly defined roles are involved. Assigning domains to specifications and properties not only makes it clear who is responsible for delivering the required information, but it also prohibits users from making changes in the requirements where they are not supposed to.
If you do not select a domain for a given specification or property, every team member with editing rights can change them by default.