Define the users and organizations that have a role for the application

In contrast to the concept of an authorized user or authorized user group which grants read/write permissions to an object, roles which are fulfilled by people or organizations may also be specified for an object. The role definition specifies the functional relationship or responsibility that a user or organization has to an object. The specification of a role is primarily for documentation purposes and provides additional information about stakeholders interested or responsible for the object. A person assigned to have a role for an object will not have read/write permissions based on the role definition. If the user shall have read/write permissions, they must be assigned to an authorized user group specified for the object.

Alfabet FastLane 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 application, either:

• Click the Edit button to open the wizard and select Responsibilities in the Go to Step field
• In the data table, click the navigate  button of the application you want to define. Click Overview and scroll to the Responsibilities page and open it.

Define the users that have a role for an application. In the toolbar, click Person to associate a user with the application. The user can have one of the following roles or a custom role added by your company:

• Application Manager: A person who is the subject matter expert for an application from a functional and technical point of view.
• Architect: A person who is responsible for the governance of the application.
• Business Owner: A person or organization that owns the application and is responsible for managing the functional requirements.
• IT Owner: A person or IT organization that owns the application and thus typically responsible for approval decisions.
• Stakeholder: A person or organization that has an interest in the application and therefore requires read-only access permissions.

In the selector, find the user to assign the role to and click OK.

Define the organizations that have a role for an application. In the toolbar, click Organization to associate an organization with the application. The user can have one of the following roles or a custom role added by your company:

• Business Owner: A person or organization that owns the application and is responsible for managing the functional requirements.
• IT Owner: A person or IT organization that owns the application and thus typically responsible for approval decisions.
• Operations: An IT organization responsible for the operations of the application.
• Stakeholder: A person or organization that has an interest in the application and therefore requires read-only access permissions.

In the selector, find the organization to assign the role to and click OK.