Prepare your Syncro before onboarding: the setup checklist

Connecting Syncro takes two minutes. Getting a clean first sync takes a little preparation in Syncro, because a few of its defaults decide what Current can see and what it is allowed to create. Work through these seven steps before you paste a token and the first sync tells you about your business rather than about your permissions.

A Syncro API token belongs to a person, and everything the token does is attributed to that person. Create a security group named Current, create a user in it named Current, and create the token while signed in as that user. Two reasons: your technicians' names stay off records Current wrote, and the permissions the sync has live in one place you can read at a glance.

• ＋Admin, Syncro Administration, Security Groups: a group named Current.
• ＋The permission list is in "Connect Syncro and choose what syncs". Tick exactly those areas, no more.
• ＋Profile, API Tokens, New Token, Custom Permissions, signed in as the Current user. The key is shown once.
• ＋If you want the Syncro Assets feed as well, tick Assets List/Search, Assets View Details and RMM Alerts List on the same token. Skip them if you do not, and add them later.
• ＋Syncro tokens can carry an expiry. Note the date somewhere you will see it: an expired token stops the sync and the connection card shows the failure. Whether Syncro names the expiry as the cause is still being confirmed, so treat a sign-in failure with no other explanation as a token to rotate first.

Admin, Tickets, Preferences: switch on parent/child tickets and ticket due dates. Then check that the Current security group carries Ticket Parent-Child, Edit. The account setting and the permission are separate, and a project create needs both. Without them, deploying a Current project to Syncro comes back as a permission error rather than a parent ticket.

A Syncro ticket timer entry bills against a product, so time Current sends needs a Labor product to point at. Create at least one, and if you already have several, decide which one your team should use for synced time and tell them, because every time entry in Current asks for it. Time entry refuses to send without one rather than guessing at a product that would bill a customer at the wrong rate.

Current does not turn every parent ticket into a project, because parent and child tickets are used for plenty of grouping that is not project work. Two things to decide now:

• ＋Which existing parent tickets are real projects. You adopt them one at a time from the "Projects from Syncro" list on the Syncro card, after the first sync.
• ＋Whether you want new parent tickets with a particular issue type, usually one named Project, adopted automatically from then on. That rule is off by default, and turning it on never reaches back for parent tickets you already have.

Syncro uses Leads for two different jobs: sales opportunities, and the inbound queue that support email lands in. Current only brings the sales ones into the CRM. A Lead reaches the CRM when its status is Opportunity, Prospect, Waiting on Client, In Negotiation, Pending, Won or Lost, or when it carries an opportunity amount above zero. Everything else stays in Syncro.

So before you connect, look at your Leads list and check that the ones you would call deals are sitting in one of those statuses or carry an amount. A real opportunity left at New with no amount will not appear in the CRM, and that is the gate working as designed rather than a missing record.

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

• ＋Two-way sync is on by default and controls whether Current writes task and project changes back to Syncro. Turn it off for a read-only start if you would rather watch first.
• ＋CRM write mode is off by default. Test mode lets pushes run against companies whose name starts with ZZ-Current Test, so you can prove the writes on records nobody bills.
• ＋Timer rounding and ticket-noise settings live on the Syncro card, and you can change them at any time. There is no workspace-wide default Labor product yet, so each person picks one on the time entry.

• ＋A user named Current exists, in a group with the permission list, and you hold its token.
• ＋Parent/child tickets are on, and so is Ticket Parent-Child, Edit.
• ＋At least one Labor product exists, and your team knows which one to pick when they log time.
• ＋Your real opportunities are in a sales status or carry an amount.
• ＋Your technicians' Syncro emails match their Current sign-ins.
• ＋You know whether you want two-way sync and CRM writes on from day one.