_index.md

title	Administration
description	Overview of administration features and roles in the Docker Admin Console
keywords	admin, administration, company, organization, Admin Console, user accounts, account management
weight	10
params	sidebar group Enterprise
grid	title description icon link Company administration Explore how to manage a company. apartment /admin/company/ title description icon link Organization administration Learn about organization administration. store /admin/organization/ title description icon link Onboard your organization Learn how to onboard and secure your organization. explore /admin/organization/onboard title description icon link Company FAQ Discover common questions and answers about companies. help /faq/admin/company-faqs/ title description icon link Organization FAQ Explore popular FAQ topics about organizations. help /faq/admin/organization-faqs/ title description icon link Security Explore security features for administrators. shield_locked /security/
aliases	/docker-hub/admin-overview

Administrators start with the Docker Admin Console to provision user seats, manage access tokens, SSO and SCIM, and deploy Docker Desktop to their organizations.

Set up Docker with Admin Console

Administrators get started with Docker by accessing the Admin Console to create a company and organizations.

• If you're a Docker Business subscriber, you have access to both company and organization features.
• If you're Docker Team subscriber, you have access to organization features.

Company and organization hierarchy

Admin Console gives administrators a bird's eye view of who has access to Docker. There are two levels of visibility, company and organizations, and they have a hierarchical relationship:

Company

The highest level of visibility an administrator can have is at the company level. A company owner views and manages all organizations within the company and has full access to company-wide settings.

Organization

An organization contains teams and repositories. Organization owners manage organization settings, users, and access controls.

• All Docker Team and Business subscribers must create one organization before inviting new members to Docker.
• All organizations owners occupy one seat, but can occupy more than one seat if they're members or owners of multiple, separate organizations.
• Unlike a company, an organization is discrete from other organizations and cannot inherit permissions in bulk from other organizations.

If you're a Docker team subscriber who wants access to company-level permissions, you can upgrade to Docker Business.

Seats and user management

The number of seats an administrator can provision depends on their subscription type. Administrators can act as company or organization owners who can invite users with their email addresses, then assign them member roles to particular teams.

Company and organization owners

Administrators can occupy company owner or organization owner roles (or both), where each role has its own permissions and seat rules.

• Company owners can view and bulk edit settings and configurations for all organizations beneath them.
• Company owners won't occupy a seat unless SSO is enabled, or they're a member of an organization within the company.
• Organization owners have full admin permissions to manage settings, members, roles, and teams within their organization, but not organizations they're not part of.

When an administrator creates the first company or organization from Admin Console, they assume owner roles for the company and/or the organization by default.

Seats

A seat is a unit purchased with a subscription plan that extends access to users to an organization's repo.

• They give administrators granular permissions around who can contribute to a repository.
• They prevent unauthorized users from pushing to a repos they're not members of.

For example, an organization owner takes up one seat. They can invite Docker users to an organization. Once invitees become members, organization owners can set permissions to members of their company or organization.

Users and members

Docker uses specific terminology to define user access:

• A user is someone with a Docker ID.
  • They're not necessarily affiliated with an organization.
  • They do not occupy a seat by default.
• An invitee is a user invited to an organization.
  • Invitees occupy one seat.
  • It behaves as a user state before accepting and joining an organization.
• A member is a user who accepted an invitation to an organization.
• Teams let you group members together.
  • They are optional.
  • They allow you to assign repository permissions in bulk.
  • Teams can simplify permission management across projects or functions.

Manage companies and organizations

Learn how to manage companies and organizations in the following sections.

{{< grid >}}