Skip to content
Current

What you need before you start with Current

4 min read · Updated Oct 22, 2026

Have five things ready: a tenant admin who runs setup (about 15 minutes), a work email address, admin access to your PSA so you can create an API user for Current, the list of people who need a login, and a card for the free trial. A Microsoft 365 global admin's one-time approval and single sign-on can come later. If the person with the PSA keys isn't around today, you can connect your PSA after setup.

Who should set it up

The person who creates the workspace becomes its first tenant admin and runs the setup wizard. Pick someone who can decide which PSA ticket queues matter, who on the team gets a login and which role each person has, and who can enter the card for the trial. Teammates who sign in before setup is finished see a note that their admins are still setting up Current. Your progress is saved at every step, so setup can stop and pick up again the next day.

A work email address

A new workspace starts from a work email. The signup form refuses a personal mailbox, such as Gmail, Yahoo, Outlook.com, Hotmail, iCloud, Proton, GMX or an internet provider's mailbox, and asks for your work address instead. Your email's domain fills in the workspace name. This rule applies only to creating a workspace: a teammate you invite later can join with any address.

Admin access to your PSA

Current connects to Autotask, ConnectWise PSA, HaloPSA, Syncro, Rev.io or SuperOps through an API account you create in your PSA for Current, never a person's own login. Creating that account needs an admin in your PSA. Each PSA has a checklist that lists what to create and which permissions to give it:

  • +"Prepare your Autotask before onboarding: the setup checklist"
  • +"Prepare your ConnectWise before onboarding: the setup checklist"
  • +"Prepare your HaloPSA before onboarding: the setup checklist"
  • +"Prepare your Syncro before onboarding: the setup checklist"
  • +"Prepare your Rev.io before onboarding: the setup checklist"
  • +For SuperOps, "Connect SuperOps to Current" lists the subdomain, API token and region it asks for.

Don't have admin access to your PSA? The setup wizard's PSA step has two ways forward. "Someone else has the admin keys? Send them the steps" emails a teammate the steps to create the API user and a link to the checklist. Connect it later records that you run a PSA and lets you finish setup, and you connect it from Settings › Integrations when the API user exists. If you don't use a PSA at all, choose "We don't use a PSA": projects, scheduling, time and the CRM all work without one.

Tip
Check your team's emails in the PSA
Current links each person to their PSA resource by matching the email address in your PSA to the address they sign in to Current with. That link is what lets them log time that reaches your PSA and see their PSA work on My Day. Fixing a mismatched address in your PSA before the first sync saves linking people by hand afterwards.

Microsoft 365 approval (can wait)

Calendar, Teams, SharePoint, Microsoft To Do and email capture come through Microsoft 365. A tenant admin approves Current once for your organization while signed in at Microsoft as a Microsoft 365 global admin, and after that each person connects their own account. If someone else is your Microsoft admin, they can type their own sign-in on your screen. This isn't part of the setup wizard, so it can happen any time after. See "Microsoft 365: SharePoint, Teams, and Calendar".

Single sign-on (optional)

You don't need single sign-on to start. People sign in with a password and a sign-in code from day one. To sign in through Microsoft Entra ID, Okta or Google Workspace instead, a tenant admin registers your identity provider later. Once it is registered, single sign-on becomes the only way in for everyone on those email domains, tenant admins included. See "Set up single sign-on (Microsoft Entra ID, Okta, Google Workspace)".

Who to invite, seats and the trial

  • +After the first sync, the wizard lists everyone your PSA knows about. You tick who needs a login and pick a role for each one. Roles can change later in Settings › Users and roles.
  • +Every staff login is a paid seat. Read-only partner viewers (your customers' contacts in the partner portal) are free and never take a seat.
  • +Seats are a pool you buy, with a minimum of three. Seat changes during the trial are free.
  • +A card is required to start the 14-day free trial. Nothing is charged that day, and the first charge lands on day 15. When another MSP referred you, the trial is usually longer (30 days for a peer referral).
  • +You agree to the Terms of Service on the trial step, after your data has arrived.

Prices, currencies and how the seat pool works are in "Seats, pricing, and what counts as a user".

A checklist to copy

  • +A tenant admin with about 15 minutes for the setup wizard
  • +Your work email address
  • +An API user in your PSA, or the email address of the person who can create one
  • +Your team's emails in the PSA matching the addresses they will sign in with
  • +The list of people who need a login, and the role each one gets
  • +A card for the free trial
  • +Later: a Microsoft 365 global admin for the one-time approval, and single sign-on if you want it
Was this helpful?