Domains and organizations or sites
Applying domains to the organization or site level (by typing appropriate values in the organization field and site field) might create unintentional access restrictions. Leaving these fields blank is the default, and stores domains at the system level.
Example one
When you specify an organization or site for domain values, note where the domain is being used.
In the Labor application, you use the SKILLLEVEL domain on the CRAFTSKILL object. You specify both the organization and site values for domain values. When you access the Labor application and lookup the skill level, you do not see your values. This issue occurs because you specified a site, and the object that is using the domain is at the organization level. To fix this problem, remove the site from the domain value.
Example two
You might want to leave the organization field and site field empty for all values (users in all organizations and sites can access them). If you specify an organization or site for one value, you must specify an organization or site for all values (users in the specified organizations or sites can access them).
Otherwise, complicated outcomes can result. For example, you can set an organization with the following domain values:| Value | Organization |
|---|---|
| GREEN | A |
| BLUE | B |
| RED | (No organization specified) |
With this domain configuration, you get the following results:
- Records in Organization A can access GREEN only.
- Records in Organization B can access BLUE only.
- Records in other organizations (other than Organization A and Organization B) can access RED only.