Skip to content

Docs / RivetMSP / Using the platform

Users, roles and client access

Roles and module permissions, limiting technicians to clients, portal access and two-factor sign-in.

Access in RivetMSP is controlled in layers. It helps to keep them apart in your head.

1. Roles and module permissions#

A role says what a technician can do in each part of the application. Manage roles under Administration > Roles.

For each module, a role has one of four levels:

Level Meaning
None The module is hidden and blocked
Read View only
Write View and change
Full Everything, including deleting

The modules cover areas such as clients, support (tickets), credentials, sales, financial, reporting and the knowledge base. A role marked as an admin role gets full access everywhere and can open the Administration area. Admin is not a separate kind of account: it is an ordinary agent whose role has the admin flag.

2. Features that are switched off for everyone#

Separately from roles, whole features can be switched on or off for the whole install. A feature must be on and the person's role must allow it. See Turning features on and off.

3. Limiting a technician to certain clients#

By default a non-admin technician can see every client. You can restrict them to a list of clients instead.

Read this carefully. The restriction only switches on once a technician has at least one client assigned. A technician with no clients assigned sees all clients. An empty list means "no restriction", not "no access". Adding even one client to the list switches that technician to seeing only the clients listed.

4. What your clients' contacts can see#

Client contacts sign in to the client portal and have no roles. What they see is driven by three flags on their contact record:

  • Primary: the main contact. Gets both of the views below.
  • Billing: can see invoices and payments.
  • Technical: can see assets and tickets.

The portal also respects the company-wide feature switches, and can be turned off entirely.

Signing in#

Technicians and client contacts sign in on the same page. If one email address has both an agent account and a client account, the person is asked which to use.

Protecting technician accounts#

  • Password. Stored as a bcrypt hash.
  • Authenticator codes (TOTP). Each technician enrols their own. You can require it per user, so that person has to set it up.
  • Passkeys (WebAuthn). Available to technicians only. Client contacts cannot use passkeys.
  • Login key. An optional install-wide shared secret, checked in addition to a user's own credentials, as a perimeter check.
  • Remember me. A hashed cookie that skips two-factor and restores the session on later visits.

Single sign-on for clients#

The client portal can offer Microsoft Entra ID sign-in. This is sign-in only; it does not sync your directory.

API access#

Applications authenticate to the REST API with a per-user bearer token, or with an install-wide API key managed under Administration > API keys (which can be read-only or read/write, and can be limited to a single client). See the REST API guide and the API reference.

This guide is maintained by Rivet IT Ops. Found a mistake? Tell us. RivetMSP on GitHub