Roles

A role describes the functional relationship that a user or organization has for an object. Users as well as organizations can be specified to have a role for each asset in the IT portfolio. A user assigned a role for an asset will not have read/write permissions based on the role definition. The role is primarily for documentation purposes to provide information about stakeholders interested or responsible for the asset.

Alfabet provides out-of-the-box role types that enable you to understand who is responsible for your IT assets in your IT portfolio. Additional role types that are relevant for your company may also be added by your system administrator.

Your portfolio administrator may configure additional role types that are relevant for your company. The role types available for an asset will depend on the object class that the asset is based on.

An application can have the following roles defined:

  • Application Manager: 1 user
  • Architect: 1 user
  • Business Owner: 1 user and 1 organization
  • IT Owner: 1 user and 1 organization
  • Operations: 1 organization
  • Stakeholder: multiple users and multiple organizations

An application group has only the following permissible roles:

  • Application Manager: multiple users
  • Architect: multiple users
  • Stakeholder: multiple users and multiple organizations

Roles can be specified in the following places: