Authorizing Team Members to Create Independent Assigned Expressions
This topic describes the permissions that are necessary for participants such as Team Members to create IndependentAssignedExpression objects.
The parent folder (Cabinet) for IndependentAssignedExpression objects resides in the System domain of the product, and the IndependentAssignedExpression object resides in the Default domain of the product. To create an object that resides in a folder, a participant must have Modify permission to the folder. Therefore, to create IndependentAssignedExpression objects, participants must be granted Modify permission on type Cabinet in the product System domain. To create a lifecycle-managed object such as IndependentAssignedExpression, participants are typically required to have Create permission for the object in its initial lifecycle state. Because of the current system limitation, participants are required to have Create permission in all states. To allow participants to create IndependentAssignedExpression objects, participants must be granted Create permission for type IndependentAssignedExpression for all states in the product Default domain.
An IndependentAssignedExpression is associated with business objects that implement the IndependentExpressionAssignable interface. When the associated object is saved to a different context, moved, or deleted, the same action is performed on the IndependentAssignedExpression. Because of these close relationships, it is recommended that you define policy rules for IndependentAssignedExpression similar to those defined for WTPart.
The following out-of-the-box access control policy rules grant Option Manager Full Control (All) permission for IndependentAssignedExpression and Cabinet objects.
For the organization context or Default/PDM domain:
Type: IndependentAssignedExpression
Permissions: + Full Control (All)
Participant: Option Manager
For the application context (for example, product) or System domain:
Type: Cabinet
Permissions: +Full Control (All)
Participant: Option Manager
In addition to these access control policy rules, the following rules are recommended for Team Members.
For the organization context, Default or PDM domain, or the application context (for example, product or Default domain):
Type: IndependentAssignedExpression
State: All
Permissions: +Read, +Create
Participant: Team Members
Type: IndependentAssignedExpression
State: In Work
Permissions: +Modify, +Delete, + Change Domain, + Create By Move, + Change Context
Participant: Team Members
Type: IndependentAssignedExpression
State: Released,
Permissions: +Revise,
Participant: Team Members
For the application context (for example, product) or System domain:
Type: Cabinet
Permissions: +Modify
Participant: Team Members
* 
Currently, the only out-of-the-box rule that authorizes Team Members for the type IndependentAssignedExpression is in the organization, Default, or PDM domain, granting Read permission.
The ability to create and manage Independent Assigned Expressions is an advanced capability subject to a separate license entitlement.
Was this helpful?