mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-18 11:15:12 +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:
co-authored by
Marco A.
parent
319c466476
commit
cc7a6145f1
@@ -12,11 +12,11 @@ Domain discovery is typically used in [B2B](./b2b) or [SaaS](./saas) scenarios w
|
||||

|
||||
|
||||
In the example there is a service provider with a ZITADEL instance running on a [Custom Domain](/guides/manage/cloud/instances#add-custom-domain) on `login.mycompany.com`.
|
||||
By default all users login on the organization **CIAM** with their preferred social login provider.
|
||||
By default, all users login on the organization **CIAM** with their preferred social login provider.
|
||||
|
||||
Users of the two business customers **Alpha** and **Beta** should login according to their organization login and access policy settings.
|
||||
In case of Alpha users will login via an external identity provider (eg, [Entra ID](/guides/integrate/identity-providers/azure-ad-oidc)).
|
||||
Beta users must only login with username/password and MFA instead.
|
||||
Users of the two business customers **Alpha** and **Beta** should log in, according to their organization login and access policy settings.
|
||||
In the case of Alpha, users will log in via an external identity provider (eg, [Entra ID](/guides/integrate/identity-providers/azure-ad-oidc)).
|
||||
Beta users must only log in with username/password and MFA instead.
|
||||
|
||||
For this scenario you need to route the user `[email protected]` to the **Alpha Organization** and `[email protected]` to the **Beta Organization** respectively.
|
||||
|
||||
@@ -78,13 +78,13 @@ In case multiple providers are configured, then the user will be prompted to sel
|
||||
|
||||
Users of **Beta** must create an account and login with password and 2FA.
|
||||
|
||||
In the organization settings under Login Behavior and Access make sure the following settings are applied:
|
||||
In the organization settings under `Login Behavior and Access`, make sure the following settings are applied:
|
||||
|
||||
- **Username Password allowed**: Enabled
|
||||
- **Register allowed**: Disabled - you may want [Managers](/concepts/structure/managers) to setup accounts.
|
||||
- **Register allowed**: Disabled - you may want [Administrators](/concepts/structure/administrators) to set up accounts.
|
||||
- **External IDP allowed**: Disabled
|
||||
|
||||
Make sure to [Force MFA](/guides/manage/console/default-settings#multifactor-mfa) so that users must setup a second factor for authentication.
|
||||
Make sure to [Force MFA](/guides/manage/console/default-settings#multifactor-mfa) so that users must set up a second factor for authentication.
|
||||
|
||||
### Verify domains
|
||||
|
||||
@@ -108,7 +108,7 @@ The user journeys for the different users would look as follows:
|
||||
|
||||
Chuck
|
||||
|
||||
1. Select Google button
|
||||
1. Select the Google button
|
||||
1. Redirect to Google IDP
|
||||
1. Chuck logs in with Google credentials
|
||||
1. Redirected back to your application
|
||||
|
||||
@@ -3,17 +3,17 @@ title: Prevent users from accessing ZITADEL Management Console
|
||||
sidebar_label: Limit access to management console
|
||||
---
|
||||
|
||||
ZITADEL includes a management console that allows Managers to configure all resources. All uses, including end-users, by default, view and manage their profile information.
|
||||
ZITADEL includes a management console that allows Administrators to configure all resources. All uses, including end-users, by default, view and manage their profile information.
|
||||
In some use cases you want to prevent users from accessing the management console, this could be:
|
||||
- User management is integrated into your own app
|
||||
- Users login via SSO and should not be able to change their data in the Management Console
|
||||
- Only managers should be able to access Management Console to manage their users
|
||||
- Only administrators should be able to access Management Console to manage their users
|
||||
|
||||
At the moment it is not possible to simply disable the Management Console, but with the configuration described in this guide, you can prevent users from accessing the Console.
|
||||
|
||||
## Self-hosted
|
||||
|
||||
If you are running ZITADEL self-hosted, we recommend restricting the access to ZITADEL Management Console via WAF/reverse-proxy for Non-Manager users
|
||||
If you are running ZITADEL self-hosted, we recommend restricting the access to ZITADEL Management Console via WAF/reverse-proxy for Non-Administrator users
|
||||
|
||||
## ZITADEL Cloud (and self-hosted)
|
||||
|
||||
@@ -33,7 +33,7 @@ By default, this setting is disabled, so all users can access the project.
|
||||
|
||||

|
||||
|
||||
Start by granting the organization of your managers, that should be able to access the Management Console, the [default project](/guides/manage/console/projects-overview#the-default-project):
|
||||
Start by granting the organization of your administrators that should be able to access the Management Console, the [default project](/guides/manage/console/projects-overview#the-default-project):
|
||||
|
||||
1. Click on the default-project > Grants > New +
|
||||

|
||||
@@ -49,9 +49,9 @@ To avoid accidental lock-out, the [default project](/guides/manage/console/proje
|
||||
|
||||
You need to use the [update project API call](/reference/api/management/zitadel.management.v1.ManagementService.UpdateProject) to set the configuration on the project.
|
||||
|
||||
First, you need a user with manager permissions to change the project settings in that organization.
|
||||
This means either you add the manager to the organization or you use a manager on the instance level with "IAM-OWNER" permissions.
|
||||
After that create a Personal Access Token (PAT) for the manager.
|
||||
First, you need a user with administrator permissions to change the project settings in that organization.
|
||||
This means either you add the manager to the organization or you use an administrator on the instance level with "IAM-OWNER" permissions.
|
||||
After that create a Personal Access Token (PAT) for the administrator.
|
||||
|
||||
More detailed information about creating a PAT and administrator roles you can find [here](/guides/integrate/service-accounts/personal-access-token)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user