Docker Organizations: Seats, Permissions, and Registries FAQs

### Our users create Docker Hub accounts through self-service. How do we know when the total number of users for the requested licenses has been met? Is it possible to add more members to the organization than the total number of licenses? There isn't any automatic notification when the total number of users for the requested licenses has been met. However, if the number of team members exceed the number of licenses, you will receive an error informing you to contact the administrator due to lack of seats. You can [add seats](../../subscription/manage-seats.md) if needed. ### How can I merge organization accounts? You can downgrade a secondary organization and transition your users and data to a primary organization. See [Merge organizations](../organization/orgs.md#merge-organizations). ### Do organization invitees take up seats? Yes. A user invited to an organization will take up one of the provisioned seats, even if that user hasn’t accepted their invitation yet. Organization owners can manage the list of invitees through the **Invitees** tab on the organization settings page in Docker Hub, or in the **Members** page in Admin Console. ### Do organization owners take a seat? Yes. Organization owners will take up a seat. ### What is the difference between user, invitee, seat, and member? User refers to a Docker user with a Docker ID. An invitee is a user that an administrator has invited to join an organization but has not yet accepted their invitation. Seats are the number of planned members within an organization. Member may refer to a user who has received and accepted an invitation to join an organization. Member can also refer to a member of a team within an organization. ### If there are two organizations and a user belongs to both organizations, do they take up two seats? Yes. In a scenario where a user belongs to two organizations, they take up one seat in each organization. ### Is it possible to set permissions for repositories within an organization? Yes. You can configure repository access on a per-team basis. For example, you can specify that all teams within an organization have **Read and Write** access to repositories A and B, whereas only specific teams have **Admin** access. Org owners have full administrative access to all repositories within the organization. See [Configure repository permissions for a team](manage-a-team.md#configure-repository-permissions-for-a-team). Administrators can also assign members the editor role, which grants administrative permissions for repositories across the namespace of the organization. See [Roles and permissions](../../security/for-admins/roles-and-permissions.md). ### Does my organization need to use Docker's registry? A registry is a hosted service containing repositories of images that responds to the Registry API. Docker Hub is Docker's primary registry, but you can use Docker with other container image registries. You can access the default registry by browsing to [Docker Hub](https://hub.docker.com) or using the `docker search` command.

This section addresses common questions about Docker organizations, including how seat allocation works with self-service accounts and multiple organizations, the difference between users, invitees, seats, and members, and the ability to configure repository permissions on a per-team basis. It also clarifies whether organizations are required to use Docker's registry.