mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-05 22:02:15 +00:00
chore: rename manager/member to administrator (#11542)
# Which Problems Are Solved As part of the naming consistency initiative, the terms `Manager`, `Member` and other similar terms that are used in the context of an administrator are replaced by `Administrator` in the UI and documentation. # How the Problems Are Solved By replacing the following terms with Administrator / Administrator Roles in docs, Console UI, and guides. - Manager - Add Manager - Add a Manager - Administrator (used as a person type) - Membership - Member grants # Additional Changes minor grammatical edits in the docs # Additional Context - Closes https://github.com/zitadel/zitadel/issues/11291 --------- Co-authored-by: Marco A. <[email protected]>
This commit is contained in:
Gayathri Vijayan
co-authored by
Marco A.
Marco A.
parent
319c466476
commit
cc7a6145f1
@@ -0,0 +1,12 @@
|
||||
Administrators are [users or service accounts](/guides/manage/console/users-overview) who have permission to manage resources within ZITADEL.
|
||||
|
||||
Administrator permissions can be assigned to different levels in ZITADEL:
|
||||
|
||||
- **IAM Administrators**: This is the highest level. Users with IAM Administrator roles are able to manage the whole [Instance](/concepts/structure/instance).
|
||||
- **Organization Administrators**: Administrators at the Organization level are able to view or manage everything, according to their permissions, within the granted [Organization](/guides/manage/console/organizations-overview).
|
||||
- **Project Administrators**: In this level the user is able to manage a [project](/guides/manage/console/projects-overview).
|
||||
- **Project Grant Administrators**: The project grant administrator manages [projects granted](/concepts/structure/granted_projects) by another organization.
|
||||
|
||||
The scope of the administrators is restricted based on their level.
|
||||
Which means that an administrator, assigned to one organization, will have access only to the resources and configurations of that organization.
|
||||
Only the Administrators on the instance level can view resources, such as users, across all organizations.
|
||||
@@ -1,12 +0,0 @@
|
||||
Managers are [users or service accounts](/guides/manage/console/users-overview) who have permission to manage resources within ZITADEL.
|
||||
|
||||
Manager permissions can be assigned to different levels in ZITADEL:
|
||||
|
||||
- **IAM Managers**: This is the highest level. Users with IAM Administrator roles are able to manage the whole [Instance](/concepts/structure/instance).
|
||||
- **Org Managers**: Managers in the Organization Level are able to view or manage everything, according to their permissions, within the granted [Organization](/guides/manage/console/organizations-overview).
|
||||
- **Project Mangers**: In this level the user is able to manage a [project](/guides/manage/console/projects-overview).
|
||||
- **Project Grant Manager**: The project grant manager is for [granted projects](/concepts/structure/granted_projects) by another organization.
|
||||
|
||||
The scope of the managers is restricted based on their level.
|
||||
Which means that a Manager, assigned to one organization, will have access only to the resources and configurations of that organization.
|
||||
Only the Managers on the instance level can view resources, such as users, across all organizations.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
title: Administrators
|
||||
sidebar_label: Administrators
|
||||
---
|
||||
|
||||
import AdministratorDescription from "./_administrator_description.mdx";
|
||||
|
||||
<AdministratorDescription components={props.components} name="AdministratorDescription" />
|
||||
|
||||
Notes:
|
||||
|
||||
- Read our [guide on Administrators](../../guides/manage/console/administrators) to learn more about the role concept and how to use Administrator roles in ZITADEL.
|
||||
- [API reference](/apis/resources/mgmt/management-service-list-org-member-roles) for Administrators on the organization level
|
||||
@@ -20,7 +20,7 @@ ZITADEL supports the following application types:
|
||||
Ensure the configuration of application settings is limited to authorized users only.
|
||||
|
||||
You can configure applications in the [management console](/guides/manage/console/organizations-overview).
|
||||
Read about our [managers](/concepts/structure/managers) and [granted projects](/concepts/structure/granted_projects)
|
||||
Read about our [administrators](/concepts/structure/administrators) and [granted projects](/concepts/structure/granted_projects)
|
||||
concepts.
|
||||
|
||||
## References
|
||||
|
||||
@@ -8,6 +8,6 @@ title: Structure
|
||||
<Card href="/concepts/structure/projects" title="Projects" />
|
||||
<Card href="/concepts/structure/applications" title="Applications" />
|
||||
<Card href="/concepts/structure/users" title="Users" />
|
||||
<Card href="/concepts/structure/managers" title="Managers" />
|
||||
<Card href="/concepts/structure/administrators" title="Administrators" />
|
||||
<Card href="/concepts/structure/policies" title="Policies" />
|
||||
</Cards>
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Managers
|
||||
sidebar_label: Managers
|
||||
---
|
||||
|
||||
import ManagerDescription from "./_manager_description.mdx";
|
||||
|
||||
<ManagerDescription components={props.components} name="ManagerDescription" />
|
||||
|
||||
Notes:
|
||||
|
||||
- Read our [guide on Managers](../../guides/manage/console/managers) to learn more about the role concept and how to use Administrator roles in ZITADEL.
|
||||
- [API reference](/apis/resources/mgmt/management-service-list-org-member-roles) for Managers on the organization level
|
||||
@@ -25,9 +25,9 @@ The main difference between users and service accounts is the type of credential
|
||||
|
||||
Learn how to [use service accounts](/guides/integrate/service-accounts/authenticate-service-accounts) with ZITADEL.
|
||||
|
||||
### Managers
|
||||
### Administrators
|
||||
|
||||
Any user or service account can be given a [Manager](/concepts/structure/managers) role.
|
||||
Any user or service account can be assigned an [Administrator](/concepts/structure/administrators) role.
|
||||
A user with an administrator role is not only an end-user of ZITADEL but can also manage certain aspects of ZITADEL itself.
|
||||
|
||||
### Federated users
|
||||
@@ -59,7 +59,7 @@ Consider this general recommendation as a starting point:
|
||||
- Create one organization ("default organization") for your own company
|
||||
- Configure projects and applications in the default organization
|
||||
- Structure users in organizations based on common domains that are self-managed (eg, company)
|
||||
- Grant your projects to the organizations, allow Managers to give granted roles to their users
|
||||
- Grant your projects to the organizations, allow Administrators to give granted roles to their users
|
||||
|
||||
You might want to adjust this general setup based on your [scenario](/guides/solution-scenarios).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user