Manage Teams and Access

The Access Management page displays the organization settings. You can view all the teams created in the organization and the user roles assigned to the teams. The resources panel displays the total number of integrations and rules associated with each group.

You have options to create teams or groups and add users to the groups, thereby giving different access permissions to the added users.

To Create New Team

1. Navigate to Setup > Access Management.

2. Click + New Team. A dialog box appears as shown below:

1. Name - Enter a name for the team.

2. Description - Enter a description for the team.

3. Add related tags to the team. The tags are used to distinguish between the teams in an application.

4. Click Create.

The team is created.

To Add User Roles

You can add user roles to the created teams.

1. Click + Add User Role. A popup appears as shown below:

1. Select the group or team from the dropdown.

2. Select the permissions from the dropdown that you want to assign to the added user. You can give either read (access to only view the applications) or admin (access to view and modify the applications) access to the users.

3. Click Save.

The user role gets updated.

The user roles can be added at the organization level and team level.

To Edit a Team

1. Click on the name of the Team (given as tabs in the Teams panel) for which you want to edit the details as shown below:

1. The details of the Team along with its User Roles are displayed.

2. Click Edit as shown below:

1. The Edit popup is displayed. Re-enter the required values and click Update.

The new details get updated.

To Generate Token

1. Click on the name of the Team (given as tabs in the Teams panel) for which you want to generate token as shown below:

1. The details of the Team along with its User Roles are displayed.

2. Click Generate Token button as shown below:

A token is created and a success message is displayed as shown:

The generated token is provided in the Jenkins plugin to integrate Delivery Shield with it, inorder to connect the applications to the respective teams. To know more, see Jenkins.