Skip to content
Current/ Help Center

Your first afternoon: the onboarding checklist

8 min read · Updated Sep 11, 2026

Rollout takes an afternoon, not a quarter. Connect your PSA and Microsoft 365 and your companies, contacts, projects, and history are already there. Here's the order that works.

The card in the bottom-right corner tracks it for you. It starts as Get Current set up and covers the essentials: your PSA (or the choice to run without one), your team, and a first project. Once those are in, the same card becomes Finish setting up and lists the optional pieces: your sales pipeline, what you sell, email sending, your workspace currency, Microsoft 365, your logo, and who gets alerted. Each line links straight to where it is done.

Set your workspace currency is the line to open if your books are not in US dollars. While this line is still open your workspace is on US dollars, because nobody has picked a currency yet; a tenant admin picks one in Settings under Workspace basics. It labels every amount Current shows and converts nothing. Your Current subscription is billed in US dollars either way.

Tip
Skip what doesn't apply
Every line on the Finish setting up list has a Skip. A workspace that never sends campaigns can skip email sending; one that doesn't use SharePoint can skip Microsoft 365. Undo puts a line back. The X hides the card for good, on every device you sign in from.

If a project is set to sync with a PSA but the workspace isn't ready to build it there yet — nothing connected, or no record linked to a PSA company — the project page says so before you press Build, and tells you who can fix it. If your workspace runs Current without a PSA at all, choose We don't use a PSA once and the reminders stop everywhere.

Heads up
Write-back is off by default
Until you deliberately enable push, Current only reads from your PSA. Nothing you do during onboarding touches your live PSA records.
Integrations → your PSA's card (ConnectWise PSA or Autotask). Manage opens the connection; Sync now pulls immediately.
  1. 1
    Connect your PSA
    Settings → Integrations → ConnectWise PSA, Autotask, or HaloPSA. Enter your API credentials; Current discovers your instance or zone automatically and runs a test connection before saving anything. See "Connect ConnectWise PSA and choose what syncs", "Connect Autotask and choose what syncs", or "Connect HaloPSA and choose what syncs" for the full walkthrough — one PSA per workspace.
  2. 2
    Let the first pull finish
    The initial sync brings in companies, contacts, projects, tickets, people, and time entries. Watch progress under Settings → Sync health.
  3. 3
    Connect Microsoft 365
    An admin configures SharePoint once for the workspace; each user connects their own account for Teams and Calendar. See the Microsoft 365 guide.
  4. 4
    Invite your team
    Settings → Members → Invite. Assign a role at invite time — roles scope what each person sees, so get this right before people log in.
  5. 5
    Review field ownership
    The ownership map decides which system wins for each field. Defaults are safe (your PSA owns billing-critical fields), but review it before enabling push.
  6. 6
    Turn on write-back
    When you're ready, enable push per entity — time entries, task dates, statuses. Each outbound write is confirmed by reading the record back.
Tip
Sandbox first
If you have a sandbox or test instance of your PSA (Autotask sandboxes are common), connect it first and run a test project through the full loop. The environment follows the credentials, so double-check which one you're pointed at.

Screen tours: the first time you open a key screen

The first time you open one of the key screens, a spotlight of three to five steps points out what matters on that page. It runs once, after the page has settled, and only when you are not already inside the tour or a walkthrough. The screens are My Day, Portfolio, a project and its Boards, List, Dependencies, Timeline and Calendar views, Schedule, Time entry, Playbooks, Integrations, Settings, Users & roles, Dashboards, Reports, Sync health, Sales Home, Companies, a company record, Contacts, Deals, My Deals, Leads, Campaigns, Sequences, Lists, Whitespace, Renewals, Business Reviews, Goals and Commissions. You only get the ones your role can open.

Afterwards a New here? card sits at the top of that page with three best practices for it, a button that replays the spotlight (it reads Show me until the tour has run, then Replay the tour), and Read the playbook, which opens the playbook for your role in this help center in a new tab. The X on the card hides it on that screen for good; the replay stays on Learn Current. Tours never run automatically during a support session, and Learn Current → Preferences switches the automatic ones off altogether while the card and every replay keep working.

Walkthroughs: do it with me

