Cloud - Authorization Configuration
- CrossALM
- Daniel Triftshaeuser
- Kristin Hildebrand
Jira End-Users will needed specific authorizations to be able to to interact with Transport Requests when they are using the Cross Connector. To customize the authorization groups, in the section “Customer Actions”, define which group can have access to which functionality:
End-User assigned to the group cross-connector-transport-admin can interact with all Cross Connector features.
The following table describes how the authorization groups works:
Action Type | Explanation |
|---|---|
INITIAL | End-Users assigned to the group described on the field “User Group” will be able to create “Transport Requests”. Button “New” is visible.  |
DELETE | End-Users assigned to the group described on the field “User Group” will be able to delete “Transport Requests”. Button “Delete” is visible. |
RELEASE | End-Users assigned to the group described on the field “User Group” will be able to release “Transport Requests”. Button “Release” is visible. |
Couple | End-Users assigned to the group described on the field “User Group” will be able to couple “Transport Requests”. Button “Couple” is visible. |
Decouple | End-Users assigned to the group described on the field “User Group” will be able to decouple “Transport Requests”. Button “Decouple” is visible. |
TOC | End-Users assigned to the group described on the field “User Group” will be able to create “Transport of Copies”. Button “Create ToC” is visible. |
CUSTOM | End-Users assigned to the group described on the field “User Group” will be able to execute the customer action.
|