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.
-
- Application Manager: A person who is the subject matter expert for the application from a functional and technical point of view.
- Architect: A person who is responsible for the governance of the asset.
- Asset Owner: A person or organization who legally owns the asset. These users and organizations are responsible for making asset allocation decisions based on strategic and operational objectives.
- Business Owner: A person or organization who owns the asset and is responsible for managing the functional requirements.
- Capability Owner: A person who is responsible for the business capability/IT capability.
- IT Owner: A person or IT organization owning the asset and thus typically responsible for approval decisions.
- Operations: An IT organization responsible for the operations of the asset.
- Project Manager: A person who is responsible for planning, organizing, managing, and executing projects from beginning to end including the project's budget, resources, and scheduling.
- Staffing Manager: A person who is responsible to allocate and balance the human resources required for a project.
- Stakeholder: A person or organization that has an interest in the assets and therefore requires read-only access permissions.
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:
- In a data workbench if the appropriate role columns have been added via the Structure button
- In the Responsibilities view in an asset's content area