A walkthrough sits beside you while you do the real thing for the first time. It is not a video and not a demo. It highlights the button you need next, then waits: the step only moves on once you have actually done it, so you can read the screen, stop to think, or go and find something before you carry on. Skip this step is on screen the whole time, and nothing is ever locked while a walkthrough is running. On your first time entry, Current offers the walkthrough above the form and you can save without it. There are five sets, and you only see the ones that fit your role, so a salesperson is never offered the time-entry walkthrough and an engineer is never offered the deal one:

  • Getting going: create your first project, log a time entry, move a deal forward.
  • Admin setup: invite the team, connect your PSA, set cost rates, brand kit, lead routing.
  • Project depth: add a dependency and see the critical path, set your PTO, run a scenario, use a playbook, share a project with a partner viewer.
  • Sales depth: build a list, save a first campaign, build a sequence, open a whitespace opportunity, build a first business review, convert a won quote.
  • Insight: build your first dashboard, put a dashboard on a TV, schedule a report.

Every one ends on the real thing you made: a real invitation, a real dependency on the map, a real list, a real TV link.

Where to start one

  1. 1
    Show me, on the setup cards and on your journey
    The rows on the corner cards that have a walkthrough behind them carry a Show me link: your own Getting started card, and the workspace setup card that admins see. So does every journey step on Learn Current that has one. Press it and the walkthrough starts on the page where the work happens.
  2. 2
    Learn Current
    Open the menu behind your initials at the top right and choose Learn Current, or click the small ring beside What's New in the top bar. Every walkthrough set, every screen tour and every playbook that applies to you is listed there, each walkthrough with roughly how long it takes, so you can run one whenever you like rather than only the first time.
  3. 3
    Replay the tour, on Learn Current
    The short guided tour you got on your first sign-in is on Learn Current too: press Show me on the Take the tour step. Take it again any time, and as often as you want.

Your journey: Day 1, Week 1, Month 1

Learn Current lays out a path for your role in three phases: Day 1, Week 1 and Month 1. Each step carries a one-line reason it matters, a Do it button that opens the screen, walkthrough or tour, and Show me where a walkthrough exists. Skip any step. Steps Current can see for itself (a time entry, a linked PSA identity, a calendar connection, a walkthrough or screen tour you ran) tick themselves; a Done button appears only on a step the app cannot see. The ring in the top bar fills as you go and turns into a check when the journey is done.

Finishing shows a quiet You know Current card on Learn Current, and your profile menu carries a line, Knows Current, with the month and year. There is no badge art and no leaderboard. Partner viewers get a three-item welcome path on the portal instead, and never a tour, walkthrough or journey from the staff app.

Learning emails

In your first two weeks you get four short emails, written for your role: your first hour on day 1, one habit on day 3, one best practice on day 7, and one thing most people miss on day 14. Each one carries a Stop these emails link, and the same switch lives under Learn Current → Preferences. They only ever go to someone in their first two weeks.

Preferences: two switches

  • Run tours automatically. Off means no first-visit spotlight launches on its own; the New here? card, its replay button and every replay on Learn Current keep working.
  • Learning emails. Off stops the four emails; on resumes them for anyone still inside their first two weeks.

Who can see how you are getting on

Your workspace admins can see which setup steps and walkthroughs each person on the team has finished, and the date each one was finished, on Users & roles. The same line prints the phase of the journey each person is in (Day 1, Week 1, Month 1, or Knows Current with the month they finished) and one figure for screen tours, Screen tours: 8 of 12. Steps you chose to skip show as skipped rather than as missing, and if nothing has moved for a while the row prints how many days it has been. Current does not record how long you spent on anything, does not time you, does not rank people against each other, and has no leaderboard. The point is so an admin can spot the teammate who never got their PSA identity linked, not to score anyone. Your own Getting started card carries a line saying so, so nothing about this is behind your back.

Note
Support sessions are not credited to you
When someone from ITPartners+ is inside your workspace helping you, nothing from that session is credited to you or to anyone else on your team: no walkthrough, no tour, no step you ticked yourself. The database refuses that write rather than the screen hiding it. Steps Current works out from your real data are the exception, and they always tell the truth about your workspace: if your PSA identity gets linked while someone is helping you, that step reads as done, because it is done.

A workspace that runs Current without a PSA is scored on the steps it can actually do. The PSA steps are not counted as missing and never show as behind; they do not apply, and the progress you see is out of the steps that are yours.

Was this helpful?