Design: Permission settings for Secrets Manager

Problem to solve

The Secrets Manager permission configuration involves two models for authorising access: Human (user) permissions and Pipeline permissions. This issue focuses on revisiting the early design for configuring the human permissions on the settings page.

The dropdown with combobox component that used in the early design is commonly find in the product (e.g., in Settings > Repository > Protected branches). This component does not clearly display selected items. It shows a summary like 2 roles, 3 users, with details hidden within the dropdown. Mixing selected and non-selected items makes it challenging to see what’s been chosen in a long list, especially as Secrets Manager supports selecting from users, groups, and roles.

Screenshot of the dropdown in action

image.png

Proposed Solution

Inspired by the members page, the proposed solution displays selected items in a clear, single view with usernames, roles, and additional details shown together. This layout improves visibility and makes it easier for users to quickly understand their selections.

State Early Design Proposed Solution
Default image.png 1_Permissions_Default.png
Add new image.png 2_Permissions_Add.png

Design Overview

The updated design addresses usability issues and aims to enhance the permission configuration experience:

  1. Default state of the permissions table
  2. Add new entity
  3. Entity added

See the design section for more details.

Links

Edited by Bonnie Tsang