Organization roles Rolling out
Last updated .
Who can change what in a MergeSafe organization?
A MergeSafe organization has two roles: Admins, who can change everything and see billing, and Members, who can see the organization’s reviews but can’t change settings or see billing; the person who installed the GitHub App is the first Admin.
Rolling out. The rules below are being rolled out now. Some pages in the app may not show the read-only state for Members yet; when a Member tries a change, the app says that only org admins can change it.
The two roles
| Admin | Member | |
|---|---|---|
| See reviews and pull requests | Yes, every repository | Yes, for repositories they can access on GitHub |
| See spending limits | Yes | Yes |
| See the balance, usage and charges | Yes | No |
| Change settings, levels and limits | Yes | No |
| API keys, Sentry, clusters | Yes | No |
| Review now in the app | Yes | Only if an Admin allows it |
| Approve people and change roles | Yes | No |
How roles are given
- The person who installed the MergeSafe GitHub App is the organization’s first Admin.
- Roles are MergeSafe’s own. Your GitHub organization role doesn’t decide them.
- Other people request to join, and an Admin approves them as Admin or Member.
- An organization always keeps at least one Admin.
@mergesafe commands on a pull request follow GitHub’s repository permissions, not these roles. See commands.
Next: Joining an org →