mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-20 11:58:47 +00:00
docs: fixed some typos, formatting, grammar (#11540)
# Which Problems Are Solved - Typos - Punctuation - Markdown table formatting - ... (A bunch of issues my editor gave) # How the Problems Are Solved # Additional Changes # Additional Context
This commit is contained in:
@@ -16,7 +16,7 @@ In a second step fill out your user data like First-, Last- and Team-name.
|
||||
|
||||

|
||||
|
||||
If you did start with your email instead of a social login (e.g Google) you have to fill a password for your authentication.
|
||||
If you did start with your email instead of a social login (e.g. Google) you have to fill a password for your authentication.
|
||||
In that case you will get an initialization mail to verify your account.
|
||||
|
||||

|
||||
|
||||
@@ -18,9 +18,9 @@ You can specify a timeout and whether the action is allowed to fail too.
|
||||
<img src="/docs/img/guides/console/action.png" alt="Create Action" width="450px" />
|
||||
|
||||
To run those scripts, a flow with a trigger has to be created.
|
||||
This could for example be a **External Authentication** Flow, with a **Post Authentication** trigger.
|
||||
This could for example be an **External Authentication** Flow, with a **Post Authentication** trigger.
|
||||
|
||||
<img src="/docs/img/guides/console/flow.png" alt="Flow" width="400px" />
|
||||
|
||||
Now whenever a user gets authenticated externally with an IDP, a action is triggered after the authentication itself.
|
||||
Now whenever a user gets authenticated externally with an IDP, an action is triggered after the authentication itself.
|
||||
If you want to know more where actions can be useful, take a look at the feature [here](/concepts/features/actions) or directly jump to an example of a custom behavior [here](/guides/manage/customize/behavior).
|
||||
|
||||
@@ -20,7 +20,7 @@ In the right part of the management console you can find **ADMINISTRATORS** in t
|
||||
## Roles
|
||||
|
||||
| Name | Role | Description |
|
||||
| ----------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------ |
|
||||
|-------------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------|
|
||||
| Instance Owner | IAM_OWNER | Manage the Instance, manage all organizations with their content |
|
||||
| Instance Owner Viewer | IAM_OWNER_VIEWER | View the Instance and view all organizations with their content |
|
||||
| Instance Org Manager | IAM_ORG_MANAGER | Manage all organizations including their policies, projects and users |
|
||||
|
||||
@@ -266,7 +266,7 @@ If an account is locked, the administrator has to unlock it in the ZITADEL Manag
|
||||
|
||||
### Add organization domain as suffix to loginnames
|
||||
|
||||
If you enable this setting, all loginnames will be suffixed with the organization domain. If this settings is disabled, you have to ensure that usernames are unique over all organizations.
|
||||
If you enable this setting, all loginnames will be suffixed with the organization domain. If this setting is disabled, you have to ensure that usernames are unique over all organizations.
|
||||
|
||||
### Validate Org domains
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ Depending on your use case, multiple organizations can be created (B2B) or you c
|
||||
width="400px"
|
||||
/>
|
||||
|
||||
If your new to management console, you'll probably want to set some settings initially. Continue reading Default settings on the next page.
|
||||
If you're new to management console, you'll probably want to set some settings initially. Continue reading Default settings on the next page.
|
||||
|
||||
## Prevent management console access
|
||||
|
||||
|
||||
@@ -16,17 +16,17 @@ Before you start, make sure you have everything set up correctly.
|
||||
## Copy some information for the action
|
||||
|
||||
1. Select the **Projects** navigation item.
|
||||
1. Select a project that has a role configured.
|
||||
1. Copy the projects **Resource Id** on the screens top right.
|
||||
1. Scroll to the **ROLES** section and note some roles key.
|
||||
2. Select a project that has a role configured.
|
||||
3. Copy the projects **Resource ID** on the screens top right.
|
||||
4. Scroll to the **ROLES** section and note some roles key.
|
||||
|
||||
## Create the action
|
||||
|
||||
1. Select the **Actions** navigation item.
|
||||
1. In the **Actions <i className="las la-code"></i>** section, select the **+ New** button.
|
||||
1. Give the new action the name `addGrant`.
|
||||
1. Paste this snippet into the multiline textfield.
|
||||
1. Replace the snippets placeholders and select **Save**.
|
||||
2. In the **Actions <i className="las la-code"></i>** section, select the **+ New** button.
|
||||
3. Give the new action the name `addGrant`.
|
||||
4. Paste this snippet into the multiline text-field.
|
||||
5. Replace the snippets placeholders and select **Save**.
|
||||
|
||||
```js reference
|
||||
https://github.com/zitadel/actions/blob/main/examples/add_user_grant.js
|
||||
@@ -37,10 +37,10 @@ https://github.com/zitadel/actions/blob/main/examples/add_user_grant.js
|
||||
Now, make the action hook into the [external authentication flow](/apis/actions/external-authentication).
|
||||
|
||||
1. In the **Flows <i className="las la-exchange-alt"></i>** section, select the **+ New** button.
|
||||
1. Select the **Flow Type** _External Authentication_.
|
||||
1. Select the **Trigger Type** _Post Creation_.
|
||||
1. In the **Actions** dropdown, check _addGrant_.
|
||||
1. Select the **Save** button.
|
||||
2. Select the **Flow Type** _External Authentication_.
|
||||
3. Select the **Trigger Type** _Post Creation_.
|
||||
4. In the **Actions** dropdown, check _addGrant_.
|
||||
5. Select the **Save** button.
|
||||
|
||||
New users automatically are assigned a role now if they register by authenticating with an external identity provider.
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ The best way is to upload a ttf file after a successful upload you will see it i
|
||||
|
||||
### Advanced Settings
|
||||
|
||||
In the advanced behavior you can choose if the loginname suffix (domain e.g [email protected]) should be shown in the loginname screen or not and if the “ZITADEL watermark” should be hidden.
|
||||
In the advanced behavior you can choose if the loginname suffix (domain e.g. [email protected]) should be shown in the loginname screen or not and if the “ZITADEL watermark” should be hidden.
|
||||
|
||||
## Trigger the private labeling for the login
|
||||
|
||||
@@ -44,7 +44,7 @@ If you like to trigger your settings for your applications you have different po
|
||||
### 1. Primary Domain Scope
|
||||
|
||||
Send a [reserved scope](/apis/openidoauth/scopes) with your [authorization request](../../integrate/login/oidc/login-users) to trigger your organization.
|
||||
The primary domain scope will restrict the login to your organization, so only users of your own organization will be able to login.
|
||||
The primary domain scope will restrict the login to your organization, so only users of your own organization will be able to log in.
|
||||
|
||||
You can use our [OpenID Authentication Request Playground](https://zitadel.com/playgrounds/oidc) to learn more about how to trigger an [organization's policies and branding](https://zitadel.com/playgrounds/oidc#organization-policies-and-branding).
|
||||
|
||||
|
||||
@@ -6,13 +6,13 @@ You are able to customize the texts used from ZITADEL. This is possibly on the i
|
||||
|
||||
## Message Texts
|
||||
|
||||
Sometimes the users will get an email or phone message from ZITADEL (e.g Password Reset Request).
|
||||
Sometimes the users will get an email or phone message from ZITADEL (e.g. Password Reset Request).
|
||||
ZITADEL already has some good standard texts, but maybe you would like to customize it for your organization.
|
||||
|
||||
Go to the message text policy on your organization and you will find the different kinds of messages that are sent from ZITADEL.
|
||||
Go to the message text policy on your organization, and you will find the different kinds of messages that are sent from ZITADEL.
|
||||
Choose the template and the language you like to edit.
|
||||
You can now change all the texts from a message.
|
||||
As soon as you click into a input field you will see some attribute chips below the field.
|
||||
As soon as you click into an input field you will see some attribute chips below the field.
|
||||
These are the parameters you can include on this specific message.
|
||||
|
||||

|
||||
@@ -21,7 +21,7 @@ These are the parameters you can include on this specific message.
|
||||
|
||||
Like the message texts you are also able to change the texts on the login interface.
|
||||
First choose the screen and the language you like to edit.
|
||||
You will see the default texts in the input field and you can overwrite them by typing into the box.
|
||||
You will see the default texts in the input field, and you can overwrite them by typing into the box.
|
||||
|
||||

|
||||
|
||||
|
||||
Reference in New Issue
Block a user