Users

What you are looking at

A table of people, one row each, with the count of machines currently in their name.

The top row holds the search box, the count of what is currently showing, and Add User. The table below has seven columns: Name, Email, Title, Department, Location, Source and Assets. Missing values are shown as an em dash rather than left blank, so an empty cell is always a real absence rather than a rendering gap.

The Assets column is a button, not a number. It shows how many machines are currently assigned to that person and opens their card when you click it. The trash icon on the far right appears only on rows whose Source is Manual.

Where the rows come from

Two sources, and the difference matters for what you can edit.

Synced rows come from a directory connection set up in Admin. They are a read-only mirror: Manifest shows what the directory says, and the next sync refreshes it. You cannot delete a synced user here, because deleting the row would only hide the fact that the directory still has them.

Manual rows are people you added yourself, through Add User. They are yours to edit and yours to delete. The Source column shows Manual with a pencil icon, and synced rows show the provider name with a circular-arrows icon.

Finding a person

One search box, matching on name or email.

Type into Search users by name or email and the table filters as you go. The search runs against the directory store, not the loaded page, so it stays quick on a large organisation. Clearing the box returns you to the full active list.

The count beside the search box reads N users and reflects what is currently showing, so it is the number of matches rather than the size of the directory.

Adding a user by hand

The guided flow for the case a directory sync cannot cover: a new hire starting today, before the next sync.

1. Open the sheet

   Add User in the toolbar, or the same button in the empty state.

2. Fill in Identity

   First name, Last name and Email. A first or last name is enough to save; the email is optional but is what the duplicate check runs on.

3. Fill in Role

   Job title, Department, Location, Worker type and Employee ID (optional). Department and Location are pickers if Admin has defined values, and plain text fields if it has not.

4. Add User

   The button is disabled until a first or last name is present. If the email already exists, the sheet stays open and shows A user with that email already exists.

A manual user with no name and no email is stored as Unnamed rather than rejected, which is deliberate: a placeholder you can assign hardware to and fix later is more useful than a form that will not let you through.

Opening a user

Double-click a row, press Return on it, or use the context menu. The card opens as a sheet.

The header shows initials, display name, email, an Active or Inactive badge, and the source label. Below it, three sections in order: ASSIGNED DEVICES, PROFILE and CUSTOM FIELDS.

ASSIGNED DEVICES lists every machine currently in this person’s name, with its asset tag, make and model, and status badge. Clicking one closes the card and opens that asset in the Assets screen, with the asset tag already in the search box. If nothing is assigned, the section reads No hardware is currently assigned to this person.

The Done and Save Profile buttons sit at the bottom. Save Profile is disabled until something has actually changed.

The compliance record

The PROFILE section is the part of a user that a directory sync will not overwrite.

Eight fields, in two columns: Employee ID, Worker Type, Manager, Job Title, Department, Location, Start Date and End Date (offboard). Worker Type is a picker; the two dates are optional and can be cleared once set.

The line under the grid says what the section is for: The compliance record is kept even when a directory sync updates this user. That is the whole point of the section. A sync refreshes the identity fields it owns; the compliance record is yours and stays put.

End Date (offboard) is the field to set when somebody leaves. It is the date the offboarding is recorded against, and it is separate from the directory entry, which may disappear from the sync the moment the account is closed.

Custom fields on a user

The same custom field system that runs on assets, scoped to people.

If Admin has defined custom fields for users, the CUSTOM FIELDS section appears on the card with an editor for each one. The section is hidden entirely when no user custom fields exist, so a fresh install shows three sections rather than four.

Custom field values are part of the compliance record and are preserved across directory syncs in the same way.

What you cannot do here

Three deliberate limits, each because the alternative would be worse.

• You cannot delete a synced user. The row is a mirror of a directory entry. Deleting it here would hide the fact that the directory still has them, and the next sync would bring them back. The trash icon only appears on Manual rows.
• You cannot edit a synced user’s identity fields. Name, email, title, department and location come from the directory. The compliance record is the part you own, and it is the part the card lets you change.
• You cannot bulk-edit users. There is no selection bar on this screen. The work that would need it, assigning hardware to a group of people, is done from the Assets side, where the machines are.

The context menu

Right-click a row for the four things you would otherwise open the card to do.

Open User does the same as double-clicking. Copy Email and Copy Name put the value on the clipboard without opening anything, which is the common case when you are pasting a name into a ticket. On Manual rows only, Delete User appears below a divider.