mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
Rewrite DockerHub group permissions documentation
On behalf of @moxiegirl https://gist.github.com/moxiegirl/1c34957b9edc0f6d528c#file-gistfile1-md Signed-off-by: Tristan Carel <tristan.carel@gmail.com>
This commit is contained in:
parent
4dd1d1bfa5
commit
515df52f19
1 changed files with 12 additions and 16 deletions
|
@ -68,23 +68,19 @@ are members.
|
||||||
|
|
||||||
### Repository group permissions
|
### Repository group permissions
|
||||||
|
|
||||||
Use organization groups to manage who can interact with your repositories.
|
Use organization groups to manage the users that can interact with your repositories.
|
||||||
|
|
||||||
You need to be a member of the organization's `Owners` group to create a new group,
|
You must be in an organization's `Owners` group to create a new group, Hub
|
||||||
Hub repository or automated build. As an `Owner`, you then delegate the following
|
repository, or automated build. As an `Owner`, you then delegate the following
|
||||||
repository access rights to groups:
|
repository access rights to groups:
|
||||||
|
|
||||||
- `Read` access allows a user to view, search, and pull a private repository in the
|
| Access Right | Description |
|
||||||
same way as they can a public repository.
|
|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
- `Write` access users are able to push to non-automated repositories on the Docker
|
| `Read` | Users with this right can view, search, and pull a private repository. |
|
||||||
Hub.
|
| `Write` | Users with this right can push to non-automated repositories on the Docker Hub. |
|
||||||
- `Admin` access allows the user to modify the repositories "Description", "Collaborators" rights,
|
| `Admin` | Users with this right can modify a repository's "Description", "Collaborators" rights. They can also mark a repository as unlisted, change its "Public/Private" status and "Delete" the repository. Finally, `Admin` rights are required to read the build log on a repo. |
|
||||||
"Mark as unlisted", "Public/Private" status and "Delete".
|
| | |
|
||||||
|
|
||||||
> **Note**: A User who has not yet verified their email address will only have
|
|
||||||
> `Read` access to the repository, regardless of the rights their group membership
|
|
||||||
> gives them.
|
|
||||||
|
|
||||||
![Organization repository collaborators](/docker-hub/hub-images/org-repo-collaborators.png)
|
|
||||||
|
|
||||||
|
|
||||||
|
Regardless of their actual access rights, users with unverified email addresses
|
||||||
|
have `Read` access to the repository. Once they have verified their address,
|
||||||
|
they have their full access rights as granted on the organization.
|
||||||
|
|
Loading…
Reference in a new issue