github.com/iamlotus/docker@v1.8.1/docs/docker-hub/accounts.md (about) 1 <!--[metadata]> 2 +++ 3 title = "Accounts on Docker Hub" 4 description = "Docker Hub accounts" 5 keywords = ["Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation"] 6 [menu.main] 7 parent = "smn_pubhub" 8 weight = 1 9 +++ 10 <![end-metadata]--> 11 12 # Accounts on Docker Hub 13 14 ## Docker Hub accounts 15 16 You can `search` for Docker images and `pull` them from [Docker 17 Hub](https://hub.docker.com) without signing in or even having an 18 account. However, in order to `push` images, leave comments or to *star* 19 a repository, you are going to need a [Docker 20 Hub](https://hub.docker.com) account. 21 22 ### Registration for a Docker Hub account 23 24 You can get a [Docker Hub](https://hub.docker.com) account by 25 [signing up for one here](https://hub.docker.com/account/signup/). A valid 26 email address is required to register, which you will need to verify for 27 account activation. 28 29 ### Email activation process 30 31 You need to have at least one verified email address to be able to use your 32 [Docker Hub](https://hub.docker.com) account. If you can't find the validation email, 33 you can request another by visiting the [Resend Email Confirmation]( 34 https://hub.docker.com/account/resend-email-confirmation/) page. 35 36 ### Password reset process 37 38 If you can't access your account for some reason, you can reset your password 39 from the [*Password Reset*](https://hub.docker.com/account/forgot-password/) 40 page. 41 42 ## Organizations and groups 43 44 A Docker Hub organization contains public and private repositories just like 45 a user account. Access to push, pull or create these organisation owned repositories 46 is allocated by defining groups of users and then assigning group rights to 47 specific repositories. This allows you to distribute limited access 48 Docker images, and to select which Docker Hub users can publish new images. 49 50 ### Creating and viewing organizations 51 52 You can see what organizations [you belong to and add new organizations]( 53 https://hub.docker.com/account/organizations/) from the Account Settings 54 tab. They are also listed below your user name on your repositories page 55 and in your account profile. 56 57 ![organizations](/docker-hub/hub-images/orgs.png) 58 59 ### Organization groups 60 61 Users in the `Owners` group of an organization can create and modify the 62 membership of groups. 63 64 Unless they are the organization's `Owner`, users can only see groups of which they 65 are members. 66 67 ![groups](/docker-hub/hub-images/groups.png) 68 69 ### Repository group permissions 70 71 Use organization groups to manage the users that can interact with your repositories. 72 73 You must be in an organization's `Owners` group to create a new group, Hub 74 repository, or automated build. As an `Owner`, you then delegate the following 75 repository access rights to groups: 76 77 | Access Right | Description | 78 |--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| 79 | `Read` | Users with this right can view, search, and pull a private repository. | 80 | `Write` | Users with this right can push to non-automated repositories on the Docker Hub. | 81 | `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. | 82 | | | 83 84 Regardless of their actual access rights, users with unverified email addresses 85 have `Read` access to the repository. Once they have verified their address, 86 they have their full access rights as granted on the organization.