Prepare your Rev.io before onboarding: the setup checklist

Connecting Rev.io takes two minutes. A clean first sync takes a little preparation, because the key's role decides what Current can see and change, and a few Rev.io lists decide where time and tickets land. Work through these six steps before you paste a key.

A Rev.io API key carries the role of the user who creates it, and everything the key does is attributed to that user. Create a user named Current and give it a role that can read every area Current syncs and edit the ones you want written back. The list is in "Connect Rev.io and choose what syncs". Two reasons for a dedicated user: your technicians' names stay off records Current wrote, and the sync's permissions live in one role you can read at a glance.

• ＋Sign in as the Current user and open Admin, API Management in Rev.io PSA.
• ＋Create the key and copy it into a password manager.
• ＋It has to be a Rev.io PSA API key. A login for Rev.io's billing REST API at developers.rev.io is a different product and will not connect.
• ＋Whether a Rev.io key expires on a schedule is still being confirmed. If the card reports a sign-in failure with no other explanation, create a new key and paste it under Edit credentials.

Rev.io boards become ticket queues in Current. After the first sync, the Rev.io card lists them and you switch off the ones that are noise, such as an alert board fed by a monitoring tool. A board switched off stops new tickets from it arriving in Current; it never deletes anything in Rev.io.

Rev.io bills time against a time log reason, and every entry Current sends needs one. Current brings the active reasons across as the billing codes a time entry picks from. Make sure the reasons your team uses are active and named so a technician can pick the right one. Current never reads a reason's cost or billing rate: the rate stays Rev.io's own, and Current never sends one.

Email is the only link between a Rev.io user and a person in Current. When they match, time is attributed, tickets land on the right person, and My Day shows the work assigned to them. When they do not, that person's Rev.io work has nowhere to land. Fix the mismatches before the first sync, and check the roster afterwards in Admin, Users and roles.

• ＋CRM write mode is off by default, so Current writes nothing to Rev.io, time included, until you set it to Test or Live. That makes the start read-only on its own.
• ＋Test mode lets writes run only on records whose Rev.io customer's name starts with ZZ-Current Test. Each write checks the record's own customer as Rev.io holds it, read live from Rev.io at that moment, so you can prove writes on records nobody bills. Create one such customer in Rev.io if you want to test.
• ＋Two-way sync, on by default, then controls task, project, ticket and CRM changes. Time entries are gated by CRM write mode alone.
• ＋Ticket-noise settings live on the Rev.io card, and you can change them at any time.

• ＋A user named Current exists, with a role that reaches the areas in the connect article, and you hold its PSA API key.
• ＋You know which boards are noise.
• ＋The time log reasons your team bills against are active.
• ＋Your technicians' Rev.io emails match their Current sign-ins.
• ＋You know which CRM write mode you want on day one, and whether two-way sync stays on.