Define the users and organizations that have a role for the component
In Alfabet, responsibilities are documented via the concept of roles , whereby each role is based on a preconfigured role type or a custom role type defined by your company. 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. If the user should have read/write permissions, they must either be the authorized user of the asset or assigned to an authorized user group associated with 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 can also be added.
Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets?
To define the users and organizations that have a role for an component, click the navigate 
button of the component to open the content area. Go to the Overview page and scroll to the Responsibilities view and open it. Click in a column cell to open a selector to define a role for the component. Depending on the role column, you may be able to select a person or an organization. Switch between Person or Organization in the selector.
A user can have one of the following roles or a custom role added by your company:
- Architect: A person who is responsible for the governance of the component.
- Business Owner: A person who owns the component and is responsible for managing the functional requirements.
- IT Owner: A person who owns the component and thus typically responsible for approval decisions.
- Stakeholder: A person who has an interest in the component and therefore requires read-only access permissions.
An organization can have one of the following roles or a custom role added by your company:
- Business Owner: An organization that owns the component and is responsible for managing the functional requirements.
- IT Owner: An IT organization that owns the component and thus typically responsible for approval decisions.
- Operations: An IT organization responsible for the operations of the component.
- Stakeholder: An organization that has an interest in the component and therefore requires read-only access permissions.