Configure Organizational Attributes

In the Management Portal at Data Model > Organizational Attributes, configure Organizational Attributes. Organizational Attributes store organizational information, like distribution list names and security levels. You can use Organizational Attributes in services to provide values in actions. The actual values of these fields are provided by an actor or automatically generated during the service transaction.

With Organizational Attributes you can:

  • specify unique values for organizational context. You specify these values at Organization, on the Attributes tab of an organizational context item. An Organizational Attribute is only available for the organizational context to which you assigned it.
  • specify which Organizational Attributes apply to the subscriber to the service. These subscriber attributes specify values in various workflow actions and service attributes.

Configuration

Field Explanation and Tips
Name Specify the name of the Organizational Attribute. You can configure multiple attributes with the same name. However, when you assign an attribute to organizational context, its name must be unique for this item.
Organizational Context Assign the attribute to organizational context.
  • You can only assign new attributes; it is not possible to change this assignment at a later stage.
  • You can only assign attributes to top-level organizational context (i.e. Departments and all its child items, not Departments\Sales only).
Child organizational contexts can inherit this value Allow organizational context to inherit the Organizational Attribute value from a parent.
This makes it easier to configure Organizational Attribute values that are shared on different levels within the organization.
For example, in an organization with multiple locations, every department at a specific location probably has the same street address. If the street address needs to be stored as Organizational Attribute on each organizational context item, you can set the address at the location level, and let the departments inherit this value.
  • You can specify a value for each organizational context item for which the Organizational Attribute is available. You can do this by editing the item on the Organization page.
  • If you delete an Organizational Attribute and you have used it as a subscriber attribute in a workflow action, the placeholder itself (e.g. #Subscriber.Roles[Role]) is not deleted.
    If Identity Director cannot resolve a value for the placeholder, the value is empty.
  • A default Organizational Attribute Name is available for each organizational context item, which stores its name (for example, #Subscriber.Departments[Name]).
    • This is a fixed attribute: it is not available at Data Model > Organizational Attributes, and you cannot add, edit or delete it.
    • This attribute is first available when the organizational context item contains another Organizational Attribute: if no other Organizational Attributes exist, it is not available.
See also