Your first 15 minutes: the setup wizard

The moment you create a Current workspace, a short setup wizard takes over — the app itself stays out of reach until it's done. It's about 15 minutes of honest questions: who you are, how you'd like to pay, which PSA you run (if any), and who's on your team. Your progress is saved at every step, so closing the tab and coming back tomorrow picks up exactly where you left off. Teammates who sign in before you finish see a friendly "your admins are still setting up Current" note rather than a half-configured workspace.

A welcome screen that lays out the five things ahead — plan and card, your PSA (or not), tidying up what syncs in, meeting your data on the first sync, and inviting your team — so nothing that follows is a surprise. It asks for nothing: your workspace was named at signup, and a logo and branding can be added later in workspace settings.

A card is required before you can use Current. We'd rather say that plainly than surprise you: entering it starts a 14-day free trial, nothing is charged today, and the first charge lands on day 15. The exact amount is shown on this very screen before you confirm — "First charge: $X for Y seats on <date>" — and we email it to you again three days before it happens. Cancel any time during the trial (a one-line reason is all we ask) and you're never charged. See "Cancelling your subscription (and what happens after)".

This step is also where you pick a plan and seats. For Round 1 founding workspaces — the first 100 MSPs — the rate is $50 per user monthly, or $45 per user billed yearly, locked for as long as your subscription stays active (list price is $95 / $85 after Round 1). The toggle shows the live math for your team size. Seats are a pool you buy (minimum 3): buy what you'll actually deploy, because adding more later is a two-click prorated charge, not a negotiation. Seat changes during the trial are free — the first charge simply bills whatever you settled on. There's a billing-email field here too, so you can point invoices at accounting@ right from the wizard. The full pricing picture is in "Seats, pricing, and what counts as a user".

The PSA step is a picker — ConnectWise PSA, Autotask, HaloPSA, or "We don't use a PSA" — and everything after it follows your choice: the prep checklist, the credential form, the mapping step, and the first sync are all shaped by the provider you pick. See "Autotask, ConnectWise, or HaloPSA: choosing your PSA in Current" for how to decide.

1. 1
   Run the prep checklist for your provider

   Autotask: an API-only user, the right security level, resource emails that match your team's Current sign-in emails, an active project type, and a billing code — each item links into "Prepare your Autotask before onboarding: the setup checklist". ConnectWise: a Developer Network clientId, an API Member with a least-privilege security role, the key pair, and your company ID and site URL — each item links into "Prepare your ConnectWise before onboarding: the setup checklist". Ten minutes in your PSA here saves an hour of head-scratching later.
2. 2
   Enter credentials and test

   Autotask: the API user's username, secret, and integration code — Current discovers your Autotask zone automatically. ConnectWise: site URL, company ID, public key, private key, and clientId — Current discovers your instance's API address automatically. Either way, a test connection runs before anything is saved.
3. 3
   Know what the test does — and doesn't — prove

   A passing test proves the credentials are right. It can't prove the API user has permission to see everything, so a permission gap sometimes only shows up at first sync — an entity that comes back empty or errors. That's normal, not broken: the wizard points at the fix, and "Reading the sync health dashboard (and fixing a stale sync)" covers the rest.

If you connected a PSA, one short review stands between the connection and the first sync — and it's the one that decides how clean Current feels on day one. Your PSA's ticket queues (Autotask) or service boards (ConnectWise) hold more than the work your customers ask for: alert and monitoring tickets, RMM automation, backup and BDR jobs, and spam or internal-IT chatter. Current highlights those four kinds with a "Recommended off" badge, because they're machine noise rather than customer demand — but it only ever recommends. Current never turns a queue or board off for you; you decide.

Turning a noisy queue or board off hides its tickets from Current immediately — they stop dragging down support history, sentiment, SBR stats, and AI insights — and nothing is deleted: flip it back on later and every ticket Current already synced reappears instantly, with new activity syncing again right away (tickets created while it was muted only return once an admin with CRM access runs a full ticket re-sync). You can do all of this here, or any time later from your PSA's Manage drawer under Integrations, and change your mind as often as you like. See "Ticket-queue noise: which queues and boards to sync, and which to mute".

This step also carries your won-quote settings — how a won quote gets fulfilled in your PSA: the default project type or board, the post-sale ticket queue or board, the waiting-on-order status, and the default procurement person. On Autotask it additionally carries industry mapping, which lines your company industries up with Autotask's Market Segments (ConnectWise has no Market Segments equivalent, so that panel simply doesn't appear for ConnectWise workspaces). Ticket-queue and board settings need no CRM access, so any tenant admin can manage them; industry mapping does need CRM access, and if whoever is running setup doesn't have it, the wizard says so and lets you defer that mapping to Integrations later.

If you connected a PSA, Current now pulls in your companies, contacts, projects, tickets, people, and time entries, showing live per-entity counts as they land. On a big shop this takes a while — and that's fine, because you can hit "Continue to team setup while this runs" and keep going. A very large first pull finishes through the background sync that runs every five minutes, so the counts keep climbing even after the wizard's own pass ends. Then comes the people-mapping review: Autotask resources or ConnectWise members whose emails match a Current sign-in are linked automatically (green), anyone unmatched gets a quick person-picker, and "invite later" is a perfectly good answer.

Add teammates by email and role, with a live seat meter ("using 4 of 8 seats") so you always know where you stand against the pool you bought. If you run out, an inline "Add a seat — free during your trial" button sits right on this step — no detour to Billing. This step is skippable — plenty of admins explore solo for a day first. Roles matter more than they look; see "Invite team members and assign roles" and "Roles & permissions: who sees what".

• ＋Integrations (in the sidebar, under Admin) — your PSA, Microsoft 365, and every other connector, including the one you may have skipped.
• ＋Billing (your initials menu, top right — admins only) — plan, seats, invoices, card, and the trial countdown. See "Manage your subscription: seats, plans, cards, and invoices".
• ＋Help (the Get Help entry in the same menu, or /help) — this help center plus Ask AI, the same one that sat in the wizard's right rail.
• ＋The in-app onboarding checklist takes over from here — see "Your first afternoon: the onboarding checklist" for the rollout order that works.