What roles exist in Alfabet?
A role is the functional relationship or responsibility that a user or organization has to an asset. In contrast to an authorized user who has read/write permissions, a person 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. Examples of roles include Architect, Business Owner, or Stakeholder.
Roles are based on preconfigured role types although your system administrator may configure more 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. Whether users or organizations can fulfill the role is also preconfigured. The role types available depend on the object class that the asset is based on. Out-of-the-box role types are:
- 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.