Permissions to work with data

The data that you can see and edit will depend on the user profile that you are using to access Alfabet FastLane. This is described in more detail in the section User profiles to access Alfabet FastLane. The ability for a user to create new data or edit the existing data in the repository is managed via several rules in Alfabet FastLane.

An object such as an application, component, business capability, etc. can only be edited if three requirements are fulfilled:

1. The user accesses Alfabet FastLane with a user profile that provides read/write permissions.

   user profile

   A user profile determines the preconfigured set of functionalities and views in Alfabet FastLane. Every user must have at least one user profile to log in. The user profile will grant either read-only or read/write permissions to the objects that are visible to the user.

2. The user is granted authorization to the object because they are the authorized user of the object or a member of an authorized user group that is specified for the object.

   authorized user

   An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for.

   authorized user group

   An authorized user group is a set of users that have been granted write permissions to an object. More than one authorized user group may be specified for an object.

   If no authorized user or authorized user group is specified for an object, all users will have read/write permissions to it.

3. The object has a release status that allows it to be edited. For example, an object with a retired or sundowned release status can no longer be changed.

   release status

   A release status describes the state of approval or agreement about an object in the enterprise. For example, the release status of an application might be Draft, Described, Reviewed, Approved,Rejected, or Retired. Release statuses may determine whether an object can be edited. For example, an application with a release status set to Approved cannot be deleted.

About roles and object responsibilities:

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.