A user account is the record for one person, one built-in system identity or one integration stand-in in your xMatix organization. It holds the person's sign-in name, contact details, audience, language and time zone. It is also the anchor for every profile, role, team, license seat and company grant that decides what the person can do. Every record in xMatix points back to user accounts: the Owner, Created By and Modified By of any record are user accounts.
Accounts are created when you invite a user and switched off when you offboard them. This page covers everything in between: finding and reading an account, editing it, what each field does, the actions on the account page, placeholder users, and how the account's settings affect the person's day-to-day experience.
Overview
You manage accounts under Setup → Access control → Users (open Setup from the gear menu in the top bar). The page lists every account in your organization in an All Users table. The page header shows a recently opened strip and the New button. Selecting a name opens the account's own page. Its header shows the key facts and the actions, and the tabs below hold the access assignments.
An account has three layers:
- Identity: Username, Email, Phone, the names, and the Audience (Internal or External). These decide how the person signs in and which security profiles can be assigned to them.
- Preferences: Language, Locale and Time zone. These change how xMatix shows text, numbers and dates to this person.
- Access: profiles, roles, teams, license seats and company access. These are separate records attached to the account. You edit them on the account page tabs and on the Company Access tab in Org Settings.
There are three kinds of account:
- Logins are people who sign in, or will once they are activated and invited. Almost every account is a login.
- Placeholders stand in for a user of an integrated system, so that records synced from that system have an owner. A placeholder never signs in. You can turn it into a login or link it to an existing login (Step 6).
- Built-in system identities: System Process, System Agent and System Anonymous. They run scheduled jobs and automation, autonomous agent runs, and anonymous storefront traffic.
How xMatix handles it
- Sign-in is provisioned separately. Saving an account writes it immediately, but the person's sign-in account is created in the background. The Sign-in column tracks this:
- Pending: the first five minutes after creation.
- Ready: the sign-in account exists.
- Not provisioned: no sign-in account after that.
- Placeholder: an integration stand-in.
- System: a built-in identity.
On the account page the same field can also read Not linked: the account is marked as provisioned, but no sign-in account is on record. Only accounts with Active switched on, and with a username or email, are provisioned.
- Activating sends the invite. When an active account is saved for the first time, or an inactive one is switched on, xMatix creates the sign-in account and emails the invite. The exception is when you untick Email the sign-in invite. An account created inactive sends nothing.
- Defaults fill gaps. A new account is active and Internal unless you say otherwise. A blank Display name is built from First name and Last name. The account's Name is taken from the username, then the email, then the display name.
- Addresses are tidied. Leading and trailing spaces are removed from the username and email when you save.
- One account per email. A new account, or a changed email, is refused when another account already uses that email.
- System identities are not people. They never sign in and show System in the Sign-in column. The Users screen offers no Edit or Delete for them. Their page shows a Built-in system identity notice. Leave them alone: removing one breaks the work it runs.
Prerequisites
- To open Users and create, edit, activate or delete accounts: the user-administration capability (
setup.security.users.manage) together with the security-administration capability (setup.security.manage), which shows the Access control menu group. - To see the License Allocations and Access Diagnostics tabs on someone else's account: the licensing capability (
setup.licensing.admin). - To edit your own preferences: no capability. Every signed-in user can.
Procedure
Step 1 — Find an account
Open Setup → Access control → Users. By default, the All Users table shows Display name, Name, Email, Phone, Active and Sign-in, sorted by name. You can add the Audience column from the column chooser.
- Use the search box in the table header to match on name, display name, email or phone.
- Use the column filters to narrow by Active or Sign-in. Filtering Sign-in is the quickest way to find accounts that cannot sign in.
- Refresh reloads the list.
Search before you create anyone. Reusing an existing account, even an inactive one, keeps the person's history in one place.
Step 2 — Open the account
Select the person's display name. The page header shows:
- Name, Display Name, Email and Audience
- Status (Active or Inactive)
- Sign-in (Ready, Not linked, Not provisioned or System)
A notice explains any state that needs attention:
- This user has no sign-in identity yet: an active account with no sign-in account.
- Marked as provisioned, but no sign-in account is linked: Sign-in reads Not linked.
- This user is inactive: use Activate.
See Common problems.
The tabs below the header are:
- Role Assignments, Profile Assignments and Team Assignments: the person's place in the role hierarchy, the security profiles that grant their access, and their teams. See Security profiles and Roles, teams and business units.
- License Allocations: product, feature and package seats, each with an add control and a Revoke seat action. See Licensing.
- Access Diagnostics: a computed summary of everything the person effectively has. It shows counts and lists of Profiles, Roles, Teams, Business Units, Product Licenses and Capabilities. Product Licenses, Feature Licenses and Capabilities are each split into Allocated to user and Required by profile. An Outlet Transfer card shows which channel partners, HQs and beats the person can transfer outlets between in the field app. When there are none, it says why.
Step 3 — Use the actions on the account page
The page header shows only the actions that fit the account's state:
| Action | Shown when | What it does |
|---|---|---|
| Back | Always | Returns to the Users list. |
| Edit | Not a system identity | Opens the Edit user dialog (Step 4). |
| Activate | The account is inactive and is not a placeholder | Switches the person on. The dialog shows whether the invite will be emailed and can give them a profile and teams. See Invite a user. |
| Check sign-in account | The account is active and not a system identity | Looks up the person's sign-in account. An existing one is linked; a missing one is created and a set-password email is sent. |
| Resend invite | Sign-in is Ready and the account is active | Emails a fresh set-password link. It works once and expires in 72 hours. |
| Set password | Sign-in is Ready and the account is active | Sets a password for the person yourself, optionally forcing a change at next sign-in. See Invite a user. |
| Log in as user | You hold the log-in-as capability, the feature is on, and the account is an active login other than your own | Opens a time-limited, audited session as the person. See Why can't a user see something?. |
All of these except Back and Log in as user need the user-administration capability.
Step 4 — Edit the account
On the account page, select Edit in the page header, or select the edit icon in the Actions column of the Users list. The Edit user dialog has the same fields as New user (see Fields). Change what you need and select Save. A confirmation reads User updated, and the account page reloads.
Username and Email are checked against the sign-in rule before the dialog saves. If the dialog flags the username, fix it.
If you switch Active on for an account that was inactive, the dialog also shows Email the sign-in invite. Leave it ticked to send the invite. Untick it to create the sign-in account without any email; you then use Set password on the account page.
Step 5 — Activate several accounts at once
In the All Users table, tick the accounts and select *Activate (n) in the page header. The dialog lists each account under What happens*:
- Invite: the account is activated and the invite will be emailed.
- No email: the account is activated without an invite. This happens when you untick Email the sign-in invite, when the address has no deliverable email, or in a sandbox when the address is not on the email allow list.
- Skipped: the account is already active, or it is a placeholder.
You can also choose a Security profile (for users who have none) and Add to teams in the same step. The confirmation says how many accounts were activated and how many invites are on the way.
In a sandbox, the Users page also shows Sandbox email, which decides who receives the sandbox's emails. See Sandboxes.
Step 6 — Turn a placeholder into a login, or link it
A placeholder shows Placeholder in the Sign-in column. Its row in the Actions column has two extra icons.
Turn into login gives the placeholder a real sign-in and keeps everything attached to it:
- Select Turn into login on the placeholder's row.
- Enter the person's Email, and their First name and Last name if you want to set them.
- Leave Activate now ticked to switch the person on straight away. Leave Email the sign-in invite ticked to send the invite, or untick it and use Set password later.
- Select Turn into login.
The account keeps its identity, so every record it owns or created stays with the person, and the integration sync keeps pointing at it. If you leave Activate now unticked, the account is saved as an inactive login; use Activate when you are ready.
If the email already belongs to another account, the dialog says so and offers Link to that login.
Link to login is for a person who already has a login, or who has more than one user in the integrated system:
- Select Link to login on the placeholder's row.
- In Login, type at least two characters of the person's name or email and pick their login.
- Leave Also move the records this placeholder owns to the login ticked to reassign the placeholder's records now. Untick it to move only future records.
- Select Link.
From then on, records synced for that integrated-system user belong to the login. With the box ticked, the Owner of the placeholder's existing records changes to the login. Created By and Modified By keep their history. A very large move is done in parts: the confirmation says how many records were moved and how many remain, and you run Link again to continue. The placeholder stays, inactive.
You can also reach Turn into login from New. When the first and last name you type match a placeholder, the dialog shows This person may already have a placeholder user. Select Use … to turn that placeholder into the new login instead of creating a second account.
Step 7 — Name a delegated approver
In the Edit user dialog, expand Approvals and pick a Delegated approver. You can pick anyone except the person themselves.
From then on, every approval step that resolves to this person also goes to the delegate. The request appears in the delegate's approval inbox and notifications, and the delegate may decide it. The original approver keeps the request too, and either of them can act.
Clear the field to stop delegating. See Common questions for limits.
Step 8 — Set language, locale and time zone
In the Edit user dialog, expand Locale & time zone and fill Language, Locale and Time zone. You type these as text here, so use the standard codes:
- a language such as
enorhi - a locale such as
en-IN - a time zone name such as
Asia/Kolkata
If you leave them blank, the person sees your organization's defaults from Setup → Feature Hub → Administration → Org Settings.
People can also set these themselves (next step). There they pick from lists, which avoids typing errors.
Step 9 — Let people edit their own profile
Any signed-in user can open their profile from the avatar menu. On the Account card they:
- Select Edit.
- Change any of Display Name, First Name, Last Name, Phone, Language, Locale or Time Zone.
- Select Save.
Language offers English (en) and Hindi (hi). Locale and Time Zone are searchable lists. Email, Username and Active are shown but can't be changed. Changing the language reloads the page.
A field left empty on the profile page keeps its previous value, so users can't blank a field this way. To clear one, an administrator edits the account.
The profile page's other tabs (Preferences, Notifications, Security, Subscription) are described in Personalizing xMatix.
Step 10 — Grant company access (multi-company organizations)
Company access is not on the user dialog. To grant it:
- Open Setup → Feature Hub → Administration → Org Settings → Company Access.
- Choose the person in Select a user.
- Either switch on Access all companies, or select Grant company access in the page header.
- If you chose Grant company access, pick a Company and an Access kind: Transact (see + post) or View (see only).
The tab appears only when multi-company mode is on and you hold the company-administration capability. While Access all companies is on, the per-company rows are ignored. How this is enforced is explained in Tenants and companies.
Step 11 — Delete an account
Deleting is the last step of offboarding, so follow Offboard or suspend a user first. Then select the delete icon in the Actions column of the Users list and confirm Delete user?.
The account disappears from the list. The business records the person owned or created keep their attribution. Usually, switching Active off is enough and keeps the account available to reactivate.
Fields
These are the fields in the New user and Edit user dialogs, in form order.
| Field | What it means | Notes |
|---|---|---|
| Username | The name the person signs in with. | Must equal Email exactly, or be a plain name without @: letters, digits and . - _ ! # ^ ~, up to 64 characters. A username that is a different email address is refused. It fills itself from Email (or Phone) until you type in it. Leave it the same as the email to sign in with the email. |
| First name | Given name. | Used to build Display name. |
| Last name | Family name. | Used to build Display name. |
| Work email address. Where the invitation goes, and a sign-in identifier. | Must be unique in your organization. In New user, the dialog warns as you type when another account already uses it, and offers Open user. Spaces are trimmed on save. | |
| Phone | Contact phone number. | If the username is a phone number and Phone is empty, the username is copied here. |
| Display name | The name shown across xMatix: lists, owner fields, mentions. | Follows First name + Last name until you type in it. Built from them on save when blank. |
| Audience | Internal (employees) or External (portal and partner users). | Required. Default Internal. A security profile scoped to the other audience can't be assigned. |
| Active | Whether the person may use this organization. | On by default. Only active accounts are provisioned and receive the invite, so you can create accounts inactive to prepare them before go-live. Clearing it on an existing account suspends it: from the next request, xMatix refuses everything the person does in this organization. Activate brings them back. See Offboard or suspend a user. |
| Email the sign-in invite | Whether switching the account on emails the invite. | Shown only while this save switches the account on (a new active account, or an inactive one turned on). Ticked by default. Unticked, the sign-in account is created without any email, and you use Set password. |
| Language | Interface language, as a language code. | Under Locale & time zone. Blank uses the organization default. |
| Locale | Regional format for numbers, dates and currency, such as en-IN. | Under Locale & time zone. When it refines the chosen language (same base language), it also drives number grouping: en-IN shows lakhs and crores. |
| Time zone | The zone dates and times are shown in, such as Asia/Kolkata. | Under Locale & time zone. Overrides the organization time zone for this person. A name xMatix does not recognise is ignored, and the organization zone applies. |
| Delegated approver | A user who receives, and may decide, this person's approval requests. | Under Approvals. Optional. The person themselves is not offered. |
Read-only facts shown elsewhere: Name (set on creation), and Status and Sign-in in the account page header.
Business rules
- Username rule. On create, and on any edit that changes Username or Email, the pair must be provisionable: the username equals the email, or is a plain name of up to 64 allowed characters. The dialog stops you before saving, and the server enforces the same rule.
- Defaults on create. Active is on, Audience is Internal, Display name is built from first and last name, and Name comes from the username, then the email, then the display name. An explicit Active off is kept.
- Provisioning trigger. Saving an account that is active, has a username or email, and has no sign-in account yet sends it for provisioning. So does switching an inactive account on. Inactive accounts are never provisioned. Once the sign-in account exists, later saves don't send another invite. Use Resend invite for that.
- One account per email. Creating a user, or changing a user's email, is refused when another account already has that email: A user with the email … already exists: … Edit that user instead of creating another. When that account is inactive, the message tells you to activate it instead. Only new or changed emails are checked, so accounts that already share an email can still be edited.
- Placeholders never sign in. A placeholder is always inactive and is never invited. Saving one as active is refused: A placeholder user cannot be active. Use "Turn into login" to give it an email and activate it. Activate skips placeholders, and Log in as user refuses them.
- System identities. System Process, System Agent and System Anonymous have no Edit or Delete on the Users screen.
- Delegation is one step. A delegate is added alongside the approver, not instead of them. A delegate's own delegate is not included. Delegation applies whether or not the original approver is active.
- Self-service limits. On the profile page a user may change only display name, first and last name, phone, language, locale and time zone.
- Deletion. Deleting removes the account from your organization's lists and stops it resolving as a user. It does not delete records the person owned or created. It also does not delete a sign-in account they use with another organization.
Example
A distribution company hires a sales coordinator who works from Kochi and approves the field team's expense claims.
- The administrator opens Setup → Access control → Users, searches
sales.coordinator@example.comand finds nothing. - They select New and type the address in Email, and Username fills with the same address. They type Sales and Coordinator in the name fields, and Display name becomes Sales Coordinator. Audience stays Internal, Active stays on and Email the sign-in invite stays ticked. Under Locale & time zone they enter
en,en-INandAsia/Kolkata. They select Create. - The row appears with Sign-in Pending. A minute later it shows Ready, and the coordinator receives the set-password email.
- On the account page, the administrator adds the coordinator's profile on Profile Assignments and their role on Role Assignments.
- Two months later the coordinator goes on leave. The administrator opens the account, selects Edit, expands Approvals, picks the regional sales manager as Delegated approver and selects Save. Expense claims routed to the coordinator now reach the manager's inbox too, and either can approve.
- When the coordinator returns, the administrator clears Delegated approver and saves.
Training
Practice exercise
In a sandbox:
- Create an account for a fictitious person with Active switched off. Expected: Sign-in shows Pending for the first five minutes, then Not provisioned, and no email is sent.
- Try to set Username to an email address that differs from Email. Expected: the dialog refuses it with the username rule message.
- Select New again and type the same email. Expected: a warning says that account already uses this email and offers Open user. Cancel.
- Open the first account, select Edit, set Time zone to
Asia/Dubaiand Locale toen-IN, and save. - Name yourself as their Delegated approver.
- Open their Access Diagnostics tab. Expected: zero profiles, and nothing under Allocated to user.
- Delete the account. Expected: it disappears from All Users.
Quick reference
- Users live at Setup → Access control → Users.
- Username = email, or a plain name without
@(up to 64 characters). - Only Active accounts are provisioned; activating sends the invite unless you untick Email the sign-in invite.
- Sign-in: Pending → Ready. Not provisioned after five minutes means: fix and save again.
- One account per email; search before you select New.
- A Placeholder never signs in: Turn into login or Link to login.
- No profile assignment means an empty workspace.
- A user's time zone and locale override the organization's for that person.
- A delegated approver shares the requests; they do not replace the approver.
- Never edit or delete System Process, System Agent or System Anonymous.
Permissions
| What | Needs |
|---|---|
| See Users in the menu | setup.security.manage and setup.security.users.manage |
| Read, create, edit, activate or delete accounts; turn placeholders into logins or link them; check sign-in, resend the invite, set a password | setup.security.users.manage |
| Assign profiles, roles and teams | setup.security.manage |
| See License Allocations and Access Diagnostics for another user | setup.licensing.admin (you always see them on your own account) |
| Preview Outlet Transfer scope | setup.featurehub.settings.manage. Without it the card says so, and the rest of the tab still loads |
| Log in as user | setup.security.users.loginAs, with log-in-as switched on for your organization |
| Grant company access or Access all companies | setup.companies.manage, plus access to Org Settings |
| Edit your own profile | Any signed-in user |
A user without the user-administration capability does not see Users in Setup, and their calls to read or change accounts are refused. The built-in SystemAdmin profile holds all of these.
Configuration
- Organization defaults. Setup → Feature Hub → Administration → Org Settings → General holds the default locale, currency, time zone and date format. Every account without its own value uses them, so changing them affects everyone who has not set a personal value.
- Per-user preferences. Language, Locale and Time zone on the account, set by an administrator or by the user on their profile page.
- Audience. Decides which security profiles fit the account. Profiles are scoped to Internal, External or Both on Security profiles.
- Delegated approvers. Set per account under Approvals. Approval steps themselves are configured on the approval process; delegation applies to every process.
- Company access. Set per user on Org Settings → Company Access, when multi-company mode is on. See Tenants and companies.
- License seats. Set per user on License Allocations. Seat enforcement and pools are described in Licensing.
- Deferred invitations. Create accounts with Active off to prepare them without provisioning or email. Then activate them at go-live, one at a time or with *Activate (n)*.
- Log in as user. On unless your organization's custom setting
security/loginAs.enabledisfalse(Org Settings → Custom Settings).loginAs.requireReason(on unless set tofalse) makes the reason mandatory.loginAs.maxMinutessets the longest session: 30 minutes when not set, never more than 60. - Sandbox email. Inside a sandbox, Sandbox email on the Users page decides who receives invites. See Sandboxes.
Common problems
"This user has no sign-in identity yet"
The account is active, but provisioning has not completed. For the first few minutes after creation that is normal. If it persists, check that Username matches Email or is a plain name without @. Then save the account again to retry.
Sign-in shows "Not linked"
The account is marked as provisioned, but no sign-in account is on record, so the person may not be able to sign in. Select Check sign-in account. An existing sign-in account is linked; a missing one is created and a set-password email is sent. The account needs a real email address first. If the page says the check is still running, refresh it after a minute.
The dialog says the username must match Email
The username is a different email address from Email, contains a character other than letters, digits and . - _ ! # ^ ~, or is longer than 64 characters. Make it identical to the email, or a plain name that follows the rule.
"A user with the email … already exists"
Another account already has that address. Open it instead (the New user dialog offers Open user), or activate it if it is inactive. If the other account is a placeholder for the same person, use Turn into login or Link to login instead of creating a new account.
"A placeholder user cannot be active"
You tried to switch a placeholder on directly. Use Turn into login on its row in the Users list. That gives it an email and activates it.
Turn into login says the email is already used
Another account already has that email (… already uses … Link this placeholder to that login instead.). Select Link to that login in the dialog.
Link to login is refused
The messages tell you why:
- This placeholder does not carry an external user id, so there is nothing to link: the placeholder was not created by an integration.
- This organization has no integration app that maps users: no installed integration maps users, so there is nothing to route.
- Link a placeholder to a login, not to another placeholder: you chose another placeholder.
Dates and times show in the wrong time zone for one person
Their account's Time zone is set to another zone, or to text xMatix does not recognise, in which case the organization zone applies. Have them pick the zone from the list on their profile page, or correct it under Locale & time zone.
Numbers show millions instead of lakhs
The person's Locale is blank or names a region that formats numbers that way. Set Locale to en-IN (with Language en) or hi-IN (with Language hi).
The delegate cannot see an approval request
Delegated approver is set on the wrong account. It goes on the account of the person who is away, naming the person who covers. It also covers only one step: if the delegate has their own delegate, that second person is not included.
There is no Edit or Delete on an account
It is one of the built-in system identities (Sign-in shows System). That is deliberate.
I cannot find the Company Access tab
It appears only when multi-company mode is on and you hold the company-administration capability. It sits in Org Settings, which also needs the Feature Hub and Org Settings capabilities to reach from the menu.
Common questions
Can two accounts share the same email address?
No. xMatix refuses a new account, or a changed email, when another account already uses that address, and the New user dialog warns you while you type. If the existing account is inactive, activate it rather than creating another. That keeps the person's profiles, roles, teams, seats and records together on one account. Accounts that shared an email before this check existed can still be edited, but changing either one's email to the other's is refused.
What is a placeholder user?
A placeholder is an account an integration creates for a user of the other system, so that records synced from there have an owner and a creator. It has no email, is never active and never signs in. When that person needs to use xMatix, Turn into login gives the placeholder their email and activates it. Their records stay attached because the account itself is kept. If the person already has a login, Link to login routes future synced records to that login and can move the placeholder's records too.
Does a delegated approver replace the original approver?
No. The delegate is added to every approval step that resolves to the original approver, so both see the request and either can decide it. Delegation doesn't depend on the original approver being away or inactive: it applies as soon as it is set. Clear Delegated approver when cover is no longer needed. Only one step is followed: a delegate's own delegate does not receive the request.
Why do two people see different times on the same record?
Each person sees dates in their own Time zone when one is set, otherwise in the organization's time zone. So two people looking at the same record can see different clock times for the same moment. The stored value is the same; only its display differs.
Can a user change their own email or username?
No. The profile page lets people change their display name, first and last name, phone, language, locale and time zone only. An administrator with the user-administration capability changes sign-in details, audience, active state, delegated approver and access. That way a sign-in identifier always passes the username rule and the uniqueness check.
What is the Name column, and how is it different from Display name?
Name is the account's record name, set when the account is created. It comes from the username, or the email, or the display name if both are blank. Display name is the friendly name shown across xMatix in lists, owner fields and mentions. It follows first and last name unless you set it yourself.
