How to run a workspace in Current

A workspace admin (the Tenant Admin role) owns four things in Current: who is in the workspace and what each person can see, the connections that feed it, the settings every number reads from (currency, holidays, cost rates, branding, notifications), and the health of the sync between Current and your PSA. This playbook is the order to do them in, what to look at each day and each week, the rules the product holds you to, and what a well-run workspace looks like a month in.

1. 1
   Settings → Workspace basics

   Pick the word your team uses for the businesses you serve and the currency your books are kept in. Both are workspace-wide. The currency labels every amount and converts nothing, so a figure recorded as 4,000 reads as 4,000 of whatever you pick; change it only when the books really changed. Only a Tenant Admin can, and every change lands in the audit log.
2. 2
   Integrations: connect your PSA, or say you don't use one

   One PSA per workspace: Autotask, ConnectWise PSA, or HaloPSA. Current discovers your instance from the credentials and runs a test connection before saving anything. A passing test proves the credentials; a permission gap only shows up at first sync, as an entity that comes back empty. Then the noise review: your ticket queues or boards hold alert, RMM, backup and spam traffic that Current badges Recommended off, and you decide. Write-back stays off until you enable it per entity. If you run without a PSA, choose We don't use a PSA once and every reminder stops.
3. 3
   Sync health

   Sync details on your PSA's card opens it (or type Sync health into ⌘K). Four numbers at the top, job states, live telemetry and the outbox. Watch the first pull land here: companies, contacts, projects, tickets, people and time entries, with counts still climbing after the wizard's own pass when a large book finishes through the background sync.
4. 4
   Users & roles

   Invite by email with a role. The role scopes what a person sees the moment they sign in, so set it now rather than after. CRM access is a separate switch on each person, and the Sales Manager sub-toggle appears once it is on; Tenant Admins start with both. Link each technician to their PSA identity here too: until a person is linked, no time they log can reach billing. Teams group reps so a manager's views open focused on their own people.
5. 5
   Settings → Cost rates

   Each person's internal hourly cost. For anyone linked to a PSA identity it syncs on every people sync, and this card is the one place an override sticks; anyone your PSA holds no cost for gets a rate you type. Rates are Tenant Admin only everywhere in Current. They feed the Profitability report and the account-level profitability figures the sales team reads as aggregates.
6. 6
   Holidays

   One calendar per workspace. Where your PSA carries a holiday calendar Current reads it; otherwise you add the days by hand. Every schedule, every capacity figure and every date Current pushes to your PSA skips them.
7. 7
   Settings → Branding

   A logo, a favicon and two brand colours. Current derives a readable palette and puts it on every Strategic Business Review, the partner portal, and the emails it sends on your behalf.
8. 8
   Notifications

   Who gets alerted for what: sync failures, integration alerts, project health, new leads. See "Notification routing: who gets alerted for what".

