Documentation Center

Validation Security Modes

Validation security is based on user permission rather than the term database's validation mode.
  • When you propose a new or changed term, the term will always get a status of Proposed.
  • When you approve a proposal, that term will always get whatever status you select.
  • When you import terms, you may elect to have them imported under a specific status, or to follow the status of the incoming terms.
  • If you have sufficient permission, you can select the term's status when you add or change a term.

User type permission is assigned to users, but TD validation mode is assigned to term databases. To make the validation security map on a per-database basis, you can use the previously described term database ACLs to fine-tune per-database access for each user. Note that you cannot configure a user to have full write and status modification permission on one term database and restrict that same user's status modification permission on another term database. This is because access control permissions only cover broad read and write permissions. A user can have either read-only or read/write access to a term database.

The following table lists the user type permissions and terminology database ACL permissions needed for each operation. User type permissions are organized in a hierarchy: having a permission implies also having its parent permission.

For example, the first table row indicates that, when you perform a terminology database search, if you have only the Can browse TD user type permission and Read ACL permission for the terminology database, you can only search for terms in languages whose locales are mapped to you. If the terminology database contains terms in German, Spanish, and Russian, and you only have the German locale mapped to you, your result set will include only German terms. If you had, additionally, the Can view terms outside user's locales permission (see the second table row), you would also see the Spanish and Russian terms.

OperationRequired User Type PermissionRequired ACL Permission
Browse/search terms in own languagesCan browse TDRead

Browse/search terms in all languages

Can view terms outside user's locales

Read

Propose new/changed term in own language

Can submit proposals

Read

Propose new/changed term in all languages

Can view terms outside user's locales

Can submit proposals

Read

Modify term entry attributes

Can modify TD

Write

Modify terms (including attributes) in own languages

Can modify TD

Write

Modify terms (including attributes) in all languages

Can view terms outside user's locales

Can modify terms outside user's locales

Write

Change term status in own languages

Can modify term statuses

Write

Change term status in all languages

Can view terms outside user's locales

Can modify terms outside user's locales

Can modify term statuses

Write

Delete terms in own languages

Can delete terms

Write

Delete terms in all languages

Can view terms outside user's locales

Can modify terms outside user's locales

Can delete terms

Write

Delete term entries

Can view terms outside user's locales

Can modify terms outside user's locales

Can delete term entries

Write

Delete result set

Can delete result set

Write

Purge TD

Can purge TD

Write

Import terms in own languages

Can import terms

Write

Import terms in all languages

Can view terms outside user's locales

Can modify terms outside user's locales

Can import terms

Write

Import terms in specific status

Can import terms

Can modify term statuses

Write

Export terms

Can export terms

Read

Create validation workflow

Can view terms outside user's locales

Can modify term statuses

Can modify terms outside user's locales

Write

Approve proposed terms in own languagesCan modify term statusesWrite

Approve proposed terms in all languages

Can view terms outside user's locales

Can modify term statuses

Can modify terms outside user's locales

Write