docs: onboarding customers and users (#7105)

* docs: onboarding organizations * docs: onboarding organizations * docs: onboarding end users * docs: onboarding end users * docs: onboarding end users * docs: onboarding end users * docs: onboarding guide in console * docs: onboarding guide in console * docs: onboarding guide in console * docs: onboarding guide in console * docs: manually add user * docs: fix links * docs: fix links * Update docs/docs/guides/manage/console/_add_manager.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/_org_login_description.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/end-users.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/end-users.mdx Co-authored-by: mffap <[email protected]> * Update docs/docs/guides/solution-scenarios/onboarding/b2b.mdx Co-authored-by: mffap <[email protected]> * docs: correct review * docs: fix typos --------- Co-authored-by: mffap <[email protected]> Co-authored-by: Livio Spring <[email protected]>
2026-11-05 22:02:15 +00:00 · 2024-01-29 13:47:08 +01:00
parent 93f35980b8
commit 5e23ea55b2
34 changed files with 423 additions and 62 deletions
@@ -19,7 +19,7 @@ To address this, we are going to change this behavior so that users will be auto

 ## Statement

-This behaviour change was tracked in the following issue: [Reuse current session if no prompt is selected](https://github.com/zitadel/zitadel/issues/4841)
+This behavior change was tracked in the following issue: [Reuse current session if no prompt is selected](https://github.com/zitadel/zitadel/issues/4841)
 and released in version [v2.32.0](https://github.com/zitadel/zitadel/releases/tag/v2.32.0)

 ## Mitigation
@@ -20,7 +20,7 @@ To address this, we are going to change the behavior of the setting mentioned ab

 ## Statement

-This behaviour change was tracked in the following PR: [Restrict AllowRegistration check to local registration](https://github.com/zitadel/zitadel/pull/5939).
+This behavior change was tracked in the following PR: [Restrict AllowRegistration check to local registration](https://github.com/zitadel/zitadel/pull/5939).
 The change was part of version [v2.35.0](https://github.com/zitadel/zitadel/releases/tag/v2.35.0)

 ## Mitigation
@@ -14,7 +14,7 @@ When users are redirected to the ZITADEL Login-UI without any organizational con
 based on the instance settings, e.g. available IDPs and possible login mechanisms. If the user will then register himself,
 by the registration form or through an IDP, the user will always be created on the default organization.

-This behaviour led to confusion, e.g. when activating IDPs on default org would not show up in the Login-UI, because they would still be loaded from the instance settings.
+This behavior led to confusion, e.g. when activating IDPs on default org would not show up in the Login-UI, because they would still be loaded from the instance settings.

 To improve this, we're introducing the following change:
 If users are redirected to the Login-UI without any organizational context, they will be presented a login screen based on the settings of the default organization (incl. IDPs).
@@ -10,7 +10,7 @@ Date: 2023-10-14

 ## Description

-Due to storage optimisations ZITADEL changes the behaviour of sequences. 
+Due to storage optimisations ZITADEL changes the behavior of sequences. 
 This change improves command (create, update, delete) performance of ZITADEL.

 Sequences are no longer unique inside an instance.
@@ -23,7 +23,7 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10000">A-10000</a>
    </td>
    <td>Reusing user session</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
      The default behavior for users logging in is to be directed to the Select
      Account Page on the Login. With the upcoming changes, users will be
@@ -39,13 +39,13 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10001">A-10001</a>
    </td>
    <td>Login Policy - Allow Register</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
      When disabling the option, users are currently not able to register
      locally and also not through an external IDP. With the upcoming change,
      the setting will only prevent local registration. Restriction to Identity
      Providers can be managed through the corresponding IDP Template. No action
-      is required on your side if this is the intended behaviour or if you
+      is required on your side if this is the intended behavior or if you
      already disabled registration on your IDP.
    </td>
    <td>2.35.0</td>
@@ -75,7 +75,7 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10003">A-10003</a>
    </td>
    <td>Login-UI - Default Context</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
        When users are redirected to the ZITADEL Login-UI without any organizational context,
        they're currently presented a login screen, based on the instance settings,
@@ -91,9 +91,9 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10004">A-10004</a>
    </td>
    <td>Sequence uniquenes</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
-      Due to storage optimisations ZITADEL changes the behaviour of sequences. 
+      Due to storage optimisations ZITADEL changes the behavior of sequences.
      This change improves command (create, update, delete) performance of ZITADEL.
      Sequences are no longer unique inside an instance.
      From now on sequences are upcounting per aggregate id. 
@@ -123,7 +123,7 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10006">A-10006</a>
    </td>
    <td>Additional grant to cockroach database user</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
      Versions &gt;= 2.39.0 require the cockroach database user of ZITADEL to be granted to the `VIEWACTIVITY` grant. This can either be reached by grant the role manually or execute the `zitadel init` command.
    </td>
@@ -135,7 +135,7 @@ We understand that these advisories may include breaking changes, and we aim to
      <a href="./advisory/a10007">A-10007</a>
    </td>
    <td>Additional grant to cockroach database user</td>
-    <td>Breaking Behaviour Change</td>
+    <td>Breaking Behavior Change</td>
    <td>
      Upcoming Versions require the SYSTEM_OWNER role to be available in the permission role mappings. Self-hosting ZITADEL users who define custom permission role mappings need to make sure their system users don't lose access to the system API.
    </td>
@@ -165,7 +165,7 @@ As ZITADEL Cloud customer, you can also login to the <a href="https://zitadel.cl

 ## Categories

-### Breaking Behaviour Change
+### Breaking Behavior Change

 A breaking behavior change refers to a modification or update that changes the behavior of ZITADEL.
 This change does not necessarily affect the APIs or any functions you are calling, so it may not require an update to your code.