Users & Roles

This page explains who can do what in Logistall. By the end of it you can pick the right built-in role for a new hire, get their account set up and handed over, build a custom role when none of the built-ins fit, grant one person an exception without inventing a whole new role, and check what someone will actually see before — or after — you give them access.

The six built-in roles

Every user has exactly one role, and every role is a set of permissions — which parts of Logistall it can see, and whether it can only view or also create/edit/delete. Logistall ships with six built-in roles:

Company Owner — full access to all data and finance, plus the only role (besides a custom role you build) that can manage staff, roles, and company settings.
Data Admin — full access to all data and finance, including deleting records, but cannot manage users, roles, or company settings.
Dispatcher — can create and edit day-to-day operations (shipments, routes, fleet, and similar) and can view customers and quotes, but has no access to finance and cannot manage users.
Accountant — full access to invoices, payments, and carrier bills, plus creates and edits expenses (approval requires an owner or data admin); read-only on finance figures, customers, and shipments; cannot edit fleet records and cannot manage users.
Viewer — read-only access across day-to-day operational data; no finance access and no user management.
Trucker — a driver’s own account. It doesn’t see the regular app at all — just their own assigned loads and vehicle, from the My Loads and My Vehicle pages (see Driver App).

You’ll find the full list, along with any custom roles your company has added, on the Roles page.

Inviting staff

Scenario: a new dispatcher joins on Monday. Here’s the full path from nothing to a working account.

From the Users page, select Invite.
Enter their first and last name and email address, and pick a role from the dropdown. If you pick a driver-scoped role (Trucker), an extra field appears letting you link the account to one of your existing driver records.
Save. Logistall creates the account and shows you a one-time temporary password in a banner at the top of the page.
Copy the temporary password and hand it to the new user yourself — this is the only time it’s shown. Dismiss the banner once you’re done.
The first time they sign in with it, they’re forced to choose their own password before they can do anything else — see Getting Started → First login.

Manage existing users

Existing users appear in the table with their name, email, role, and status (active/inactive):

Deactivate on a user’s row blocks them from signing in without deleting their account; Activate reverses it.
Change Role lets you move a user to a different role at any time.

Custom roles & cloning

Scenario: you want your ops manager to run day-to-day operations like a Dispatcher, but also see finance figures. No built-in role does both — so build one.

If none of the six built-in roles fit exactly, build your own from the Roles page:

Select New Role.
Give it a name and description.
Use the permission matrix to choose exactly what it can do: each row is an area of the app (Shipments, Invoices, Users, and so on) and each column is an action (read, create, update, delete). Check individual boxes, or select a row’s name to toggle every action in that row at once.
Save, then assign the new role to users from the Users page with Change Role.

Rather than starting from a blank matrix, select Clone on any existing role — built-in or custom — to open a new-role form pre-filled with that role’s entire permission set (and a name like “Dispatcher (copy)”). Adjust the name, description, and permissions, then save it as a brand-new custom role; the role you cloned from is untouched.

Per-user permission overrides

Sometimes one person needs an exception to their role rather than a whole new role — say, one senior dispatcher who should also be able to read invoices, while every other dispatcher stays finance-free.

On the Users table, select Permissions on the user’s row to open their override editor — the same kind of matrix as the Roles page, but scoped to just that user.
Set individual cells. Each cell has three states:
- Default — follow whatever their role grants.
- Allow — grant this permission even if their role doesn’t include it.
- Deny — block this permission even if their role would normally grant it.

Their effective access is their role’s permissions, plus anything you’ve set to Allow, minus anything you’ve set to Deny.

Check what someone will see: “View as” preview

Scenario: before assigning the Viewer role to a new auditor, you want to be sure it hides everything it should.

The sidebar has a View as picker that lets you preview the app as if you had a different role’s permissions. Pick a role and Logistall re-renders your own session under that role’s permissions: pages and buttons you wouldn’t normally see disappear, exactly as they would for a real user with that role.

This is entirely client-side — it only ever restricts what your own screen shows you, and it never touches the server or grants you anything you don’t already have. A banner stays pinned to the top of the page for as long as the preview is active, with an Exit button to return to your normal view.

You can also preview as a specific person rather than a generic role: select View As on a user’s row in the Users table to see the app the way that exact user would, including any per-user overrides they have.

Troubleshoot with their real data: “Open as user” (read-only)

Scenario: a trucker calls saying a load is missing from their app. Rather than guessing, look at exactly what they see.

Separate from the UI-only preview above, Open as user — available on a user’s row in the Users table (for staff other than yourself) — actually opens a real working session as that person, so you see their exact data rather than a simulation. That makes it the right tool for troubleshooting what someone is reporting, such as checking a trucker’s own assigned loads.

This session is strictly read-only: while it’s active, any action that would change data is blocked, no matter what the target user could normally do. A distinct banner (in a different color from the View As banner) stays visible the whole time, with its own Exit button to close the session and return to your own account.