Roles provide the building blocks for the security system. Roles have permissions that define the actions the roles can perform with product features. Typical actions include changing or executing an item, such as an application process, or modifying its security settings. Users or groups assigned to a role are automatically granted the permissions configured for it. The default roles can be edited and new roles can be created.
Serena Release Automation maps key product features or areas to security roles. Each area has several permissions defined for it (listed below). When you create a role, you first specify the product area. Selecting a product area defines the set of permissions available to the new role—only permissions defined for the area are available.
Generally, permissions fall into one of these groups:
| Permission | Description |
|---|---|
| Security | Enables users to change an item's security settings. For example, a user with this permission for agents can determine which users can view, configure, and set security for them. |
| Write | Enables users to add, change, and delete items. A user with this permission for components can create a component. |
| Read | Enables users to read (view) an item, but not change it or create another of its type. A user with this permission for agents, say, will be able to see agents within the user interface, but will not be able to modify them or create another unless granted additional permissions. |
| Execute | Enables users to run processes associated with applications, components, environments, and resources. Users must also have read permission for an item before actually executing it. |