mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-23 16:02:14 +00:00
Marco A.andGitHub
382aec2d61
# Which Problems Are Solved Inconsistent naming of service account, found in the following variations: - Machine User - machine user - Service User - Machine Account - Technical Account - User: Type Machine # How the Problems Are Solved Attentive search and replace. Localizations have been translated using Copilot # Additional Changes Some unused methods have been removed from the Go code. # Additional Context - Closes #11285
46 lines
3.1 KiB
Plaintext
46 lines
3.1 KiB
Plaintext
To create a new user, go to Users and click on **New**. Enter the required contact details and save by clicking “Create”.
|
|
|
|
<Callout>
|
|
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 Management Console for User creation" in the Default Settings.
|
|
</Callout>
|
|
|
|
<Tabs>
|
|
<Tab 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](/guides/integrate/login/hosted-login) the user will be prompted to setup a password
|
|
- When using the [Zitadel Login V2](/guides/integrate/login/hosted-login#hosted-login-version-2) 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)
|
|
|
|
</Tab>
|
|
<Tab value="human_deprecated" label="Human User [deprecated]">
|
|
<img src="/docs/img/guides/console/addhuman.png" width="680px" alt="Add Human" />
|
|
|
|
After a 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.
|
|
|
|
</Tab>
|
|
<Tab value="service" label="Service Account">
|
|
<img
|
|
src="/docs/img/guides/console/addmachine.png"
|
|
width="540px"
|
|
alt="Add Service Account"
|
|
/>
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
You can prompt the user to add a second factor method too by checking the **Force MFA** toggle in [Login behaviour settings](/guides/manage/console/default-settings#login-behavior-and-access).
|
|
|
|
When logged in, a user can then manage the profile in the management console, adding a profile picture, external IDPs and Passkeys.
|
|
|
|
<img src="/docs/img/guides/console/myprofile.png" alt="Profile Self Manage" />
|