Documentation Users Create User
Detailed guide

Create User

The user creation form for inviting or adding a workspace member.

Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Add users with the least privilege needed for their job, then expand only if required.

Put it into practice

  1. Start by confirming this person needs workspace access and identifying the minimum role they require.

    InteractionsUsers page: click New User only after role intent is clear.

  2. Enter identity fields accurately so account recovery and audit trails remain reliable.

    InteractionsCreate User form: complete username, email, and required identity fields.

  3. Assign role and activation settings deliberately to enforce least privilege from day one.

    InteractionsCreate User form: choose role/access controls and account activation options.
    Open workflow: Roles

  4. Save and validate the new account appears with expected status and role in users list.

    InteractionsAfter save, return to Users table and verify row values.

  5. If onboarding includes password support, confirm reset or first-login guidance path.

    InteractionsUsers row actions: verify reset-password pathway if required.
    Open workflow: Reset Password Modal

What to review

Page header and breadcrumb

Confirms whether you are creating or editing, gives you the back path, and is the quickest way to avoid updating the wrong record.

Primary form sections

The form is grouped so you can complete one block at a time instead of hunting for every field in a single long screen.

Required inputs and field labels

Every required label tells you what must exist before the record can be saved; blank or invalid values should be corrected before moving on.

Validation and inline errors

Use these messages as instructions, not warnings to dismiss. They tell you exactly which field blocks save and why.

Primary save action

Commits the record only after the form validates. Use it after reviewing every section because it is the action that changes workspace data.

Cancel or return action

Leaves the form and takes you back without finishing the workflow. Use it when you opened the wrong record or need to check related data first.

Identity fields

These fields define who the account belongs to.

Role and access fields

Use the role fields carefully because they decide what the new user can see and do.

Activation controls

Activation settings determine whether the user can start working immediately.

Guardrails

  • Identity and role fields must be complete before the user can be created.
  • Only workspace admins should be able to add users.

If it starts drifting

  • If the intended role is missing, review role administration instead of improvising with the wrong permission bundle.