mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-14 09:55:12 +00:00
+6








07ce3b6905
This PR summarizes multiple changes specifically only available with ZITADEL v3: - feat: Web Keys management (https://github.com/zitadel/zitadel/pull/9526) - fix(cmd): ensure proper working of mirror (https://github.com/zitadel/zitadel/pull/9509) - feat(Authz): system user support for permission check v2 (https://github.com/zitadel/zitadel/pull/9640) - chore(license): change from Apache to AGPL (https://github.com/zitadel/zitadel/pull/9597) - feat(console): list v2 sessions (https://github.com/zitadel/zitadel/pull/9539) - fix(console): add loginV2 feature flag (https://github.com/zitadel/zitadel/pull/9682) - fix(feature flags): allow reading "own" flags (https://github.com/zitadel/zitadel/pull/9649) - feat(console): add Actions V2 UI (https://github.com/zitadel/zitadel/pull/9591) BREAKING CHANGE - feat(webkey): migrate to v2beta API (https://github.com/zitadel/zitadel/pull/9445) - chore!: remove CockroachDB Support (https://github.com/zitadel/zitadel/pull/9444) - feat(actions): migrate to v2beta API (https://github.com/zitadel/zitadel/pull/9489) --------- Co-authored-by: Livio Spring <[email protected]> Co-authored-by: Stefan Benz <[email protected]> Co-authored-by: Silvan <[email protected]> Co-authored-by: Ramon <[email protected]> Co-authored-by: Elio Bischof <[email protected]> Co-authored-by: Kenta Yamaguchi <[email protected]> Co-authored-by: Harsha Reddy <[email protected]> Co-authored-by: Livio Spring <[email protected]> Co-authored-by: Max Peintner <[email protected]> Co-authored-by: Iraq <[email protected]> Co-authored-by: Florian Forster <[email protected]> Co-authored-by: Tim Möhlmann <[email protected]> Co-authored-by: Copilot <[email protected]> Co-authored-by: Max Peintner <[email protected]>
49 lines
3.2 KiB
Plaintext
49 lines
3.2 KiB
Plaintext
To create a new user, go to Users and click on **New**. Enter the required contact details and save by clicking “Create”.
|
|
|
|
import Tabs from "@theme/Tabs";
|
|
import TabItem from "@theme/TabItem";
|
|
|
|
:::note
|
|
If you started with Zitadel before version 3, you might have the "Human User [deprecated]" UI.
|
|
In this case please enable the Feature Flag "Use V2 Api in Console for User creation" in the Default Settings.
|
|
:::
|
|
|
|
<Tabs>
|
|
<TabItem value="human" label="Human User" default>
|
|
<img src="/docs/img/guides/console/invitehuman.png" width="680px" alt="Invite Human" />
|
|
|
|
When creating a new user you have different options.
|
|
First add the email, and select if the email address should be added automatically as "verified".
|
|
|
|
In the last section you can choose the authentication options:
|
|
- **Setup authentication later for this user**: This flow might be useful if an employee starts at a later point but you already want to prepare the account. The user will not have an authentication method, before they will be able to login, they need to setup a method.
|
|
- **Send an invitation E-Mail for authentication setup and E-Mail verification**: The user will receive an email and be able to setup an authentication method (e.g Password, Passkey, External SSO).
|
|
- When using the [Zitadel Login V1](/docs/guides/integrate/login/hosted-login) the user will be prompted to setup a password
|
|
- When using the [Zitadel Login V2](/docs/guides/integrate/login/hosted-login#hosted-login-version-2-beta) the user has the option to choose the authentication method (password, passkey, identity provider), based on the configuration of the organization
|
|
<img src="/docs/img/guides/console/setupauthmethod.png" width="680px" alt="Invite Human - Setup authentication method" />
|
|
- **Set an initial password for the user**: The user will receive an email and be able to setup an authentication method (e.g Password, Passkey, External SSO)
|
|
|
|
</TabItem>
|
|
<TabItem value="human_deprecated" label="Human User [deprecated]">
|
|
<img src="/docs/img/guides/console/addhuman.png" width="680px" alt="Add Human" />
|
|
|
|
After a human user is created, by default, an initialization mail with a code is sent to the registered email. This code then has to be verified on first login.
|
|
If you want to omit this mail, you can check the **email verified** and **set initial password** toggle.
|
|
If no password is set initially, the initialization mail prompting the user to set his password is sent.
|
|
|
|
</TabItem>
|
|
<TabItem value="service" label="Service User">
|
|
<img
|
|
src="/docs/img/guides/console/addmachine.png"
|
|
width="540px"
|
|
alt="Add Service User"
|
|
/>
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
You can prompt the user to add a second factor method too by checking the **Force MFA** toggle in [Login behaviour settings](/docs/guides/manage/console/default-settings#login-behavior-and-access).
|
|
|
|
When logged in, a user can then manage the profile in the console, adding a profile picture, external IDPs and Passwordless authentication devices.
|
|
|
|
<img src="/docs/img/guides/console/myprofile.png" alt="Profile Self Manage" />
|