mirror of https://github.com/docker/docs.git
admin: clarification for company owner seats (#22440)
## Description - Company owners do not normally occupy seats, but there are some caveats where they might (SSO is enabled or they are a member of an org) - Updated company owners doc, and FAQ ## Related issues or tickets - [ENGDOCS-2562](https://docker.atlassian.net/browse/ENGDOCS-2562?atlOrigin=eyJpIjoiMGZiNGEyMDRkNDNmNDE5MWI5YTZlN2VkMWFkMDM1MjkiLCJwIjoiaiJ9) ## Reviews - [ ] Editorial review [ENGDOCS-2562]: https://docker.atlassian.net/browse/ENGDOCS-2562?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
This commit is contained in:
parent
a996f877f9
commit
060688a95e
|
@ -12,8 +12,14 @@ A company can have multiple owners. Company owners have company-wide
|
|||
observability and can manage company-wide settings that apply to all associated
|
||||
organizations. In addition, company owners have the same access as organization
|
||||
owners for all associated organizations. Unlike organization owners, company
|
||||
owners don't need to be member of an organization. When company owners aren't a
|
||||
member in an organization, they don't occupy a seat.
|
||||
owners don't need to be member of an organization.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Company owners do not occupy a seat unless one of the following is true:
|
||||
>
|
||||
> - They are added as a member of an organization under your company
|
||||
> - SSO is enabled
|
||||
|
||||
## Add a company owner
|
||||
|
||||
|
|
|
@ -32,14 +32,22 @@ You can add a maximum of 10 company owners to a single company account.
|
|||
|
||||
### Do company owners occupy a subscription seat?
|
||||
|
||||
Company owners don't occupy a seat in any organization unless they are added as a
|
||||
member of the organization. Since company owners have the same access as
|
||||
organization owners for all organizations associated with the company, it is not
|
||||
necessary to add company owners to an organization.
|
||||
Company owners do not occupy a seat unless one of the following is true:
|
||||
|
||||
Note that when you first create a company, your account will be both a company
|
||||
owner and an organization owner. Your account will occupy a seat as long as
|
||||
you're an organization owner.
|
||||
- They are added as a member of an organization under your company
|
||||
- SSO is enabled
|
||||
|
||||
Although company owners have the same access as organization owners across all
|
||||
organizations in the company, it's not necessary to add them to any
|
||||
organization. Doing so will cause them to occupy a seat.
|
||||
|
||||
When you first create a company, your account is both a company owner and an
|
||||
organization owner. In that case, your account will occupy a seat as long as
|
||||
you remain an organization owner.
|
||||
|
||||
To avoid occupying a seat, [assign another user as the organization owner](/manuals/admin/organization/members.md#update-a-member-role) and remove yourself from the organization.
|
||||
You'll retain full administrative access as a company owner without using a
|
||||
subscription seat.
|
||||
|
||||
### What permissions does the company owner have in the associated/nested organizations?
|
||||
|
||||
|
|
Loading…
Reference in New Issue