Custom fields, tags, roles and co-managed access
Add your own fields and tags to customers, contacts, sites and devices; build roles from the presets; give a technician or a customer's own IT team only some customers.
Updated
On this page
Custom fields
Settings → Custom fields adds fields of your own to customers, contacts, sites and devices (and to tickets when RevoPSA is on). Each field has a type: text, number, date, yes or no, dropdown or link. A required field must be filled when a record is added or imported, and can't be cleared.
Fields show on the record: a customer's overview (Tags and fields), a contact's details, a site's Fields, and a device's quick look or Settings tab. Filter the customer and contact lists by a field, and build device groups on them. In CSV import and export, each field is a column named by its label.
Tags
Customers, contacts and devices can carry up to 20 tags each. Tags you already use are suggested as you type. The customer, contact and device lists filter by tag.
Import and export
Settings → Import and export exports customers, contacts or devices without an agent as CSV, in the columns the import reads. To import, choose a file: Revo checks every row first and shows what it would add, update or skip, and why. Then Import brings in the rows without errors. A blank cell leaves a value unchanged.
Roles
Settings → Roles builds roles of your own. Start from technician, analyst or admin, then tick or untick permissions. Nobody can create or assign a role that can do more than they can. Billing stays with owners; managing people, API keys and workspace settings needs a role based on admin. Give someone a role from Settings → Team → ⋯ → Access.
Working on some customers only (co-managed IT)
In the same Access dialog, tick Only selected customers for a technician or analyst and choose their customers. They then see only those customers and their records, devices, tickets and notes. They keep the permissions that touch a customer's own data, and lose workspace-wide ones: settings, integrations, patch policies, reports across customers and the AI analyst. Their notifications cover only their customers. Use this for a customer's in-house IT staff, or technicians assigned to some accounts.
Sign-in restrictions
Owners can limit the addresses the team signs in from: Settings → Sign-in restrictions. A list that leaves out your own address is refused, so you can't lock yourself out. Customer-portal users and API tokens aren't affected. If an office address changes and nobody can sign in, contact Revo support to clear the list.