Eight of the walkthroughs are written for this role: invite the team, connect your PSA, set cost rates, brand kit, lead routing, build your first dashboard, put a dashboard on a TV, and schedule a report. Each one highlights the control you need next and waits until you have pressed it, so it ends on a real thing: a real invitation, a real connection, a real rate. Start any of them from Learn Current (in the menu behind your initials, or behind the small ring beside What's New) or from Walkthroughs in that same menu. Nothing is locked while one runs, and Skip this step is always on screen.

• ＋Sync health, or the sync badge on any project header: Synced, Sync error, Awaiting sync or Current-only. The Stale (7d+) filter on Portfolio finds projects that think they are syncing and are not.
• ＋Users & roles for anyone waiting: an SSO sign-in to approve, a pending invitation to resend, a new technician with no PSA identity yet.
• ＋The bell. Sync failures and integration alerts land there and in email according to your routing.
• ＋Radar on My Day if you also run projects; the morning brief on Sales Home if you also sell.

• ＋Reports: fifteen reports on one date range with a comparison to the period before. Schedule the ones you read every week. One schedule holds up to eight reports in one PDF, sent weekly or monthly at an hour in your time zone, and each recipient's copy is computed as that person, so a schedule you set up for the team can never hand anyone a number they could not open themselves.
• ＋Profitability, on Reports. It is listed for Tenant Admins only, because it reads cost rates.
• ＋Field ownership, in your PSA's Manage drawer, before you turn on push for a new entity. Your PSA owns the billing-critical fields, Current owns the scheduling overlay, and each outbound write is confirmed by reading the record back.
• ＋Billing, in your profile menu: seats in use against the pool, invoices, the card. Seats are a pool, and adding one is a prorated charge.
• ＋The audit log under Workspace: role changes, currency changes, deletions and tag changes are all there.
• ＋Users & roles, for how the team is getting on (below).

Dashboards, pinned under Portfolio, starts every workspace with an MSP Scorecard, and you build the rest by describing the number you want. For the office screen, Present mode fills the display and rotates between dashboards; a TV link is a private URL a smart TV opens with no login, minted from the dashboard menu and shown once. What a TV link shows is decided tile by tile: the service desk numbers and the recurring revenue tiles reach it, and a cost rate, a per-technician breakdown, an open deal or a margin never does, whoever minted the link. Revoke it and the screen goes dark within a minute.

• ＋One PSA per workspace, and a synced project is always named for the provider it syncs to. Current-native is the default for a new project and makes no PSA call at all. Converting a native project into your PSA is permanent and needs an explicit confirmation from one of the deploy flows, so a stray request fails closed.
• ＋Write-back is off by default. A fresh workspace only reads. You enable push per entity, the field-ownership map decides which side wins each field, and a disagreement the map cannot settle is logged for a person rather than overwritten.
• ＋Time that cannot reach billing is never recorded as if it could. The time-entry guard refuses an entry on a Current-native project, on an unsynced task, on a ticket type your PSA will not take, and from a person with no PSA identity, and it names the reason. Fix the data, never the guard.
• ＋Money stays behind the admin wall. Cost rates and the per-technician breakdown are Tenant Admin only. Sales leadership and account executives read account-level aggregates through the profitability card, and a Partner Viewer reaches no financial field on any surface, enforced in the database rather than by a hidden button.
• ＋Roles are enforced in the database. Only a Tenant Admin invites, changes roles, deactivates, or creates a partner invitation; a project manager who tries the last one gets Not authorized from the database itself. Nobody in your workspace can grant super-admin.
• ＋Currency relabels; it does not recalculate. A quote priced in another currency still creates its deal, flagged, and a PSA base currency that differs from the workspace currency is reported at connect time and left alone.
• ＋A company that came from your PSA is never deleted in Current. Deactivate or delete it in the PSA and the next sync mirrors that. A Current-only company is deleted by typing DELETE, with its contacts, deals, notes and tags, and every deletion is written to the audit log.
• ＋Nothing done inside your workspace by someone from ITPartners+ during a support session is credited to anyone on your team: no walkthrough, no tour, no step. The database refuses the write.

Users & roles shows, under each member, the setup steps and training they have finished with the date of each: PSA identity, first project, calendar, first time entry, the tour, and every walkthrough they have run. It also prints the phase each person is in (Day 1, Week 1, Month 1, or Knows Current with the month they finished) and one line for screen tours, Screen tours: 8 of 12. Steps that do not apply to a role, or to a workspace with no PSA, are not counted; a skipped step reads as skipped; and a row with nothing new for a while prints how many days it has been. Current records no durations, times nobody, ranks nobody and has no leaderboard, and each person's own Getting started card says the admin can see this.

• ＋Sync health shows every entity green, nothing in the dead-letter queue older than a day, and a last full sync inside its schedule.
• ＋Every technician who logs time is linked to a PSA identity and carries a cost rate, synced or typed.
• ＋Roles match what people do: nobody with CRM access who should not have it, and no Tenant Admin who only needed Project Manager.
• ＋Write-back is on for the entities you decided on, with field ownership reviewed once.
• ＋One scheduled report reaches the people who run the business, and a dashboard hangs on a screen if you have one.
• ＋Your logo is on the review cover and the portal, the currency and the customer word are right, and the holiday calendar has the whole year in it.
• ＋Users & roles shows the team at Week 1 or later, with nobody stalled for two weeks.