All guides
Admin

User

Create and edit accounts, assign roles, manage existing teams and review user activity.

Step-by-step guide

Before you start

Use an administrator account for this feature.

Open this feature

Open /admin/users on your application domain, or use the matching item in the application menu.

Steps

Sign in as an administrator who can manage users. Use an address controlled by the intended account owner. Decide whether you are creating an ordinary account or an administrator before setting access.

Create an ordinary user

  1. Open Users at /admin/users and select Create user. The create form is also at /admin/users/create.
  2. Enter Name, a unique Username, and the owner’s Email. For a practice account, use a name such as Training User and an inbox you control.
  3. Choose Locale if needed and select the user’s actual Timezone. Select language and Select timezone are prompts, not values to save.
  4. Enter a private Password of at least eight characters and repeat it in Confirm password. Generate password creates a candidate; check that the confirmation matches.
  5. For an ordinary account, leave Is super admin off under Admin access. In User role, choose an existing role only if the account needs its permissions.
  6. Choose an available Plan and Plan expiry date if needed. A new account without an explicit plan may receive the configured default signup plan; check the saved plan instead of assuming it has none.
  7. Select Create user. On the edit page that opens, check the identity, access and plan.

Edit a user or change a password

  1. Return to /admin/users, locate the correct person by email or username, and choose Edit from that row’s actions.
  2. Change the required identity, locale or timezone fields. Select role and plan by their visible names; do not type database IDs.
  3. To keep the existing password, leave the password-change fields empty. To replace it, enter the new password and matching confirmation in the password section.
  4. Select Save changes, reload the same user and check the values. If you intentionally changed the password, have the owner check it privately.

Create a role and assign it

  1. Open /admin/user-roles and select Create role.
  2. Enter a unique Role name, for example Content Manager. Add a Description of the responsibility. Leave Slug empty to let the form derive it, or enter an appropriate unique slug.
  3. Select the permission checkboxes for the actions this role needs. Read each group before granting it; the role name alone does not grant access.
  4. Select Create role. Then open the intended user’s edit form, choose this role in User role and select Save changes.
  5. Check the assigned user’s access with that account. A super-admin account is not a useful test of a restricted role.

Edit an existing team and add a member

  1. Open /admin/user-teams. Choose Manage for the existing team you want to change.
  2. Edit Team name and optional Description, then select Save changes for the team details.
  3. In the member form, select an existing User and the intended Role: Member, Lead or Owner. Select Add member.
  4. Check the member list below the form. To remove an ordinary membership, choose its Remove control, verify the person and confirm only if removal is intended.

Review user activity

  1. Open /admin/user-logs.
  2. Use User search or the User selector, and set Date from and Date to when you need a date range.
  3. Select Apply. Review the returned records for the selected user and period.
  4. Use Reset to remove the filters before investigating a different account.

Fields and choices

Field or problemWhat to do
Name / Username / EmailRequired, up to 255 characters each. Username and email must be unique. Use the intended owner’s real address when creating a real account.
Locale / TimezoneLocale is optional. Timezone is required and must be selected from the offered list.
Password / confirmationRequired for a new user, minimum eight characters and matching confirmation. On edit, leave both empty to preserve the password.
Admin access / Is super adminEnable only for an account that should have super-admin access. Enabling it clears the assigned ordinary role in this form.
User roleSelect an existing role by name. A missing role must be created and saved before it can be assigned.
Plan / Plan expiry dateSelect an existing plan and a valid date where needed. On creation, a configured default signup plan may apply. On edit, clearing the plan also clears its plan timing; review this before saving.
AvatarOptional JPG, JPEG, PNG or WebP, up to 2 MB. Use the photo/upload control if it is present in this installation.
Role name / Slug / permissionsRole name is required and unique, up to 255 characters. Slug is optional and unique. Choose permissions explicitly.
Team member / RoleSelect an existing user. Member, Lead and Owner are team-membership roles, separate from the account’s admin role.

Check the result

  • Reload the saved user and compare email, timezone, role and plan with the intended setup.
  • Check permissions from the affected user’s account, not only from the administrator’s session.
  • On the team page, confirm the member’s name/email and the team role after adding them.

Common problems

Field or problemWhat to do
Username or email is rejectedCheck for an existing account before creating another. Correct the value or edit the existing person.
Password change is rejectedUse at least eight characters and matching confirmation. Keep both password fields empty if you did not intend to change the password.
The selected role is unavailableCreate and save the role first, then reopen the user form. The role and plan selectors expect existing choices, not typed IDs.
Access differs from what you expectedCheck both Is super admin and User role, then test the affected user. Plan availability and team membership are separate settings.
The signed-in account cannot be deletedThe application blocks deletion of the account currently signed in. Do not try to bypass the check.

Technical reference

Role-scoped source references

Pinned commit: 40d27448e4517301d3d8f5a27ca0c7531c51f136

Source-only route information
MethodSource-default route
LIVEWIRE/admin/users
LIVEWIRE/admin/users/create
POST/admin/users/{user}/impersonate
LIVEWIRE/admin/users/{user}/edit
GET/admin/user-report
GET/admin/user-logs
LIVEWIRE/admin/user-roles
LIVEWIRE/admin/user-roles/create
LIVEWIRE/admin/user-roles/{role}/edit
LIVEWIRE/admin/user-teams
LIVEWIRE/admin/user-teams/{team}/edit
POST/impersonation/leave
LIVEWIRE/settings/auth
LIVEWIRE/admin/settings/auth
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
auth_landing_page_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_signup_page_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_activation_email_new_user_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_welcome_email_new_user_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_user_change_email_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_user_change_username_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_two_factor_authentication_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_facebook_login_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_facebook_login_app_idmodules/AdminUser/Livewire/AccessIdentity.php
auth_facebook_login_app_versionmodules/AdminUser/Livewire/AccessIdentity.php
auth_google_login_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_google_login_client_idmodules/AdminUser/Livewire/AccessIdentity.php
auth_x_login_statusmodules/AdminUser/Livewire/AccessIdentity.php
auth_x_login_client_idmodules/AdminUser/Livewire/AccessIdentity.php
selectedPermissionsmodules/AdminUser/Livewire/RoleForm.php
form.plan_expires_atmodules/AdminUser/Livewire/UserForm.php
avatarmodules/AdminUser/Livewire/UserForm.php
date_frommodules/AdminUser/Http/Controllers/AdminUserLogController.php
date_tomodules/AdminUser/Http/Controllers/AdminUserLogController.php