Skip to main content

Application Users

An Application User is the sign-in and permissions account in Drixal ERP: profile, seat, activate/deactivate, and roles.

What an Application User Does for Your Business​

  • Links a person to sign-in identity (user name, email, mobile)
  • Sets organization preferences: currency, language, seat type
  • Enables or stops access without deleting the record
  • Grants roles from the Roles tab

Path: Sidebar ← Administration ← Application Users
Pages: /Entities/ADM/ApplicationUser · /new · /{id}

User List​

Columns and views​

  • Default columns: name and row actions
  • Primary view is list (cards/tree usually off)

Filters​

  • Name
  • EntityTypeId
  • EntityStatusId

Row and list actions​

ActionMeaning
EditOpens the record page
DeleteRemoves the record (prefer deactivate when someone leaves)
ActivateRe-enables access
DeactivateStops access without deleting the record
Change seat type (changeSeatType)Updates the seat license
CreateOpens /Entities/ADM/ApplicationUser/new

Create and Edit a User​

  1. Create a new user or open an existing record
  2. Fill Name and Arabic name (name, nameAr) — required on the record page
  3. Add optional profile and preference fields as needed
  4. Save, then assign Roles from the dedicated tab
  5. Use Activate / Deactivate / Change seat type from the record header when needed

Required fields​

FieldUse
Name (name)Display name
Arabic name (nameAr)Arabic display name

Optional end-user fields​

FieldUse
CurrencyIdPreferred currency
LanguageId / langAbbrvUI language
OrganizationIdOrganization link
seatTypeLicense / seat
firstName / lastNamePersonal name parts
jobTitleJob title
mobile / phoneContact
email / userNameSign-in identity
isActiveWhether they can sign in
Identity and security fields

Some technical fields (passwordHash, lockout, two-factor / 2FA, accessFailedCount) belong to system administration. Do not change them casually from daily user screens.

Record page (Id)​

Tabs:

TabWhen availablePurpose
DetailsAlwaysProfile and preferences
RolesAfter create / on existing recordAssign application roles

Header actions: Activate, Deactivate, Change seat type.

From the record sidebar you can use Activities, Attachments, Insights, and Logs, plus quick Note / Call / Task / Meeting / Visit.

Lifecycle Actions​

ActionMeaning
ActivateRe-enables access (with a comment in the dialog)
DeactivateStops access without deleting the record
Change seat typeUpdates the seat license with a comment

After Save​

  • Roles tab to link application roles
  • Activities, attachments, logs, and insights from the record sidebar

Best Practices​

Assign roles right after create

A user without roles may sign in and see nothing. Attach the role before handing over the account.

Deactivate instead of delete

When someone leaves, deactivate the user and keep the audit trail instead of hard delete.