Description
Problem to solve
Currently, Access Control is a dedicated page (/access-control) that also surfaces other git provider added by the user in /settings.
This is part of #3300. 🍕
User Experience goal
The user should be able to a) see a list of all available (git) providers, b) gradually ask for or revoke additional permissions per provider per need, c) add additional (git) providers.
Proposal
In this context and since adding additional providers is not a common user action, it seems optimal to merge these two existing functionalities (Access Control and Git Providers) to a single starting page and have the Access Control as a starting pont.
In this first MVC (minimum viable change), we can do the following:
- Introduce a dedicated page for seeing the list of all (git) providers including the default providers (GitLab, GitHub, Bitbucket) as well as enabled specific permissions for each provider.
- Allow users to authorize with the any of the providers listed.
- Allow users to see the list of as well as add or remove additional providers.
- (Optional) Rename Access Control to Providers, Integrations, Connections or something similar to make it friendlier to the user.
- Show a modal to update provider permissions or additional providers.
Components involved:
- Text Field
- Button
- Modal
- Checkbox
- Dropdown
- Table or List
Designs
| Integrations | Integrations (Spacing) |
|---|---|
 |
 |
| Provider | Provider (Connect) | Provider (Update) |
|---|---|---|
 |
 |
 |
| Integration (New) | Integration (Error) | Integration (Success) | Integration (Activate) | Integration (Remove) |
|---|---|---|---|---|
 |
 |
 |
 |
 |
See also design specs.
Documentation
No documentation changes are needed for this first iteration.