Frequently asked questions
The short answers. Ask the search anything for a sourced one.
No. There is no setting for it anywhere: not per person, not per workspace, not for a Tenant Admin. Every password sign-in to Current finishes with a second factor, which is the 6-digit code emailed to the address on the account, or an authenticator app or passkey once someone has added one. Current holds live PSA billing records, partner project data and your whole CRM, so a password on its own is never enough to reach it. What you can change is which factor and for how long a browser is remembered: a Tenant Admin can raise the floor from Email code to "Authenticator app or passkey", and can shorten the trusted-device window from 30 days to 14 or 7, both in the Sign-in panel at Workspace → Users & roles. Each only moves in the tightening direction, and each is written to the audit log. The one way to stop seeing codes altogether is single sign-on: register your identity provider and everyone on your verified domains signs in through it, with its MFA doing this job.
No. An SSO sign-in never triggers a Current code, because your identity provider is the second factor and its MFA and conditional-access rules are what apply. From the moment you register a provider, everyone whose email is on a domain you verified signs in through it, Tenant Admins included, and there is no exemption to hand out. People at other domains keep a password and a second factor: a Partner Viewer at their own company, a contractor on their own address, anyone invited at an address you do not own. Your provider cannot authenticate those accounts at all, so the mandate would only lock them out. One more thing worth knowing: if somebody on your domain already had a password account, their first SSO sign-in merges it into the SSO identity, so their role, history and time entries stay on a single profile.
Use one of the ten recovery codes Current issued when you registered single sign-on. Sign in with your email and password, and when you land on the "Sign in with single sign-on" page, open "Workspace admin? Use a recovery code" and enter one. That opens 12 hours of password sign-in for that one Tenant Admin, who still completes the normal second factor. Codes are single-use, only a Tenant Admin of that workspace can redeem one, and every use writes to your audit log and notifies your other admins and ITPartners+. If the codes are gone or sitting behind the same provider that just failed, contact ITPartners+: a super admin can open a password window of 1 to 24 hours for the whole workspace, any admin can close it early from the single sign-on card on Integrations, and it closes itself when the time runs out. That card also shows how many codes are unused and carries Generate new codes, which replaces the whole set at once.
Yes. In the Sign-in panel at Workspace → Users & roles, the Second factor for password sign-ins row has a Require an app or passkey button. From then on the emailed code is not offered to anyone signing in with a password: people who already have an app or a passkey carry on unchanged, and anyone without one is asked to set one up at their next sign-in, before they reach the workspace. Any TOTP app counts — Microsoft Authenticator, Google Authenticator, 1Password, Bitwarden — and so do passkeys (Face ID, Touch ID, Windows Hello, a security key) wherever the platform has them switched on. The change cannot be undone: a workspace that requires an app cannot go back to email codes. The panel's roster shows who has an app or a passkey and who is still on the emailed code. If somebody loses the phone their app was on, choose Reset second factor beside their name there (or in the ⋯ menu on their row): it clears their factors, un-trusts their browsers, and they start over at their next sign-in; ITPartners+ support can run the same reset when no admin can get in.
30 days by default, counted from the moment a second factor is verified on that browser. A Tenant Admin can shorten it to 14 or 7 days in the Sign-in panel at Workspace → Users & roles, and the change reaches devices that are already trusted: a browser trusted 28 days ago on a workspace that has just chosen 7 days is challenged on its next visit. The window only moves down, so once a workspace has chosen 7 days it cannot go back to 14 or 30, and 30 is the ceiling for everyone. Trust is per browser rather than per person, which is why one person can be challenged more often than the colleague beside them: a new machine, a second browser, a private window, or anything that clears site data on exit asks for a factor again.
Yes, and since September 11, 2026 it is on from the start. The switch is Satisfaction surveys, in Workspace → Integrations → the PSA card → Manage, just under the two-way sync switch; a Tenant Admin can switch it off there. While it is on, Current reads the survey answers already sitting in your PSA and uses them everywhere it uses CrewHu's: the Customer surveys card on the company record, the CSAT gauges on dashboards, the satisfaction section of an SBR pack, the urgent follow-up to-do, and the churn flag. The first read reaches back 12 months and the lane runs about once an hour after that, re-checking the last 45 days so a late answer still lands. Current only reads: it never sends a survey and never writes anything back. Each PSA needs one permission — Autotask's two survey-rating checkboxes under Security level → Other → Surveys (on by default for the API User level), ConnectWise's Service Desk → Service Survey: Inquire All (older instances list it as Companies → Surveys), and for Halo the API application's own permissions, which is where its ticket and feedback access is set. Scores become Positive, Neutral or Negative on fixed rules: Autotask 4–5 stars positive, 3 neutral, 1–2 negative; ConnectWise by share of the points available, 80% or more positive and under 50% negative; Halo by your own feedback bands where they can be read, otherwise the same 1–5 or 0–100 rules.
No. When both have scored the same ticket, the ticket counts once and CrewHu's answer is the one that counts. Current drops the PSA copy and keeps the ticket and the technician it carried on the CrewHu row, so the 90-day counts on the company record, the churn math, the dashboard gauges and the CSAT by technician leaderboard each count that ticket a single time, and one ticket never raises two follow-up to-dos. Tickets only one system scored count normally from whichever one scored them. You do not choose a winner anywhere: leaving both switched on is a supported setup, and the settings on the Survey alerts & churn flag card — which readings alert, when the to-do is due, the churn window, count and percentage — cover both sources at once.
Three things account for almost all of it. First, the clock: the lane reads about once an hour and makes no call at all while the switch is off, and the first read walks back 12 months, so give it a cycle before treating it as broken. Second, a permission gap: if the PSA refused the survey endpoint, the first-connect diagnostic on the connector records the refusal in plain words, and the lane sleeps until the next cycle instead of hammering it — grant the line for your PSA (Autotask's two survey-rating checkboxes, ConnectWise's Service Survey: Inquire All, Halo's API application permissions) and the next read picks up on its own. Third, what the surveys carry: one that was sent and never answered is not a score, so it is skipped, and so is one Current cannot tie to a company. A survey finds its company through the ticket it was about, so that ticket has to be one Current has synced — the diagnostic counts the unmatched ones separately so you can tell which of the two you are looking at.
So Reports can say where your business comes from. Both New deal dialogs and the manual New lead form ask for one, and Create stays off until it is picked while your workspace requires it (an admin can switch that off in Settings → Lead source). The choices are your PSA's own lead-source list — on Autotask, the opportunity's Lead Referral list — so the value is written to the opportunity when the deal pushes; with no PSA connected the field is free text. A deal on a company that is already a customer starts as Existing customer; change it if a referral or campaign brought that deal in. Deals that predate the rule show a short strip asking for it the next time they are opened, and Reports → Deals by type has a Where deals come from table.
Current reads the bounce report from the sender's Microsoft 365 inbox. A hard bounce (the address does not exist) puts the address on the Do not email list as Bounced, turns the contact's email badge to Invalid, writes a note on the contact's timeline, ends every sequence the contact is in with the exit reason Bounced, cancels their pending Outreach queue items, and drops any queued campaign send to them. A soft bounce (mailbox full, a temporary refusal) is only noted, unless it is the third for that address inside 30 days, which counts as hard. The contact is never deleted. Once a day the sequence's owner gets one bell with the count and a link to the list. Fix the address on the contact and the badge clears; the old address stays blocked. A bounce only counts for an address Current itself emailed in the last 30 days, so a forged bounce cannot block a real contact. Optionally, under your PSA's Integrations drawer, an admin can have a hard bounce also deactivate the contact in Current and, on workspaces whose PSA supports it, in your PSA.
Under Sales → Lists, pinned at the top as Do not email. It moved there from the Email (Resend) integration tile on September 10, 2026, and gained an export. Everyone with CRM access except Partner Viewers can search it and export it as a CSV whose columns are email, reason, source and added_at. Sales leadership (a sales manager, or anyone with the sales leadership flag) and tenant admins can add an address by hand, upload a CSV, and remove addresses that were added by hand. An entry that came from a person's own unsubscribe click, a bounce, a spam complaint or an email verification is locked for compliance and cannot be removed by anyone. Adding an address ends that person's sequence enrollments immediately and drops any queued marketing send to them.
Yes, on purpose. An unsubscribe is an opt-out from marketing, and a service notice campaign (a price change, an outage note, a renewal) is not marketing, so it still reaches those people; sequences and marketing campaigns skip them. What stops every kind of mail, service notices and app notifications included, is a bounced address, a spam complaint, or an address that verification marked invalid. That last one is a change made on September 10, 2026: before it, an invalid address still received notifications.
Only during your workspace's business hours. Current reads the time zone, working days and desk hours you set under Settings → Workspace basics, plus your holiday calendar, and holds every outbound step (an email, a task, a LinkedIn touch) until the desk is open. A step that comes due at 6 AM waits for opening time that day; one that comes due at 7 PM on a Friday waits for the next business morning. On top of that, each mailbox sends at most 250 sequence emails a day, counted on the same calendar, so a large enrollment works through at 250 a business day. Delay timers and reply windows keep counting around the clock; only the moment an email reaches someone is held. The per-sequence Business days switch controls the working-day part; the hours apply to every sequence.
That was a bug in how the opening was placed, fixed on 10 September 2026: a greeting written as a bare "Jane," line (the way the AI builder writes them) was not recognised as a greeting, so the opening was put in front of it. Now you control the spot with the {{personalization}} tag: put it on its own line after your greeting and the one or two opening sentences land exactly there. The AI builder writes every email with the tag already in place, and it is a chip in the Personalize palette for steps you write yourself. A step without the tag gets the opening after its greeting line, whether that line reads "Hi Jane," or just "Jane,". If personalization is off, or the AI has nothing real to say about someone, the tag disappears and the plain email sends. The subject line is never changed.
Because of how a sequence sends. Every sequence email leaves one person's own Microsoft 365 mailbox at 250 a day, so 1,000 people is already four business days per step, and that mailbox carries the bounce and spam-complaint risk for the whole list. Past that size a Campaign is the right tool: it reaches everyone at once from your workspace's sending identity (a Resend domain you verified, or the sender's mailbox if you have not set one), with unsubscribe handling built in, and a campaign's audience has no size limit tied to a sequence. Send the campaign, then enroll the people who reply into a sequence for the personal follow-up. The 1,000 counts people currently in the sequence, so anyone who replies, unsubscribes, finishes, or is removed frees their spot and an evergreen sequence keeps taking new people. The enroll panel shows the room left before you click; an enrollment that would go past the limit is refused as a whole with the numbers, never trimmed to fit. Sequences that were already above 1,000 when the limit arrived keep everyone and keep sending, and simply cannot add more until they drop under. Super admins are not held to the limit.
Two places. On the screen itself, the New here? card at the top of the page has a button that replays the spotlight: it reads Show me until the tour has run once and Replay the tour after that. If you closed the card with its X, open Learn Current (in the menu behind your initials at the top right, or the small ring beside What's New in the top bar) and every screen tour that applies to your role is listed under Screen tours with a replay beside it. The X hides only the card on that one screen, so a replay is never lost. A replay records nothing new about you, and it runs the same three to five steps you were shown the first time, dropping any step whose control is not on the page right now.
Yes. Open Learn Current and, under Preferences, switch off Run tours automatically. From then on a key screen you open for the first time shows its New here? card without launching the spotlight, and you can still press Show me on the card or replay any tour from Learn Current whenever you want. The first-login tour is separate and unaffected; Show me on the Take the tour step of Learn Current brings that one back. The switch is yours alone, only you can change it, and it applies on every device you sign in from. Two things never run automatically whatever the switch says: nothing runs during a session where someone from ITPartners+ is helping inside your workspace, and nothing runs while another tour or walkthrough is already open.
Press Stop these emails at the bottom of any of them: it opens Current signed in and records the choice, and no more are sent. The same switch, Learning emails, lives under Preferences on Learn Current, where you can turn it back on. There are only ever four, written for your role, on days 1, 3, 7 and 14 after you join (your first hour, one habit, one best practice, one thing most people miss), and they go only to someone in their first two weeks, so after that there is nothing to stop. Stopping them changes nothing else: your journey, the tours and the walkthroughs stay exactly as they are.
Users & roles, under Workspace in the sidebar. Under each member's name is one written line: the setup steps and the training they have finished with the date of each (PSA identity, first project, calendar, first time entry, the tour, every walkthrough they have run), the phase of the learning journey they are 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. A skipped step reads as skipped, a step that does not apply to their role or to a workspace without a PSA is not shown or counted, and a row with nothing new for a while prints how many days it has been. Current records no durations, times nobody and ranks nobody; there is no leaderboard anywhere. Nothing done while someone from ITPartners+ was helping inside your workspace is credited to anyone. Each person can see the same line on their own Getting started card and on Learn Current, together with a note that their admins can see it.
Yes. Open Funnels on the Leads page, click Settings on the funnel, and under Automatically tag new leads pick one of your existing tags: every lead that lands in that funnel, or is moved into it, gets the tag on its company and its contact. A booking link has the same setting, Tag people who book, on the Booking links page: everyone who books through that page is tagged the moment the booking lands. Both pick from tags that already exist, so create the tag first, on a company or contact record or under Settings → Tags. Leads and bookings from before you picked the tag are not tagged after the fact. Once the tag is on, filter the Companies list by it or build a campaign, list, or sequence audience on it.
Yes. A sales manager or admin creates a send-as identity under Settings → Email signature: the shared Microsoft 365 mailbox's address, the From name, a job title and phone for the signature, which logo the signature carries (none, your workspace logo, or the Current wordmark), an accent colour, and optionally a booking page of its own. Then open the sequence, and under Send from pick the identity instead of the owner's mailbox. From that moment every email leaves from the shared mailbox, signed as the identity, with the Book time with me button pointing at the identity's page, and contacts already in the sequence get their next email from the new address. The owner is still the host: their Microsoft 365 connection sends, and the identity's booking page puts meetings on their calendar. Two things have to be true in Microsoft 365: the host needs Send As or Send on Behalf permission on the shared mailbox, and your organisation must have approved the Current app's Mail.Send.Shared permission. If either is missing, the first email pauses the enrollment with a message saying which one. Replies land in the shared mailbox, which Current adds to CRM email capture automatically, so a reply still exits the contact.
On a static list's Members tab, tick the checkbox on each row (or the header box for the whole page), then click Remove from list in the bar that appears and confirm. They come off the list together and the toast offers an Undo for a few seconds. The contacts themselves are not deleted — they stay in your CRM, on other lists, and in their sequences.
Open the company record and expand Quotes & opportunities in the right rail. The three numbers at the top are the MRR quoted across everything open, the one-time money quoted, and the MRR already on contract. Below them, each open opportunity links straight into your PSA, and each quote shows the tool it lives in, its state and expiry, and a link into that tool. Money is counted once: a quote attached to an open opportunity never adds to the totals twice. If Quoter or Kaseya Quote Manager quotes show as plain text, an admin needs to enter that tool's web address on Integrations, on its own card, because those accounts each live at their own address and neither API reveals it.
Under Settings → Tags, a sales manager or workspace admin sees every tag with the number of companies and contacts carrying it and the audiences that filter on it. Use the row menu: Merge into… moves everything onto the tag you keep, updates any campaign, list, or segment that filtered on the old one, and removes it. Delete takes one click for an unused tag; a tag still on records asks you to type DELETE because those records lose the label. A tag an audience still filters on can't be deleted, only merged, so no send changes reach by accident. Every change lands in the audit log.
There shouldn't be any more. Current auto-creates a renewal deal about 90 days before a recurring agreement's end date, while that agreement is still active, and it used to leave the deal on the board forever afterwards. That is a problem because closing the old agreement is a normal part of renewing: you end it in your PSA and write a new one, often folding a site or a service into a larger agreement. The old agreement goes inactive, and the renewal deal Current made for it has nothing left to renew, but it kept sitting in the pipeline and counting toward your totals. Current now watches the agreement behind every auto-created renewal. When it stops being active in your PSA, whether that reads as inactive, cancelled or expired, the deal is hidden: off the board and the list, and out of your pipeline value, your goals, your dashboards and your reports. Nothing is deleted and nothing is marked lost, so if the agreement goes active again the deal comes straight back. This only ever applies to a renewal nobody has worked. The moment anyone moves it to another stage or edits it, it stays on your board no matter what the agreement does, because you may well be negotiating that exact renewal while the old agreement is being closed out. Renewals you created by hand are never hidden either. To look at the hidden ones, set the Ended renewals filter on the Deals page to Shown; the number beside it says how many are being held back, and each one carries an Ended chip beside its deal type. Reset filters puts it back to Hidden.
Lost Reason is a company field, so open the list, campaign, or sequence audience builder, add a Company fields row, and choose Lost Reason. The comparison opens on is any of with a checkbox for every reason on your list plus any value already stored; switch it to is none of and tick the reasons to leave out, say Price and Went with a competitor. The live count drops as those companies leave, and a company with no lost reason recorded stays in. The same row works on the Companies directory's Company fields filter, and every other dropdown or text field, yours or synced from your PSA, gets the same checkboxes.
Deleting is for sales leadership and tenant admins, from the Danger zone at the bottom of a company record or from the bulk bar on the Companies list. A company that came from your PSA is never deleted here; the Danger zone says so, and the bulk bar marks it as skipped. Deactivate or delete it in your PSA and the next sync mirrors that. A company linked to HubSpot, one with a won deal or an open project, or one mid-sync is kept too, and the result names the reason. For a company that lives only in Current, typing DELETE removes it with its contacts, open and lost deals, notes, tags, and list memberships. It can't be undone, and every deleted record is written to the audit log.
Integrations → Email (Resend) → Manage walks it as five steps and ticks each one off as it lands. One, connect Resend: create a free account at resend.com, make an API key, and paste it in. Two, choose your sending domain, something like news.yourcompany.com that you keep for outreach rather than the domain your everyday mail uses, and press Create in Resend and get DNS records. Three, add those records at whoever runs your DNS. Four, press Check verification, which asks Resend to re-read your DNS and reports back per record. Five, turn on real sending, which is the switch that ends preflight, because until it is on every campaign reaches only your own team's addresses no matter what the audience says. Budget about ten minutes plus however long your DNS takes to propagate. Only a tenant admin can do any of it; everyone else with CRM access sees a line on the Campaigns page naming the admins to ask. If you would rather not touch DNS at all, sequences and account-manager-mode campaigns can send from each person's own connected Microsoft 365 mailbox instead.
Almost always because the tracking DNS record has not verified yet. Resend measures an open or a click only through a tracking subdomain, links.yourdomain, and that CNAME is one of the records step 3 of the email setup lists. Mail sends perfectly well without it, which is why the report can read 0% while the campaign is landing and being read. Add the links CNAME at your DNS host, press Check verification in step 4, and the wizard's "Open and click tracking" line moves from waiting for DNS to on. Two things to watch. On Cloudflare, the record has to be DNS only, the grey cloud, because a proxied record never verifies. And tracking is not retroactive: emails sent before the record verified stay untracked, so it is worth doing before your first real send rather than after. If tracking is on and the report is still empty, check the webhook instead: delivery and open events reach Current through a webhook you register in Resend, in the same Resend account as your API key.
Yes, both. In a campaign the body is a stack of blocks, and two of them carry files — Picture and PDF — which you place anywhere in the message and move up or down like any other block. A sequence email step takes one picture and one PDF, and they always send below your message and above your signature. Pictures are resized and compressed in your browser before they upload, so a six-megabyte photo straight off a phone becomes roughly 300 KB at a size that suits email and you do not have to prepare anything first. JPG, PNG and WebP are accepted, up to 10 MB before compression, with up to ten pictures in one campaign. Animated GIFs and SVG files are not accepted: a GIF cannot be compressed in a browser without flattening it to a single frame, which would quietly destroy the thing you picked it for, and an SVG is a document that can carry scripts. Give every picture a short description, because many mail clients block images until the reader clicks and that description is what they see in the meantime. One thing to know before you upload: a picture has to be readable without anyone signing in, or mail clients could never display it, so files added here sit at a public web address. The address is random and nobody can browse the list, but treat it as marketing material only, never anything private. Files belong to the campaign or sequence you added them to, so deleting that deletes the files, and a file you upload and then remove is tidied up automatically about a week later. There is no storage limit to manage.
Because an attachment would work from some workspaces and quietly fail from others, and it would hurt your delivery rate everywhere. Two separate reasons. First, bulk email carrying attachments is one of the more reliable ways to land in a spam folder, so a campaign with a file stapled to it reaches fewer inboxes than the same campaign with a link. Second, campaigns and sequences leave by one of two routes — your workspace's own Resend key, or the sender's Microsoft 365 mailbox — and Microsoft caps the entire message at a few megabytes, while Resend allows far more. A real attachment would therefore behave differently depending on which route your workspace uses, and a test email would stop being a reliable preview of what your audience receives. A download button behaves identically on both routes, has no practical size ceiling, and if you send on your own Resend key you can see who clicked it in the campaign report. The reader gets a labelled button — you write the label, something like Read the guide — with the file type and size underneath.
Open the renewal deal for that account and open its renewal dossier: the private profitability section is on screen as soon as it loads, for anyone allowed to see financials. It sets the last twelve months of revenue against what the account actually cost to serve: service ticket labor mirrored from your PSA, project time tracked in Current, and the vendor cost carried on your contract lines. The verdict at the top is labeled "Recurring services margin" and judges the recurring contract on its own, because a renewal re-prices the contract and not last year's project. It reads green, amber or red against margin targets a workspace admin sets, starting at 55 percent gross margin for green and 40 for amber. When an account sits under the green target, the banner names the MRR that would reach it at what the contract costs to serve, and that is the number to walk into the renewal conversation with. Projects and one-time work sit beside the verdict rather than inside it: a "Revenue and cost by type" table shows recurring services, projects, one-time and T&M, anything the rules could not place, and an all-in line, with hours attributed by the billable flag your PSA already holds. Project and one-time revenue come from your PSA's billed items, and until those have been mirrored for your workspace they read "Revenue not mirrored yet" rather than a zero. Labor is priced from each active technician's own PSA cost rate, whether or not that person has a Current login, and hours worked by somebody your PSA holds no cost for, or who is no longer active in it, are still counted, priced at your team's median rate and labeled as estimated. On the vendor side, contract lines are counted three ways rather than lumped together: lines that carry a cost, lines your PSA records at zero, which some services genuinely are, and lines with no cost on file at all. Sales leadership and admins can open "See lines" on the vendor tile for the line-by-line table behind that figure. The same profitability card now sits on the company record itself, under Sync & system, for any account on an active recurring contract, so you can ask the question without opening a renewal deal. Sales leadership and account executives see the account numbers; the breakdown by technician is for workspace admins. The section is internal, and it stays off a printed dossier unless you tick "Include internal profitability in the print" beside Print / PDF, which stamps the printout with an INTERNAL watermark.
Because the people who can open it are the people who need it. The section is on screen the moment a renewal dossier loads for sales leadership, account executives and workspace admins, and the switch "Show private profitability analysis" turns it off again. Nobody else sees the switch or the numbers behind it: the database refuses the read rather than the page hiding it. Printing is a separate decision. Print / PDF leaves the internal section off the paper unless you tick "Include internal profitability in the print", the checkbox beside the button, and ticking it puts the section on the printout under an INTERNAL watermark. The tick only appears while the section is on screen, and it clears itself whenever you open a different dossier, so it never carries from one account to the next.
Because the cost recorded on that line cannot be right, so it is left out of your margin. Two shapes trip the check: a unit cost more than double the unit price, and a unit cost of 5,000 or more on a line priced at nothing. That 5,000 is the US dollar figure, and the threshold scales with your workspace currency, so a pound workspace flags at 4,000 and a yen workspace at 750,000. A zero-price line with a smaller cost is a service sold inside a per-user seat, and that cost is counted in full. Both are what a placeholder cost looks like, and a single placeholder at twice the threshold on one line can swing a whole account from green to red. A flagged line is excluded from the vendor cost total and from the margin, it is listed with its own numbers in the line table so you can see exactly what was read, the tile counts how many lines were held back, and the notes under the tiles say how much monthly cost that was. Fix it in Autotask, on the contract service itself, and the next contract sync clears the flag on its own. A small cost on a zero-price line is not flagged, because that is the shape of a service sold inside a bundle.
Stop pressing Retry — that message means your PSA will not accept the task the entry points at, and the same request gets the same answer every time. The Outbox recognises that answer, takes the Retry button off the row, and gives you two choices instead. Fix moves the time onto a replacement task: the picker only offers tasks that exist in your PSA, it starts with the tasks on the same project, and before anything is written Current asks your PSA whether the hours will be billed as a new entry or linked to time that is already there. Write off records that the hours can never be billed, and needs a sentence saying why. Retry all skips these rows and its count tells you how many are actually left to retry.
Nothing is deleted. The entry stays on the person's timesheet labelled Written off, carrying the name of the manager who wrote it off, the date, and their reason, with your PSA's original refusal still readable underneath. What changes is that the hours stop counting: project actuals, the Budget report, the hours tiles and the dashboard hours metrics all leave written-off time out, so no number in Current is inflated by hours nobody will ever bill. The entry is refused if anyone tries to submit it, including from Submit drafts on the timesheet. Admins and project managers can write time off and can reverse it; the Outbox keeps a line naming what was written off in the last thirty days, and both the write-off and any reversal are recorded in the audit log. Current will not let you write off an entry that already reached your PSA — that one is a real billing record, and the remedy for it is in your PSA.
Seat movement is measured from daily contract snapshots, and those snapshots have a first day in every workspace. When the period you pick starts before that first day, the tile measures from the first real snapshot instead and says so — "since Jul 8" — rather than comparing against a blank and showing your whole seat count as growth. With under a week of history it says "Not enough seat history yet" and holds the seat numbers back until there is something real to compare; if the history check itself fails it says that instead, because that is a different thing. The same rule drives the seat movement in the Book & activity report, in the Sales category of Reports, where contacts added still count for the full period because those dates come straight from your CRM.
Yes. On a company or contact record, the pencil on a note or a follow-up opens its title and its text so you can fix a typo, correct a name, or add what you learned later. You can edit your own notes; sales managers and admins can edit anyone's. A follow-up can only be edited by the person who owns it, because it syncs into that person's Microsoft To Do — and saving updates it there too. If a note has already been filed in Autotask, ConnectWise, or HaloPSA, saving sends the new wording to your PSA as well, so the two do not drift apart; the note tells you when that applies. If that write cannot go through — your PSA is unreachable, or CRM writes are switched off — your change is still saved in Current and it keeps retrying on its own. Every edited note carries a small Edited marker naming who changed it and when, so nothing is quietly rewritten behind your teammates' backs. Emails and system events are not editable: they are records of what happened rather than something a person wrote.
Because every task has to live inside a project, and your workspace does not have one yet. A brand-new workspace starts empty: nothing is created for you, and nothing arrives until you connect your PSA. While that is the case the board shows a Create your first project panel with a New project button on it, and the Add task button on each column is switched off with the reason on hover, rather than letting you type a task name that has nowhere to go. You can make a project from that button, from New project in the top bar, from the Portfolio page, or from the Getting Started card in the corner, and the board fills in with its columns and cards straight away. If you have connected ConnectWise, Autotask, or HaloPSA, the first sync brings your existing projects in and the board fills in on its own.
Anyone on the delivery team who can see the project, engineers included. Open the project's Risks tab and press Flag a risk at the foot of the lane that fits, or flag one straight from the work: the top row of the task drawer carries a Flag a risk button that fills the task name in for you and links the card back to that task. You can edit, close, and delete the risks you flagged. Project managers and tenant admins can do all of that to any risk on the project, and they are the only ones who can set a project's color by hand. Account executives and partner viewers are refused project risks at the database layer, reading and writing both, so the board is internal in fact and not only in the interface.
The Current Score band: 80 and up is on track, 55 to 79 is at risk, under 55 is off track. The score starts at 100 and subtracts for what Current can see — overdue tasks, unassigned work, unscheduled tasks, open PSA sync conflicts, budget burn from 90% up, a project past its own due date, open red risks at 10 each up to 30, risks nobody reviewed by their review date at 3 each up to 9, stalled tasks at 6 each up to 24, and work stopped, a flat 50 that fires when a critical task is stalled red, when a critical task is more than a week overdue, or when the project itself is more than a week past due and unfinished. Every deduction is itemized on the project page and at the top of the Risks tab, so the color always has a list behind it. When the arithmetic and the truth disagree, a project manager can set the color by hand with a reason: a worse-than-computed color holds until somebody clears it, and a better-than-computed one lapses after seven days or as soon as the score falls more than five points below where it stood when they pinned it.
No. The Risks tab is not in a partner's view strip, a partner who reaches the address gets a note pointing them back to their portal, and underneath both of those the database refuses a partner viewer every row of project risks, reading and writing. Nothing from the board reaches the partner portal either: the portal shows status, progress, dates, milestones, tasks, and shared documents, and risk cards, severities, owners, and review dates are not on that list. The one place a risk leaves Current is the note filed on an Autotask-synced project when a risk opens, turns red, or closes, and that note is internal — where Current cannot confirm an internal note type in your Autotask zone, it files nothing rather than let a note land somewhere a client could read it. Account executives are blocked by the same wall.
No, and that is deliberate. Tools that automate LinkedIn break LinkedIn's rules, and LinkedIn has been restricting the personal accounts that use them — your profile is not something worth gambling. Current does everything except press Send: a sequence's LinkedIn step lands in your Outreach queue with the note already written for that exact person, their profile one click away, and outcome buttons for afterward. A touch takes about ten seconds, and your tap — accepted, replied, declined — is what the sequence reacts to. Current also paces the queue so you are never handed more than 25 new invites in a day, comfortably inside LinkedIn's own safe limits.
You pick the approach on each email step, and the builder explains each one. Off sends your exact template. Opening line keeps your body word-for-word and writes one or two fresh opening sentences per person, from their role, company, and your history with them. Full adapt lightly rewrites the whole email per recipient while keeping your intent and your ask. Whatever the mode, the AI only uses facts already on the record — it never invents names, numbers, or links — and if it cannot produce a good draft, your plain template sends instead. The first five personalized sends in each sequence wait for your review in the Outreach queue; after five approvals the sequence goes hands-off.
Give the sequence a goal when you build it — book a meeting, start a conversation, or share information. When an enrolled contact books time through your booking page, Current spots the booking, counts the conversion, exits them from the sequence so they get no more automated touches, and sends you the bell. The sequence report shows meetings booked next to the LinkedIn numbers: invites sent, accept rate, and replies.
It gets reported to our team the moment it happens, without you doing anything. The error screen says so, and under it there is an optional box asking what you were doing — a single sentence there, like "I clicked Save on a new deal and the screen went blank", is worth more than all the technical detail put together, because it turns a report into something someone can reproduce. The report carries the page you were on, your browser and device, the version of Current you are running, and the last few things you clicked. It never carries anything you typed, your password, or the data that was on the page. If the same error hits several people it is grouped into one report with a count, so there is no need to send it twice.
Open your account menu at the top right and choose Report a problem. That is the one for a total that reads oddly, a button that does nothing, or a list that seems to be missing a row — none of those trigger an error screen, so nothing is reported automatically. Describe what you expected and what you are seeing instead, in plain language. The page you are on, your browser, and your recent steps travel with it, so nobody has to ask you to reproduce it. Reports are readable only by ITPartners+ super admins and are deleted automatically after 90 days.
Yes. Open the static list, click Add contacts, and choose the By filter tab — it opens the same audience builder campaigns, sequences, and dynamic lists use. Stack the filters, check the count, and click Add; everyone who matches right then joins the list at once. When you create a new list, pick Static and switch on Start from a filter to create it already filled. It is a one-time snapshot: the list does not remember the filter or update itself, but you can run a filter on it again later and only the newcomers are added. The builder's primary-only and active-only switches apply, an Account Executive fills from their own book only, and the list keeps one person per email address the way a send does, so the number added can come in a little under the preview when several contacts share an address; the confirmation shows the real number.
Yes, on Sales → Lists. Click New folder, name it, then drag a list into it by the handle at the left of the row, or use Move to folder in the list's ⋯ menu. Folders are shared with your whole team, so a list you file under "Trade shows" is under "Trade shows" for everyone; which folders you leave open or collapsed is yours alone and follows you between browsers. There is one level, so no folders inside folders, and anything you have not filed sits in Unfiled at the bottom of the screen. Deleting a folder never deletes a list — whatever was inside moves to Unfiled. Organizing is open to whoever can already manage the list: a sales manager, or the person who created it.
Because its name is how Current matches it back to the HubSpot tag it syncs from. Renaming it here would break that link without erroring: the next import would find no list under the tag's name, create a second one, and the list you renamed would quietly stop receiving anyone. So those rows show "Name managed by HubSpot" in place of Rename. Rename the list in HubSpot instead and the new name arrives on the next import. Every other list renames from the ⋯ menu on its row — the name turns into a text field in place, Enter saves and Escape leaves it alone.
Because three of the four tiles a customer gets — active MRR, renewal date, and support tickets — are worked out from a contract, and a prospect has no contract, so they used to sit empty. Open a company with no active recurring contract and you get four that are actually populated instead: Pipeline, which counts the open deals and what they add up to; Source & lists, which shows where the company came from and the marketing lists its contacts sit on; Owner, with a one-click claim when nobody owns it; and Engagement, which shows how long since anyone touched them and how many contacts are walking a live sequence. The switch is automatic — a company becomes a customer once it holds an active recurring contract, and Current already knows that, so there is nothing to set. If you would rather see a different four, the gear under the tiles lets you pick any of them, and prospects and customers are remembered separately.
Yes. The gear under the tiles opens four slots, and each one can hold any standard tile — both the customer set and the prospect set — or any custom field your workspace has added to companies. What you pick is yours alone: it changes nothing for anyone else, and it follows you between browsers. Prospects and customers are stored separately, so rearranging the prospect view leaves customers alone. Reset puts a view back to its default and keeps it there, which means a later improvement to the defaults reaches you rather than being frozen out. If a tile you chose stops being available — someone retires the custom field behind it, say — that one slot falls back to the default for that position and your other three choices stay put; restoring the field brings your choice back.
A sales manager can add fields that appear on every company in the workspace — money, a number, a percentage, a date, plain text, or a Choice dropdown you define — from the gear on the "Your fields" band of the key facts card at the top of any company page. Anyone who can edit the company can then fill them in, and each value saves on its own as you leave the box. A Choice field is worth reaching for whenever the answer should be one of a set: everyone picks the same wording instead of typing their own, which is what makes the field reportable. Type the options when you add the field, and use the list button on it to add or remove them later; removing an option leaves every company that already has it untouched, and the dropdown still offers that value back. Lost Reason arrives as a Choice already filled in with your workspace's lost reasons. What you record is usable across the CRM rather than only readable there: each field is a column you can turn on and sort by in Companies, a filter on both Companies and Contacts, and a condition in a campaign, sequence, or dynamic list. There is no delete, on purpose: retiring a field hides it everywhere while keeping every value already saved, so a field removed by mistake can be restored with its history intact. Retired fields sit at the bottom of the same menu with a Restore button. Retiring is workspace-wide; if a field simply is not part of your job, hover it and press the eye to hide it on your own company records instead — only you see that change, and a "hidden" count at the top of the section brings any of them back. Alongside these, every workspace also gets five built-in fields aimed at qualifying a prospect — their current IT provider, when that contract ends, their headcount, what they run, and the potential MRR if you win them. Your PSA has no equivalent for any of those, so nothing overwrites what you type.
The fields you work from — phone, website, LinkedIn, the address (country included), lead source, and the five MSP-fit fields — sit on the key facts card at the top of the company page, and you edit them in place with the pencil on each one. On Autotask, phone, website, and the address travel back — country included, matched against Autotask's own country list, and a value it does not recognize is left off and reported rather than guessed at. LinkedIn never syncs anywhere: no PSA has a field for it. On ConnectWise and HaloPSA these fields stay in Current, so no sync note appears. Everything else is in Sync & system, the closed row just under the card: what Current works out on its own, what came from your PSA, and the sync plumbing. Company type, classification, and market segment are marked there with a lock and the name of your PSA: it owns them and never accepts them back, so change those over there and they sync here. Between the card and the panel, that is every field Current holds — everything except a handful of internal identifiers, which are the row ids linking the record to your workspace, your PSA, and HubSpot, and the panel says how many it left out. An empty field shows a dash rather than disappearing, so you can tell nothing-recorded from nothing-to-see. Account executives can edit companies in their own book; opening someone else's account still shows you everything, but a save you are not allowed to make tells you so rather than appearing to work.
Every person sets up their own signature once at Settings → Email signature: full name, job title, and phone, plus switches for showing their email address and for a "Book time with me" button that links to their active booking page. Current can fill the fields in from their Microsoft 365 profile, and what they save is what sends. The layout is set by the workspace — the logo and button color come from the brand kit, so every teammate's signature matches, and there is no free-form HTML to paste. A separate switch leaves the logo off for anyone who prefers a plain sign-off. Campaign and sequence emails sent as a person end with that person's signature, above the unsubscribe footer on marketing sends. Each campaign, and each email step in a sequence, has an Include sender signature switch that starts on; a campaign sent as the brand rather than a person goes out unsigned, and so does anyone who hasn't saved a signature or has turned theirs off.
Yes. Company type is one of the audience filters in the campaign and sequence composers, sitting between company status and classification. It reads your PSA's own company type picklist — Customer, Prospect, Vendor, Partner, and anything else your instance defines — and the list of types fills itself in from your PSA, both the types your companies already carry and any type you added over there but have not moved a company onto yet. It stacks with every other filter, so Vendor plus Michigan plus an active contract narrows to exactly that. Note that company type asks a different question from the two filters around it: relationship is about whether a company holds an active contract, company status is about whether your PSA still counts the company as active, and a company typed Vendor can be both of those things.
Yes. The audience builder in the campaign composer has a Company fields row, and so does the sequence composer and a dynamic list's rules. Add a row, pick one of the fields your workspace added to companies, choose how to compare it, and type the value. A money, number, or percent field compares with is over, is under, equals, or is not; a text field with contains, is, or is not; a date field with is after, is before, or is on; and any field can ask for has a value or is empty. Every row must hold, the same as the rest of the builder, and you can stack up to eight. Beside it, an Open deal setting cuts the audience to companies with a deal still in play, or to the ones without — an open deal being any stage before won or lost, in any pipeline. So classification "M&A Prospect", not in an open deal, and annual revenue over 1,000,000 is three conditions and one send. The same three narrow the Companies directory, so you can read the list before you write to it. The Company fields row only appears once your workspace has defined at least one field.
Yes — on Companies, the Leads list, Contacts, the Deals list, and the contacts inside a CRM list. Open Columns at the right of the filter bar. Untick anything you never read, use the arrows to move a column left or right, and set the 0 to 3 control to keep that many columns in place while the rest scroll sideways. Every change lands as you make it, so you are choosing against the real table rather than guessing in a dialog. The name column and the row's action buttons are always shown, and Columns only lists what that page actually has — on Deals there's no Pipeline column inside a single pipeline, no Value column without permission to see deal amounts, and no Closed column until a won or lost deal is in view. The Deals board is a set of stage columns rather than a table, so the control sits out while you're on it; switch to List. Your arrangement is yours alone and follows you between browsers; to keep it as a named list you can come back to, or hand to a teammate, choose Save view. A view remembers your columns, your filters and your sort together, and Export CSV sends exactly the columns you can see.
Yes, every column. Click a header to sort by it and click again to flip the direction. The sorting runs in the database across every contact matching your filters, not just the ones your browser has loaded, so the order still holds after you press Show more. Name, Company, Title, Email, Phone, Primary, Active, Email health, Created, Last activity, City and State all sort, and contacts with nothing in the column you picked go to the bottom either direction, so sorting by Title doesn't open on a screen of blanks. Sorting by Phone uses whichever number the Phone column is showing, which is why the separate Mobile phone column doesn't sort on its own. Save a view and it keeps your sort along with your filters and columns.
More than each table starts with, and they all begin switched off so a table you never touched looks the way it always has. Open Columns and tick what you want. Companies has City, State, Industry, Market segment, Lead source, Created and Last activity. Deals has Probability, Forecast, Contract term, Lead source, Created and Days in funnel, which counts from the day the deal was created and keeps counting when it changes stage — that's the difference between it and In stage. Contacts has Mobile phone, Email health, Created, Last activity, City and State. Everything you turn on lands in Export CSV, and everything except Mobile phone sorts — the Phone sort already covers the number the Phone column shows. Last activity is always the company's most recent activity, ticket or synced email, worked out overnight, which is why the column on Contacts says "(company)" rather than reading as when you last spoke to that person.
Yes. Any custom field you added to a pipeline is a column on that pipeline's List tab. Open Columns and tick it — like the other extra columns it starts switched off. It sorts by the real value, so money and numbers order by size and dates by date, and deals with the field left blank sit at the bottom whichever way you sort. Export CSV carries the raw value rather than the formatted one, so a spreadsheet can do arithmetic on it. Custom fields only appear on their own pipeline: the All tab spans pipelines that each define their own fields, so a field from one would be blank down most of the list and Columns leaves it out there instead.
Click your view's pill above the filter bar (on Deals, open the View menu at the right end of the toolbar) and choose Share with people, then pick the teammates you want. They get the view in their own view bar and can apply it, but it stays yours to change or delete, and you do not need to lead sales to share your own view. Sales leadership also has Share with team, which publishes a view to everyone with CRM access. Either way a view saves the filters, not the rows: when a teammate opens it, it filters what they are allowed to see, so sharing a view never gives anyone access to a company they could not already open.
An AI-native CRM and project management platform built for MSPs — everything your PSA can't do. Sales pipeline, campaigns, quote-to-project handoff, dependency-aware scheduling, time entry, and billing sync — one workspace.
In the United States. Your workspace database, the files you upload, and the backups all live in US regions, and our subprocessors process data in the United States unless we say otherwise. You'll see this stated on the signup form and in the first step of setup, and it's written into the Terms of Service and the Privacy Policy. If your organization needs its data hosted in another region, use the contact form at current.day/help/contact and we'll tell you what we can support. Regional hosting isn't available by default and is arranged case by case.
No. Current is not a PSA and it does not replace the one you run. You keep ConnectWise, Autotask, or HaloPSA for tickets, contracts, and invoicing, and Current integrates with it. What Current adds is the part your PSA never had: a real CRM, a dependency-aware scheduling engine, and an AI layer, all syncing both ways so your PSA stays the system of record.
No. It runs on top of it, and you still need it. Two-way sync keeps your PSA the source of truth for time and billing, while Current adds the CRM, the scheduling engine, and the AI layer. Nothing gets ripped out and nothing gets migrated away from it.
It means we've shipped an update and the tab you're looking at is still running the previous version. Click Refresh and the page reloads on the newest version and brings you right back to the exact page you were on — nothing you were doing is lost. If you're staff, the What's New feed also opens once after the reload so you can see what changed. The banner shows at the top of the app and at the top of the client portal, and it can't be dismissed on purpose: running an old version against the updated service can cause confusing behavior, so refreshing is the intended way past it.
Synced emails and mirrored PSA tickets carry their full body for the last 100 days. After that, a nightly job clears the stored body while keeping the subject, the people involved, every date, and a short summary — forever. Nothing disappears from the activity feed, counts and reports are unaffected, and opening an old ticket still fetches its full detail live from your PSA, which always keeps the original. Notes, meetings, calls, and quote activity are never trimmed. This keeps your workspace fast as years of mail and tickets accumulate; a tenant admin can lengthen the email window up to two years from CRM settings.
Yes, with Seamless.ai connected. Bring your own Seamless API key (Integrations, Sales section) and the Lists page gains a prospecting builder: search by industry, size, revenue, technology, location, title and more, preview the full match count before anything meaningful is spent, and land the people you pick in a Current list or on the Leads board. Revealing verified emails and direct dials is the real spend — it always shows the exact credit cost and asks first, and a monthly cap plus an optional per-person allowance back that up at the moment of spend.
No, never. Enrichment is fill-blanks-only: it writes into empty fields, tells you exactly which ones it added, and leaves every populated field alone. That holds for the one-click Enrich action on companies, contacts, and leads, and for the automatic enrichment of new web leads — which also always saves the lead first, so an enrichment problem can never delay or lose a lead.
Connect again. That message came from an earlier version of Current's Microsoft sign-in, which sent people from other organizations to the wrong Microsoft directory (error AADSTS50020); it was fixed on September 11, 2026. Each person now signs in to their own organization. If Microsoft then says an admin has to approve Current, a Tenant Admin runs Approve for my organization once, as the next question describes.
A global admin of your Microsoft 365 organization, once for everyone. In Current, a Tenant Admin opens Integrations, chooses Manage on any Microsoft 365 tile, then Approve for my organization, and signs in at Microsoft with the global admin account. That can be a different person from the Current admin: they type their own sign-in on the same screen. Microsoft lists what Current asks for and records the approval for the whole organization. The list includes reading mail across the organization, and approving as a global admin from inside your workspace also turns on staff-mailbox capture, once Microsoft confirms your organization owns your email domain (the next question has the detail). After that, everyone else chooses Connect Microsoft 365 and isn't asked to approve anything.
A Tenant Admin approves Current for your Microsoft 365 organization from inside the workspace: Integrations, Manage on any Microsoft 365 tile, then Approve for my organization, signed in at Microsoft as a global admin. If your organization has already approved Current, choose Turn on staff-mailbox capture in the same place instead. Current then goes back to Microsoft once more, which may ask you to pick the account again, and checks two things: that the account is a global admin or Privileged Role Administrator, and that your Microsoft 365 organization owns the email domain of the Tenant Admin who started it. When both hold, every staff mailbox on the Staff mailboxes panel in Users & roles starts syncing, including people who never sign in to Current, and each one brings in its last 12 months of email. Only mail to or from a company in your CRM is stored; internal and personal mail is never saved. Any mailbox can be switched off there, which also removes what it already brought in. Three things stop it: an account that isn't a global admin, an organization that doesn't list your email domain as one of its verified domains, and an organization already linked to another Current workspace (contact ITPartners+ to move it). It can't be turned on from a support session either: it has to be the workspace's own Tenant Admin, signed in as themselves.
Yes, and it's off until an admin turns it on. Open Settings, then Workspace basics, and pick a team and channel under Celebrate in Teams. Current then posts a short note when someone takes the lead on a dashboard leaderboard, or when a week's top three is settled. There's a Post a test message button so you can check it lands in the right place before anyone else sees it. It reads the boards you already have, so there's nothing new to set up and no new numbers to trust. Nobody is @mentioned: a shoutout is about someone, not aimed at them. A message only goes out once the board has a day of history to compare against, so the first day after you turn it on is quiet. A tie at the top says nothing rather than picking one of two people, and a post that fails is retried for a couple of days and then dropped, because a celebration that turns up late is worse than one that never turns up. This is separate from sales win announcements, so leaderboards and won deals can go to different channels. Requires Microsoft 365 connected and the Tenant Admin role.
They're badges, and there are two. Best day yet appears when somebody's figure beats their own best on that board: it compares whole days against whole days, so it only shows on boards set to today, and matching an earlier best doesn't count. On a roll appears when someone holds first place for three recorded days running. Both are measured against the days Current has actually recorded for your workspace, not against all time, so a day Current couldn't read is a gap and the streak restarts rather than bridging it. That means a run can be understated but never overstated. Click any row to open that name's own panel: where they stand, how they've moved, the badges they hold, and a day-by-day trend of that board's figure. Open About this number on a board showing either mark and it explains in plain words how the mark is earned and what it doesn't mean. The style is a workspace choice: the first time an admin opens Dashboards, Current asks whether you want playful (confetti and a marker on the top spot) or professional (a quiet highlight). Both show exactly the same numbers, nothing is picked for you, and boards stay quiet until somebody chooses. Change it any time in Settings under Workspace basics. A badge never changes a number.
It's the full-width banner at the top of a company record for the one thing everyone must know before touching the account. Anyone who can view the company can add, edit, or clear it. On Autotask companies it syncs two ways with the Autotask Company Detail Alert, so service desk and sales always read the same warning, whichever side wrote it. Companies on ConnectWise or HaloPSA get the same banner inside Current only, and the banner labels itself accordingly.
On the company record, open the "Files" chip in the activity panel. Current lists the documents attached to that company and its opportunities in your PSA — Autotask, ConnectWise, or HaloPSA — and you can sort them by newest, oldest, name, size, or file type. Click any file to preview it in place: PDFs and images open in an expandable viewer with buttons to open full-size or download; other file types offer a download. PDF previews are drawn by Current rather than your browser's plugin, so they render on every browser including Safari — you can't select text inside the inline preview, but "Open full size" opens your browser's own viewer where you can. Nothing is copied into Current — each file is pulled from your PSA the moment you open it — and only people who can already see the company can see its files, so Partner Viewers never can. (HaloPSA file preview is still being verified against a live system; until then a HaloPSA file that can't open points you back to HaloPSA.)
Because Current now draws the preview itself instead of handing the PDF to your browser's built-in plugin, and a drawn page has no selectable text layer. That change fixed a real problem: on Safari, and on machines where Chrome is set to download PDFs rather than open them, or where a PDF extension had taken over, an inline preview came up as a blank white box while "Open full size" worked fine. Nothing in our code could detect that, so the durable fix was to stop asking the browser and render the pages ourselves — which works everywhere. If you need to select, search, or copy text, click "Open full size" and the PDF opens in your browser's own viewer, where all of that still works. This applies everywhere Current previews a PDF inline: a company's Files area, the Win Quote wizard, the quote drawer, and commission evidence.
Yes. An internal note an AE typed on a ScalePad Quoter quote — a ship-to address, a special instruction — syncs into Current and appears in the Win Quote wizard as a bold amber “Internal note from Quoter” banner at the top of the first screen. It combines the quote-level note and each line item's note (each line prefixed with its item name), and you have to tick “I've read this” before the wizard lets you continue, so a fulfilment-critical note can't be missed. If the quote has no internal note, there's no banner and no extra step. A Kaseya Quote Manager quote gets the same banner, carrying its private note plus the delivery block the order ships to. ConnectWise CPQ and HaloPSA-native quotes don't carry a note at all. (Field availability from each quoting tool's API is best-effort: notes appear when the tool provides them, and nothing is ever invented.)
When you convert a won quote through the Win Quote wizard — into a project or a post-sale ticket — Current files the signed quote PDF onto the company in your PSA. It copies the PDF from the won opportunity to the company's own attachments and renames it to the company name, the quote/offering name, and the date you converted (for example "Acme Corp Managed Services 8-1-27.pdf"), so it appears in the company record's Files area right away — the signed paperwork lives with the account instead of buried on the opportunity. It's best-effort: if the PDF can't be filed (it's a link rather than an uploaded file, or the PSA rejects the upload), the conversion still completes and the wizard shows a non-blocking heads-up so you can file it by hand. This is live for Autotask and ConnectWise; HaloPSA filing follows once its attachment API is verified against a live system.
Autotask won't let a task run past its phase's due date, or a phase past its project's end date. When you push a task date beyond its phase on the Overview, Current now asks first — an "Extend the phase to fit this date?" confirmation — and, if you approve, moves the phase's end date (and the project's, if needed) out in Autotask so the task fits, instead of leaving you to fix it in Autotask by hand. You can also set a phase's due date directly in its header on the Overview. (This clamp is an Autotask rule; on ConnectWise, every date push is verified by read-back the same way, and a date the PSA didn't store is reported rather than silently assumed.)
Inquire at the All level on Companies (Company Maintenance, Contacts, Documents), Sales (Opportunity), Project (Project Headers, Project Tickets), Service Desk (Service Tickets), Time & Expense (Time Entry), Finance (Agreements, Invoicing), Procurement (Product Catalog), Schedule, and System (Member Maintenance, Table Setup, My Account). Add and Edit at the All level on Project Tickets, Service Tickets, Opportunity, Time Entry, and Project Headers, plus Companies and Contacts if you turn on CRM write mode, and Documents and Product Catalog if you use the Win Quote wizard. Everything is All rather than My, because the API Member never owns the records it reads. The full module-by-module table, with what each permission is used for, is in "Prepare your ConnectWise before onboarding: the setup checklist". Member Maintenance matters most for the first step: the connection test reads the member list, so a role without it fails the test.
Because neither PSA gives Current a way to write a phase back, so a rename here would be undone by the next pull: you would type a name, watch it stick, and find the old one again an hour later. Rather than let that happen, the Add phase button and the rename pencil are left off ConnectWise and HaloPSA projects. Rename the phase in your PSA and Current picks it up on the next sync. Autotask projects get both — a phase you add is created in Autotask, and a rename is pushed and then read back to confirm Autotask stored it. Reordering phases and setting a phase due date work on every provider, because phase order belongs to Current and the due date has a write path everywhere.
Two moves can't reach Autotask, and the toast names which one you hit. Dropping a task into General — the bucket for tasks with no phase — moves it in Current while Autotask keeps showing its old phase, because an Autotask task always sits in a phase. Dropping it into a phase that isn't in Autotask yet leaves its Autotask phase alone too; that phase's header carries a "Not in Autotask" chip, and clicking it sends the phase across, after which moving the task again pushes properly. A third possibility is that two-way sync is switched off for your workspace, and the message says so. Either way the move stands in Current — nothing is rolled back.
Yes, on an Autotask-synced project with two-way sync on. Click the task name in its drawer, type, press Enter, then Save: the name is written in Current and pushed to Autotask on its own, so a name that didn't land is reported instead of hiding inside a batch that otherwise worked. Your rename then survives every sync until the name in Autotask actually changes, so a time entry or a note on the task leaves it alone. If somebody does rename the task in Autotask, their name wins unless your rename is provably later than the last activity Autotask recorded on that task, and the swap shows on the task's panel with a one-click Re-apply mine as well as on the Conflicts panel. On ConnectWise and HaloPSA the name is read-only in Current: rename it in your PSA and it arrives on the next sync.
That's fixed. Current had a blind spot where it could quietly record your PSA's new date in the background without actually applying it — and every later sync then read the date as "unchanged" and kept the old value, so a task moved to October in Autotask could keep showing March in Current indefinitely. Now, whenever your PSA's date disagrees with a date nobody edited inside Current, the PSA's date wins and is applied on the next sync (Autotask, ConnectWise, or HaloPSA). A date you did edit in Current is only reconsidered when your PSA's date genuinely changes, and then the PSA's date wins unless your edit is provably later than the last activity on that task. When the PSA's date wins, the swap is shown on the task, with one click to put your date back and send it across. If an old date is still showing, run Reconcile (or Resync from Autotask on that project) from the sync health page to apply it right away.
Because a sync never writes to your PSA on a judgement call. When Current keeps your edit, that decision is local: your value stays in Current, your PSA keeps its own, and nothing is pushed out on the back of an arbitration. That is deliberate, so an automated read can never overwrite a record in a live PSA. To close the gap, send the value across yourself from the task drawer. Save only pushes the fields you changed in that sitting, so when the field already shows the value you want, change it to something else, save, change it back, and save again. Both saves are real pushes, so your PSA briefly holds the throwaway value and anything watching that field there will see it — pick a harmless one. The second save then puts your value across, and reports your PSA's own reason if the write is refused, so it either lands or you hear why.
You don't have to anymore. A task deleted in your PSA that has no logged time is now archived automatically — it drops out of every board, list, timeline, calendar, and My Day, because your PSA is the source of truth. A task that does have logged time is held in Sync health's "Removed in your PSA" list for your review, so its billing history is never removed silently: there you can Archive it (hide it, keep the time entries), Delete it, or Keep it. Deletions are detected by Reconcile, which runs nightly and on demand from the sync health page.
Autotask schedules work on business days, so a due date that lands on a weekend or a company holiday is stored as the next working day: it accepts the push, then quietly keeps that working day. A date set on Labor Day Monday, for example, is stored as the Tuesday. Current recognizes the business-day move — it checks your workspace's holiday calendar, which syncs from Autotask itself — adopts Autotask's stored date so both systems agree, clears what used to be a permanent red date-push conflict, and names what happened — for example "stored Mon, Nov 2 instead of Sat, Oct 31." If the work must be done before the weekend or holiday, set the due date to the last working day before it.
You'd be told. A sync watchdog checks every few minutes that each PSA sync schedule (Autotask, ConnectWise, HaloPSA) is actually firing and that every synced record type is staying fresh. If a schedule dies or a record type stops updating, workspace admins get an in-app alert and an email, and a red or amber banner appears at the top of the Sync health page until the problem clears — a silent overnight stall can't go unnoticed anymore.
Both mean "more to come," not "broken" — the run synced what it could inside its time and request budget and resumes on the next cycle. A record type that's mid-sync and progressing under the sync watchdog's coverage shows a calm blue "Catching up" rather than amber, so an in-progress large book doesn't read as a problem. It turns amber when the watchdog flags it — no forward progress for about 2 hours, or falling behind its expected refresh window (as soon as an hour for core project data) — that's when it's genuinely worth a look. A few low-stakes record types (like holidays and time off) sit outside watchdog coverage and always show plain amber Partial while mid-sync. The note under the status says exactly why it paused (for example, which record failed to save, or that the PSA's request budget ran out) instead of a generic message. Every PSA request has a hard timeout so one stalled call can't eat a cycle, CRM records (opportunities, notes, charges, tickets) get a guaranteed slice of every cycle, and whatever has waited longest syncs first — so a catching-up row completes on its own within a few cycles. The all-systems summary chip at the top of the page counts how many record types are still catching up while everything stays green. Press Sync now to continue immediately; re-running never duplicates a record.
Search finds every task that has synced into Current — including completed ones (a done task on an active project is fully searchable by its number, name, or a fragment of either). So if a number like T20251117.0389 comes up empty, that task's row isn't in Current yet: most often its project was added to your PSA before Current started tracking it, or the task was removed here. The fix: open the task's project in Current and click the “Resync” button in the project header — it pulls every task on that project, completed included — then search again. (The Resync button shows for project managers and admins; if you don't see it, ask one to run it.) The search window now tells you this itself when a number-shaped search finds nothing.
AI briefings draft overnight, once per day — ready before your workday starts. Each company's own AI read is on a twice-weekly cycle instead, regenerating Monday and Wednesday mornings, because an account's story rarely moves enough in 24 hours to be worth re-reading. A company qualifies for that cycle if it holds an active recurring contract, if anything happened there in the last 30 days, or — new in July 2026 — if it has at least one open deal, which keeps a prospect covered for as long as the deal is live. A company with an open deal and no read yet doesn't wait for Monday: an hourly pass generates its first read within about the hour. There's also a manual refresh on every company page. The data underneath syncs on its own schedule: your PSA — ConnectWise, Autotask, or HaloPSA — polls every 5 minutes by default. See the sync-schedules article for the full table.
Because Current only files a message onto a company when the other party's address sits on that company's own email domain, and some companies have nothing that can identify one. The domain comes from the company's website first; where that's blank or unusable, from the domain its contacts share — and since July 2026 a single contact on a real business domain is enough, so a prospect whose only contact is jane@northwinddental.com now gets northwinddental.com. That's much wider than the old rule, which wanted the primary contact specifically or three contacts agreeing, and it's why quieter accounts and prospects have started filling in. What still produces nothing: a blank website plus contacts who are all on personal hosts (gmail, outlook, yahoo), all on role addresses (noreply@, alerts@, support@), or all on your own staff domain — none of those can be a company's identity. Two safeguards also hold: a domain appearing across several unrelated accounts is treated as a vendor or ISP host and identifies none of them, and a domain already claimed by one company is never handed to a second, so where two have a claim Current files the mail nowhere rather than guessing wrong. To fix an empty company, fill in its real website or add one contact at their work address; the next sync picks it up.
Yes. Every contact page has a Follow up button in the action row next to Email, Email history, Enroll in sequence and Verify email. It opens the same dialog the company record uses, with the person and their company both filled in, and it needs no email address on file — so it works for someone you only have a phone number for. Give it a title and a due date, and hand it to a teammate if it's their call to make. The to-do lands in the To-dos panel on My Day carrying that person's name, and clicking the name opens their contact page with their details, email history and sequences already in front of you; the reminder does the same when it fires, rather than dropping you on the company page to find them again. It rides through to your own Microsoft To Do like every other Current to-do, with nothing extra to switch on.
On the sign-in page, enter your email, continue to the password step, and click "Forgot password?". A one-time reset link is emailed to you (check spam); it opens a set-new-password page and signs you in. If you normally sign in with Microsoft, use your Microsoft account instead — there's no Current password to reset.
Register an app in Microsoft Entra ID, add Current's redirect URI, and paste the client ID, tenant ID, and secret into Settings → Authentication. Full walkthrough in the SSO article — including the common AADSTS errors.
It shouldn't any more. That column used to show the last time somebody actually typed a password or went through Microsoft, which never moves while a signed-in session keeps renewing itself — so a person who signs in through Microsoft and leaves the tab open could look like they had been away for weeks. It now shows the last time they really used Current, spelled out as Today or Yesterday for recent activity. If it still reads a stale date for someone, they have genuinely not opened Current since then.
Current tells you. Every workspace admin gets an email and a bell notification as soon as somebody signs in and lands in the approval queue, and a notice appears at the top of every page with a Review link to Users & roles → Pending sign-ins. Dismissing that notice with the X hides it until somebody new signs in, so you can clear it without missing the next person. Only admins of the workspace that owns that person's email domain are told — or, for an outside address, the workspace that invited them.
Deny blocks that sign-in from reaching the pending screen again but keeps the record, so it's reversible. Delete permanently removes the login altogether — meant for a genuine orphan, like a stray login left behind by an old, torn-down test tenant. Current won't let you delete anyone who already has a real profile in your workspace. Super admins also get a one-click "Clear all stale" that sweeps clearly-abandoned logins — older than 7 days and on a domain no live workspace has claimed; denied sign-ins are never touched.
365 days. The admin audit log holds a full year of history, and it's searchable (by actor email, entity type, or entity ID), filterable by action and date range, and paginated with Load more — click any entry for its full before-and-after detail. Entries are append-only: nobody, not even a Tenant Admin, can edit or delete them.
Yes — invite them to the free, read-only partner portal: status, timeline, progress, shared documents, and co-managed comments. Financials are firewalled at the database layer. Portal viewers are unlimited and never count toward your bill.
Open the project's Documents list, hover the document's row, and click the eye icon. A crossed-out eye means internal only; a solid green eye means it is shared. It saves straight away and the document appears under Shared documents in the portal for every partner who is a member of that project. Sharing is per document and starts off, so nothing reaches a partner until you turn it on, and clicking the eye again makes it internal again. Project managers and tenant admins have the switch. Current shares the title and the link, not the file, so the partner still needs their own access to open it.
No. Rates, costs, margins, budgets, time entries, and internal notes are blocked at three database layers — row-level security, restrictive deny policies, and financial-column-free views. Not hidden; absent.
Everyone on your team with CRM access — account executives, sales managers, and admins — sees the ConnectBooster Payments card on a company, including the amounts a customer is being charged, because knowing that is the point of the feature. Two hard limits sit under that: Current never stores or shows a full card number — only the last four digits and the expiry month, everywhere — and partner-portal viewers (your customers) can never reach the payments feed at all; it's blocked from them at the database layer, not just hidden in the interface.
Only if you turn on the Autotask bridge — it's off by default. HubSpot two-way sync keeps HubSpot and Current in step but doesn't write to your PSA on its own. A separate admin toggle on the HubSpot 2-way sync card, "Create HubSpot contacts & deals in Autotask," creates qualifying HubSpot contacts and open deals in your live Autotask (as contacts and Opportunities) and keeps edits flowing both ways. It only turns on once HubSpot sync is Dual-run and live, your CRM write mode is Live, and Autotask is connected — the toggle names anything still missing. A deal crosses only when it's open, its pipeline stage is mapped to an Autotask stage, its company is already in Autotask, and it isn't a Quoter deal; only the last 365 days of HubSpot activity is in scope, and inactive companies are skipped. A Backfill button previews how many existing open deals would be created before you commit. This bridge is Autotask-specific — ConnectWise and HaloPSA workspaces can't use it.
Most likely your workspace creates companies in the PSA only once they have a deal. That setting lives in Integrations, in your PSA's drawer under Sync behavior, and it is on for workspaces created from July 31, 2026 (older workspaces kept their previous behavior, with it off). While it is on, a company you save stays in Current with its contacts, notes, and to-dos, and is created in your PSA the moment its first deal is added, or right away if it is already a company there. Nothing is stuck and there is nothing to retry: the company won't appear on the sync health dashboard, and saving it tells you it will go across when a deal is added. A tenant admin can turn the setting off, after which any company saved in Current can be created in your PSA. If the setting is already off and the company still isn't there, check CRM write mode on the same screen, which is off by default and blocks every CRM write until an admin opts in.
Your PSA first: ConnectWise PSA, Autotask, or HaloPSA, each with deep two-way sync — one per workspace, chosen at signup. Then Microsoft 365 (Teams, SharePoint, Calendar, To Do), Microsoft Entra ID SSO, HubSpot, ScalePad Quoter, ConnectWise CPQ, Kaseya Quote Manager, and HaloPSA quotes (won-quote engines), ScalePad Lifecycle Manager, CrewHu, NeverBounce (bring your own account), Handwrytten (handwritten cards), and Resend (email delivery). A set of read-only reporting connectors feed your business reviews: Datto RMM, ConnectWise RMM, NinjaOne, Datto Backup (BCDR + SaaS Protection), Backup Radar (ScalePad's backup monitoring), Veeam Service Provider Console, Axcient x360Recover, Slide (its boxes, protected systems and the restores you ran), Huntress, SentinelOne, ThreatLocker, AutoElevate (which computers it controls, and what users asked to elevate), Datto EDR, RocketCyber, Auvik, UniFi, Cisco Meraki, Fortinet FortiCloud, KnowBe4 (security awareness), Duo (multi-factor coverage), Addigy, and Inky. And ConnectBooster / BNG Payments (a read-only daily sync) shows which of your customers are on autopay, whether it's actually charging, and when a stored card is about to expire.
No. AI is built into the platform — briefings, SBR drafting, sequence copy — all covered by the one per-user price. No tiers, no per-module SKUs, no AI surcharge.
Yes — every workspace ships with 24 built-in delivery playbooks grouped into folders: Infrastructure, Cloud & Migration, Security & Compliance, Onboarding & Managed Services, and Managed Intelligence (AI projects you can deliver to your customers, like a Microsoft 365 Copilot Deployment or a Custom AI Assistant / Chatbot). Each comes with real phases, tasks, durations, estimated hours, owner roles, dependencies, and checklists — clone one, set a start date, and the schedule builds itself. Edit, rename, or delete them like any playbook.
One per-user price, everything included — the CRM, the project engine, every integration, and all of the AI, with no tiers, no per-module SKUs, and no AI surcharge. List price is $95 per user monthly, or $85 per user on the annual plan (billed yearly). Round 1 — the first 100 MSPs to join — lock the founding rate of $50 per user monthly ($45 annual) for as long as their subscription stays active. Every workspace has a 3-seat minimum and a 14-day free trial. Partner portal viewers are always free and never count toward your bill. Billed in US dollars, euros, pounds sterling, or Canadian, Australian or New Zealand dollars, whichever you pick at the plan step, at a fixed price per currency. See the pricing article for the full breakdown.
A member of your team — technicians, PMs, sellers, admins. Clients viewing their own projects in the partner portal are free and unlimited.
Every new workspace starts with 14 free days. A card is required before you enter the app — it is the last step of setup, after your PSA connection and first sync, and entering it is what starts the trial — but nothing is charged until day 15, and we email you the exact amount three days before. Cancel during the trial (a one-line reason is all we ask) and you're never charged. A workspace set up without that self-serve card step gets a shorter 7-day setup window, room for up to 3 members, then goes read-only until a plan is chosen — with the banner saying exactly that ("choose a plan to continue"), never a payment-overdue message it never earned.
You buy an allocation — a pool of seats, minimum 3 — and every active team member draws one. Partner portal viewers are free, unlimited, and never counted; disabled users don't count either. Adding seats charges a prorated amount immediately and co-terms to your renewal; lowering the allocation takes effect at renewal, never mid-term.
Nothing dramatic, and nothing is deleted. The card is retried for about 7 days with an email at each step. Then the workspace goes read-only — everyone can still sign in and look, nothing can change. After 7 more days it pauses entirely except the Billing page. Fix the card or pay the open invoice on Stripe's secure page and access returns instantly.
No — annual terms are never refunded mid-term. Cancelling turns auto-renew off and you keep full access through the end of the year you paid for, so you always get everything you bought. If refund flexibility matters more than the annual discount, the monthly plan is the one to be on.
An afternoon, not a quarter. Connect your PSA (ConnectWise, Autotask, or HaloPSA) and Microsoft 365 and your companies, contacts, projects, and history are already there. Write-back stays off until you deliberately turn it on.
Every SBR claim carries evidence chips that resolve to a real record. During generation each reference is checked against its source; anything unresolvable is dropped before it reaches the page.
Your own other customers of a similar size — and only ever as anonymous medians. The magazine pack gives the comparison two pages: service (median first response, after-hours share, critical-priority share, positive-survey rate) and fleet & AI (the fleet measures plus Copilot adoption), each drawn as dot-plots of the partner against the cohort median. A real peer comparison renders only when at least five similar-sized customers exist; every row states how many peers reported that measure, and a measure too few peers have data for stays off the page. No peer is ever named, and only the aggregate medians ever leave the database. With a smaller book, the pages switch to a fallback — the partner against their own last quarter — optionally alongside clearly-labeled general industry framing that is never dressed up as a measurement from their record.
There weren't enough similar-sized peers for a real comparison — a peer cohort needs at least five of your other customers, because below that a median is neither anonymous nor meaningful. The magazine doesn't fake one, but it doesn't just vanish either: the comparison pages fall back to "you vs. your own last quarter" trend rows, optionally with clearly-labeled industry framing. A comparison page disappears entirely only when there's nothing to put on it at all — no cohort, no self-trend, and no framing.
Yes. A review built from September 5, 2026 carries a page called Where you're exposed, between the priced risks and the road ahead. It maps every offering in your catalog for that partner, filled when their live agreement lines match it and hollow when they don't, with the in-place and not-covered counts above the map. Up to three gaps are featured beside it, loudest ask first: each card names what the gap leaves open (the AI's own line when the review's analysis raised it, otherwise the description you wrote under Manage offerings, and always yours to rewrite), how many of their tickets and emails mentioned it in the last 90 days (counts only, never the messages), and your target price per unit when one is set, for example "From $6 per seat a month". No target price means no money on the card, and the Whitespace grid's estimate from what other partners pay never prints. The page is on for every partner with a gap; the builder's Coverage gaps step is where you switch it off, choose the featured gaps, leave an offering that does not apply off the map, or rewrite the wording. It presents in Live mode like every other chapter, drops on its own for a prospect or a fully covered partner, and can be removed from a built pack like any other page.
Yes — the Refresh data button on a built pack re-pulls the live numbers while keeping your picks, edited text, custom sections, and conversation choices (trend cuts recalculate). What clears edits is rebuilding through the wizard: saving the review again rewrites the text, so old overrides are removed rather than silently masking words nobody re-read.
No — by design. Any sentence is click-to-edit on a built pack (with a revert), but counts, percentages, money values, the scorecard, and the charts are computed from the record and can't be typed over, so a pack can never contradict its own data. If a figure looks wrong, fix the source data and hit Refresh data.
Yes — the poll interval is configurable per workspace under your PSA's connector settings (ConnectWise PSA, Autotask, or HaloPSA). Default is every 5 minutes. Pushes are immediate regardless.
The chain of dependent tasks with zero slack — if any task on it slips, the whole project's end date slips with it. Current computes it live from your dependency graph and highlights it on the Timeline and dependency map. See the critical-path article for how to read and shorten it.
Draw a link by dragging from a task's right dot to another task's left dot, and if it's refused the message names the rule you met. The link would loop, leaving a task waiting on itself. The two tasks are already linked, or already linked the other way round. The two projects don't share a sync type — a link can't cross between a PSA-synced project and a Current-native one, because Current would have to schedule against two sources of truth at once. Or the link isn't yours to add: a project manager can add any dependency, and you can add one on a task you're assigned to. Your type and lag stay in the dialog either way, so you can point the link somewhere else without starting over. To remove a link, open the task and use the trash button on the row under "Waits on" or "Waiting on this" — the map draws links rather than deleting them.
It works on every project you can manage. Press Bulk edit in the project header, tick the tasks you want, and the action bar offers status, priority, task type, department, reassign, shift dates, and set dates. On a PSA-synced project the confirmation counts what leaves Current before you commit — "6 of the 9 selected tasks are linked to Autotask, so applying changes them there too. There is no undo." Find/replace and Remove stay on templates, where a wrong click costs a draft instead of live work. A selection survives the task search box, and the dialog names how many of your ticked tasks a search is currently hiding.
Yes. Hover any day in month or week view and press the + in its corner; the day view has an Add button instead. Choose Project task and it's created on that day in the project you pick — with a project pinned in the scope bar, that one is already filled in and held. Choose To-do and it's due at the end of that day, yours alone, and it syncs to your Microsoft To Do list. Neither snaps off a weekend or a holiday, because you chose the day. A task added this way is created in Current and stays there, even on a project linked to your PSA. Partner viewers don't get the +.
Your own open to-dos with a due date show as blue chips on the day they're due, in your local time. A teammate's to-dos never appear on your calendar. Drag one to another day and it becomes due at the end of that day, with no working-day snap, since you picked the day. If you use Microsoft To Do, the new due date reaches your list there on the next sync. To-dos with no due date stay on My Day rather than the calendar, because there's no day to put them on.
Both can sync from Autotask or be entered manually; on ConnectWise workspaces both are entered manually in this release, and they drive everything identically. Holidays: one company-wide calendar, filled by Autotask sync plus any admin-added dates, drives all scheduling. Employee costs: pulled from the linked Autotask resource's internal cost (locked from editing), or entered by a Tenant Admin — and used only for the admin-only Profitability lens.
System mail (sign-in codes, invites, digests, alerts, and booking confirmations) is transactional and sends through Current's own authenticated domain so it lands instantly. That is the only mail Current's built-in sending carries. Outreach sends from an identity you own: sales sequences always go from your own Microsoft 365 mailboxes, and a live campaign goes from your workspace's own Resend key and verified domain (set up in Integrations → Email) or, with no key saved, from the connected Microsoft 365 mailbox of whoever the campaign is from. That keeps your domain's reputation and your replies in your own hands. A workspace with neither a Resend key nor a connected mailbox for the sender can't send live campaigns, and Current refuses the send rather than using a shared address. The "Who it's from" choices decide whose name, and when it's on your domain whose real address, each email carries.
Yes — sales leadership and tenant admins can, in the composer's "Who it's from" section (this is a leadership capability, enforced at the database, so account executives keep their two options: your brand, or "you from your brand"). "Each account manager" sends every recipient's email from that company's own account manager — from their real address when it's on your verified sending domain, otherwise replies still route back to them, and any company without an account manager falls back to your brand. "Someone else" signs the whole campaign as one chosen person — pick a teammate or type a name and reply-to. The Review step shows exactly who each recipient will hear from before you send. Three sign-off tags — {{sender_name}}, {{sender_first_name}}, {{sender_email}} — fill in per recipient to match whoever the email is from.
Up to 1,000 people can be active in one sequence at a time. The enroll panel shows the room left before you click, and an enrollment that would go past the limit is refused as a whole with the numbers, never trimmed to fit. Anyone who replies, unsubscribes, bounces, finishes or is removed frees their spot, so an evergreen sequence keeps taking new people. Sending is capped too: each Microsoft 365 mailbox sends up to 250 sequence emails a day (a hard limit that protects your sender reputation), so a big enrollment paces out over several business days, about 250 at a time, with the rest waiting safely in the queue. Above 1,000 people a Campaign is the right tool — it reaches everyone at once from your workspace's sending identity, with unsubscribe handling built in, and its audience has no size limit. For a very large list, verify (Enrich) it first to strip bad addresses, because sequence email comes from your own Microsoft 365 mailbox and a list full of bounces or spam complaints hurts your domain's reputation. Sequences that were already above 1,000 when the limit arrived keep everyone and keep sending, and simply cannot add more until they drop under. And enrolling someone into a sequence that has no email steps yet never marks them 'completed' — they show as 'Waiting for steps' until you add one.
Open the menu on its row — on Sales → Campaigns or Sales → Sequences — and choose Duplicate. You get a fresh copy called "Copy of «name»" and the original is left exactly as it was. A campaign copy carries the audience, sender, subject, and body but no recipients, no send history, no results, and no approval stamp: it is born a plain draft and walks the whole approval flow again from scratch, so copying is a shortcut through the writing, never through the review. A sequence copy carries every step in order and is created paused, so nothing sends until you switch it on. Enrollments, send logs, and auto-enroll triggers are never copied — a copy that inherited a trigger would quietly start enrolling everyone the original was set up to catch.
Open the menu on its row and choose "Save as template." Current files a copy under the Templates tab on that page, and the campaign or sequence you saved from is untouched and keeps doing whatever it was doing. To use one, click "Use template" on the template row, or pick "Start from a template" when you click New campaign or New sequence — that option appears once your workspace has saved at least one. A sequence template is always paused, holds no enrollments, and carries no triggers, so it can never send anything itself; use it to create a sequence, then set up enrollment on the sequence you created. Deleting a template only removes the saved starting point — anything already built from it keeps running.
Use the Company status filter in the audience builder — set it to Active. It reads your PSA's own active/inactive flag (Autotask, ConnectWise, or HaloPSA), so a service notice reaches only companies that are still active partners and skips ones you've offboarded — even a former company that still carries a lingering contract, which the Customers filter alone wouldn't catch. Combine Active with the Customers filter to reach current partners who also hold an active contract. One caveat: a company's status comes from your PSA on the next sync, so a company you marked inactive in your PSA becomes excludable once that sync runs; until then it still counts as active, so no one is dropped by surprise.
About 3–5 minutes per 1,000 addresses that actually need checking — and the campaign wizard states a computed estimate for your exact list size before you start. Small batches (ten addresses or fewer) finish in seconds. Addresses verified within the last six months are skipped automatically, so re-verifying a recently-checked list is usually much faster and costs nothing. When it's done, the wizard's pre-send report shows every address with its verdict — valid, accepts-all, unknown, or flagged — with suggested corrections, and flagged addresses are excluded from every send automatically.
No — by design. On the Do not email list (Sales → Lists, pinned at the top) sales leadership and admins can remove an address someone added by hand or uploaded, but an address that landed there from a real unsubscribe click, a bounce, a spam complaint, or a verified-invalid check is locked and can't be removed by anyone. If someone opted out, they have to opt back in themselves.
The Relationship health tile on Sales Home ranks your partners on one churn score, computed live from your own data: survey results, the AI's read of the account, quiet-account detection, how long since anyone made contact, contracts coming due, weak renewal deals, and stalled deals — weighted by how big the account is. The AI explains a row; it never picks one. An account Current hasn't read yet is shown as unknown, never as healthy. The tile shows the four riskiest accounts on Your Day and the five riskiest on the Team Cockpit, where sales managers see the same ranking across every rep.
Current writes the to-do for you, syncs it to your Microsoft To Do, and logs an internal note on the company's timeline that partners can't see. The account then steps aside for 21 days so the next-riskiest one can surface. You get five seconds to undo before anything is created.
Yes — group reps into a sales team in Users & roles → Teams (a manager plus their reps). That manager's sales dashboard, reports, and deal views then open focused on their team by default, with "Everyone" one click away. It's a view default, not a permission change: leadership access is unchanged, and a manager without a team keeps seeing the whole CRM. A person can be on one sales team and one project team, but not two of the same kind — so it's always clear whose team a rep is on.
Because it has no close date, and every report that counts by month counts by close date. It happens when the system that marked it won sent no date with it, usually an import or a PSA sync, and Current would rather leave the date empty than invent one. Those deals are the second group on Deal review, at /sales/deal-review: "These closed, but we do not know when." That page is not listed in the Sales menu, so open it directly. Each row shows the best date on record and says where it came from. If HubSpot recorded a real close date you can accept it in one click; if the only date on record is the moment a sync touched the deal, the field starts empty and you type the day it really closed. Setting a date there changes only the date. The outcome and the stage stay exactly as they are, and until it has one the deal counts toward nothing: not won revenue, not goals, not commission. Sales leadership only, because the date you pick decides which month the money lands in.
Yes. Open Deals, choose Edit columns, then New pipeline, and add one for any kind of work your team tracks separately, with its own columns and its own board tab. Sales Managers and Admins with CRM access can do this. When you create it you tell Current what its deals count as — New Logo, Expansion, Renewal or Project — and that is how goals, commissions and forecasts read them, so pick the one that matches the money. You can reorder your pipelines and archive one you have finished with; an archived pipeline leaves the board tabs but keeps its deals and their history, and you can restore it any time. The four built-in pipelines can be renamed and reordered like any other, but they cannot be archived, because quote minting, renewal tracking and expansion revenue look for them by name.
Yes, by adding custom fields to the pipeline those deals live in. Open Deals, choose Edit columns, and use the Custom fields box inside the pipeline you want. Name the field whatever your team calls it, pick what kind of value it holds — money, number, percent, text or date — and it appears on every deal in that pipeline, in the order you set. It appears nowhere else, so an acquisitions pipeline can track EBITDA and an asking price without any of that turning up on your New Logo board. Sales Managers and Admins with CRM access set the fields up; anyone who can already edit a deal can fill them in. Renaming a field or moving it keeps everything already entered. There is no delete, on purpose: retiring a field takes it off the deal but keeps every value your team saved, so restoring it later brings them all back.
Not in the security sense, and it is worth being clear about that before you rely on it. Listing people keeps a pipeline off everyone else's deals board, which is what you want when a pipeline would only be clutter for most of the team. It does not lock the deals away: anyone on your team with CRM access can still reach them through search and reports. If a deal genuinely must not be seen by certain people, this setting is not the tool for it. One other thing to know: sales leaders are not added to the list automatically, so if you want a pipeline on your own board, add yourself.
Because Current can only prove when it closed for some deals, and it will not guess on the rest. If a deal was won months ago and only reaches the Won stage today, closing it with today's date would put commission in this month for a win that belongs in another one, and nobody would have asked for that. So Current closes the ones it can stand behind (a deal your team created and closed this month, a loss, or a deal that already carries a real close date) and sends the rest to Deal review for a person. Two things follow from that. Your open pipeline and forecast can read slightly higher than you expect, because those deals stay open until somebody works the list. And the list is short work: Deal review can accept every trustworthy date in one action, and only leaves you the ones where the date on record is an import stamp rather than a real close.
No. A one-time close-out was planned for 27 July 2026 and it never ran. The queue emptied because the everyday sync closed those deals as it caught up with them, and Current records each of those closes as coming from the sync. Commission only starts tracking when a deal is closed in Current, so a close a sync makes pays nobody, while a rep closing a deal in Current, or sales leadership closing one on Deal review, pays exactly as it always did.
No. Commission only starts tracking when a deal is won in Current, and a deal that arrives already closed was won somewhere else. That covers the HubSpot import, the HubSpot two-way sync, and the Autotask, ConnectWise and Halo opportunity syncs: when one of them closes a deal, Current records that the close came from the sync, and no commission line can ever be created for it. The deal still counts in your pipeline and your won-revenue reports, so nothing goes missing from your numbers. Won quotes are the deliberate exception and always pay in full — a ScalePad or ConnectWise CPQ quote your rep built, sent and won is a win made in Current. And if your team closed a deal in Current first, a later sync leaves it alone: the rep keeps that commission no matter how many times the deal syncs afterwards.
It is still there, at /sales/deal-review, and nothing about the page changed. The row left the Sales menu on 27 July 2026 because the queue it was built for is empty on a normal day, and a permanent menu entry for an empty list is clutter. Deals still land on that page whenever a sync marks one won without saying when, so open it directly if a report tells you a win is missing a close date. Sales leadership only, because the date you pick there decides which month the money lands in.
Only sales leadership — a tenant admin, anyone with the Sales Manager role, or anyone with the sales-manager toggle. The rep never sees them, and that's enforced at the database layer, not just hidden in the interface. A rep sees only their own sessions' shared content: the shared notes, the outcomes, and the promises. See the Sales Coaching article for how sessions and promises work, and where open promises show up between meetings.
Yes. A promise made in a 1-on-1 lands on its owner's My Day and Microsoft To Do the moment it's saved — owner-scoped, so a rep's promises go to the rep's lists and a leader's to the leader's. The next steps you type in the coaching pipeline review sync the same way. Open promises also roll forward into the next session automatically, and kept-or-missed outcomes feed the follow-through trend on the coaching roster.
No. Your assigned project tasks appear in a "Current Projects" list in Microsoft To Do as a personal, one-way view: marking a task done in Current (or your PSA) checks it off there automatically, but checking one off in To Do never completes the real task and never flows a completion to Autotask, ConnectWise, or HaloPSA. If you check off a task that's still open in Current, it comes back titled "(Still open in Current — see notes)" with instructions to finish it — mark it done in Current, or extend its due date there. Deleting a To Do item just stops it mirroring for you. (Your personal CRM to-dos in the separate "Current" list still sync both ways.)
Because it's a snapshot, on purpose. When a coaching session is finalized, its goal panel freezes as "Goals as of" the session's date — the targets and actuals exactly as they stood the day you met, not as they've moved since. That keeps the record accurate: what you discussed reflects what was true then. Only the live draft session reads today's numbers.
Each offering owns a short list of match phrases, and a customer is marked covered when any of their live PSA service lines — Autotask services, ConnectWise agreement additions, or HaloPSA contract lines — matches any phrase: contains (anywhere in the name), prefix (starts with), or exact, all case-insensitive. The phrases match the service name as your PSA writes it, which is usually namespaced ("Backup - Datto BCDR - S5-6…"), so one short phrase like "datto bcdr" groups a whole product family. Coverage is only ever computed for customers, so a prospect never shows as covered.
Sales leadership can, from the Manage offerings panel on the whitespace page. Every workspace starts with a default catalog of 29 common MSP offerings, each pre-loaded with generic starter keywords, so the grid is useful on day one — your job is to refine them to match how your PSA names things. A short note at the top of the panel spells out exactly what your keywords match against for your PSA (the Autotask Service name, the ConnectWise addition's product/description, or the HaloPSA line description). As you type a phrase it shows how many of your real PSA service names it would match, so you can tell at a glance whether it's too broad or matches nothing. Add or remove a phrase and that column is rebuilt against your data within a few seconds — the grid updates itself, with the overnight sync as a backstop. A phrase can belong to more than one offering on purpose, so a bundle or a two-in-one product ticks every box it covers.
It counts the support tickets and synced emails from the last 90 days that were actually about that offering — even though the customer doesn't buy it. Twice a week (the Monday and Wednesday insights run) Current's AI reads each customer's recent tickets and emails and works out which offering each one is about, by meaning rather than keywords, so "can't get my 2FA code", "set up MFA for new hires" and "authenticator app broken" all count toward the same multi-factor offering. It reads up to the first 2,500 characters of each part of an item — a ticket's title and description, an email's subject and body — for enough context to judge it accurately. It reflects what the customer said, not what you said back: only inbound emails count, with the quoted reply thread and signatures stripped first, so a topic your engineer raised in a reply is never counted as the customer's. Hover the circle for the breakdown — "2 tickets and 6 emails mentioned this in the last 90 days" — and click it to open the drawer, where each ticket and email expands ("Show more") to the full message the AI read, then start an expansion deal. Only offerings a customer doesn't already buy light up, and only the last 90 days count. Brand-new signals appear after the next twice-weekly pass rather than instantly.
From your own book, not industry averages. Each offering is priced at the average monthly per-unit price across every matching active service line in your PSA — Autotask services, ConnectWise agreement additions, and HaloPSA contract lines all feed the same math — or at a target price sales leadership sets in Manage offerings, which also lets you value an offering you haven't sold yet. That price is multiplied by the company's own size on the offering's sizing basis: their Microsoft 365 seats, their RMM device count, their contact count, or once per company. The Revenue opportunity band above the grid totals the estimates for whatever your filters are showing (one exception: the "My team" lens cuts the grid rows in your browser, so the band shows the wider total and says so) and calls out the warm subset the partner already asks about. A gap with nothing to go on shows no figure rather than a fake zero. Value estimates are visible to sales roles only, like MRR everywhere else.
From the partner's own numbers, on the AI opportunity page — its own page near the end of the pack. The per-year figure is grounded in the seat count the review states (and the page says whether that count is measured or assumed), the hours each selected play returns, and measured Copilot adoption where enough similar partners report it — otherwise a clearly labeled industry estimate. You choose the plays on the wizard's AI plays step, the headline and lead figure follow your selection, and the factors print beside the figures so the arithmetic is checkable. With no plays selected, the page drops from the review rather than printing a generic pitch.
Whatever your own catalog says. The required Email seats offering (Sales → Whitespace → Manage offerings) holds License pools rules — includes and excludes — that decide which of your ScalePad SaaS license pools count, and that definition drives the pack's seat figure, the AI per-person math, and the peer-comparison size bands. Out of the box the rules cover Microsoft's mailbox-bearing base licenses (E3/E5, Business plans, Exchange Online), and add-ons are excluded so nobody double-counts: a person on E3 plus Teams Phone is one seat. An MSP on Google Workspace just edits the rules — no product update needed — and the seat label in the pack is the offering's own name.
Because it defines what a managed email seat means everywhere Current states one — the SBR's seat figure, the AI at-scale math, and the peer-comparison size bands. Deleting it would leave those numbers with no definition, so it wears a lock badge (Required · defines email seats) and deletion is refused at the database layer, not just in the UI. Everything else is yours: rename it (the seat label follows), deactivate its whitespace column, or rewrite its rules entirely.
No. The Datto RMM connector is read-only: every request goes through a guard that only allows specific GET reads (sites, devices, open alerts). Resolving alerts, moving devices, running jobs, and resetting API keys are unreachable — Current reads Datto RMM and never writes to it.
Almost always because API access isn't switched on yet, or the platform is wrong. In Datto RMM go to Setup ▸ Global Settings ▸ Access Control and Enable API Access, then generate the Access + Secret key under Setup ▸ Users, and make sure the platform you pick in Current (pinotage, merlot, concord, vidal, zinfandel, or syrah) matches the region you log into.
Each Datto site (identified by its siteUid) is auto-matched to a Current company by normalized name and linked only when exactly one company matches. Unmatched sites appear on the card's mapping panel to link by hand; a manual mapping is never overwritten. Unmapped sites still sync — the data just doesn't surface on a company until it's mapped.
No. The Datto Backup connector is read-only: it calls only GET (read) endpoints — the device list, each appliance's protected-systems list, the Direct-to-Cloud endpoint list, and the SaaS Protection customer roster with per-customer seats — and every request is checked against that allowlist in code before it's sent. Current never writes back to Datto, and the key-management actions (regenerate, deactivate, delete) live in the Partner Portal, not in Current.
In the Datto Partner Portal, go to Admin ▸ Integrations ▸ API Keys ▸ Create API Key. Datto issues a Public API Key and a Secret API Key — the Secret is shown once, behind Reveal, so copy it before leaving the page. It takes a Partner Portal administrator. Paste both into the Datto Backup card on Current's Integrations page. One pair reads appliances, SaaS Protection, and Direct-to-Cloud.
Datto identifies customers by company name, not a stable id, so an appliance surfaces on a company only once that name is mapped. Open the Datto Backup card, work the Unmatched list, and pick the Current company for it. Unmapped appliances still sync — they just don't appear on a company until linked — and a manual mapping is never overwritten by the auto-matcher.
Some Datto Partner-Portal API keys are product-scoped, so a key created for another integration may read appliances but not SaaS Protection or Direct-to-Cloud. When Current detects that, the Datto Backup card shows a note naming the fix: create a NEW API key from Admin ▸ Integrations ▸ API Keys, paste the new Public/Secret pair into the card, and press Test. Reconnecting is non-destructive — every appliance, agent, seat, and mapping already synced is kept.
In ScalePad Hub: sign in as an administrator, open your own profile, then API Keys ▸ Create. Only an administrator can make one, the key is personal (it carries the permissions of whoever made it), and ScalePad shows it once with a two-year expiry by default — so copy it before you leave the page and note the expiry somewhere you will see it. Paste it into Integrations → Backup Radar in Current and press Test connection: Current sends it as the x-api-key header, makes one live read against Backup Radar, and stores it server-side only. One key spans every ScalePad product the account is licensed for. If the account has no Backup Radar subscription, the key is still valid and reads nothing — Current says exactly that rather than reporting a bad key, so there is no point creating a second one.
Because the two products count different things. Datto Backup counts protected systems — one row per machine an appliance backs up. Backup Radar counts backup jobs, and one server can carry several: a nightly full, a verification run, a replication. Neither figure is a total of the other, which is why they sit on separate cards on a company record instead of being added together there. On the Backups failing now dashboard tile, where both products are connected, the two are added and the tile says so on its face.
No. Backup Radar reports boot verification as a pass or a fail, never a picture: a job classified Primary Boot Verification carries a result status, and that is the whole of it — there is no screenshot, thumbnail, or attachment anywhere in the ScalePad API. Screenshots come from Datto BCDR, which mirrors the image itself into Current, where it appears as a thumbnail on the Backup & continuity card on a company record and in the proof strip of a Strategic Business Review's backup chapter. A workspace running only Backup Radar gets the verdict without the exhibit.
One of two things: the job's latest run came back an error, or its service level reads Out Of Compliance — which includes Out Of Compliance - No Results, the state a job that has never reported sits in. Current takes that verdict as given rather than applying a threshold of its own, because Backup Radar has already judged the job against the SLA policy your team set for it. Those jobs are what the company's backups-failing alert and the Backups failing now tile count, alongside anything Datto Backup reports failing, so a company raises one alert whichever tool saw the problem. A job Backup Radar has not judged yet shows no SLA state and counts as neither failing nor in SLA.
No — never. The Datto SaaS Protection connector is read-only. The one write in the whole Datto Partner API is a bulk seat change (pause/unlicense seats), and it is walled off in Current's code: the request layer only allows the three read endpoints and throws on anything else, so the seat-change endpoint is unreachable. Connecting Datto to Current cannot change, pause, or remove a single seat.
In the Datto Partner Portal: Admin → Integrations → API Keys → Create API Key, as a Partner Portal administrator. You get a Public key and a Secret key; paste both into Integrations → Datto SaaS Protection → Manage in Current. It's the same key family as Datto BCDR, so one pair can power both connectors.
Seat and backup data only appears on a mapped company. Datto identifies each customer by a SaaS customer id; Current auto-matches by name where it's unambiguous, but the rest need mapping by hand on the Datto SaaS Protection card's Unmatched list. Once the customer is mapped, its coverage shows on the company record within a sync cycle.
No. Datto EDR's LoopBack API exposes full create/update/delete and response actions (isolate, scan) on most models, but the Datto EDR connector is read-only: every request goes through a guard that only allows a strict list of GET reads (endpoints, sites/organizations, alerts). Isolating a host, running a scan, or closing an alert is unreachable — the API allows those changes, Current's code physically cannot issue them.
Datto EDR API tokens expire exactly one year after they are created, with no auto-refresh, so the most common cause is simply that the token lapsed (a 401). Create a new token in Datto EDR under Admin ▸ Users & Tokens ▸ API Tokens, paste it into the card, and re-test the connection. Set a calendar reminder ~11 months out so the next one is replaced before it expires.
Your Datto EDR instance is a per-partner subdomain like https://yourcompany.infocyte.com — find it in the address bar when you're logged in. Current needs it with /api on the end (https://yourcompany.infocyte.com/api); the trailing /api is mandatory, and leaving it off makes authentication and company loading fail.
No. RocketCyber's Customer API is entirely read-only — it has no write endpoints at all — and on top of that every request Current makes goes through a guard that only allows four specific GET reads (accounts, agents, enabled apps, and incident counts). Current reads RocketCyber and never writes to it.
Per-customer value signals for your executive and CIO business reviews: the count of managed endpoints and enabled security apps, how many incidents are open right now by severity, and 90-day incident activity (raised, resolved, and the most recent incident). It stores rolled-up counts per customer, not a raw log of every incident.
Each RocketCyber account (identified by its accountId) is auto-matched to a Current company by normalized name and linked only when exactly one company matches. Unmatched accounts appear on the card's mapping panel to link by hand; a manual mapping is never overwritten. Unmapped accounts still sync — the data just doesn't surface on a company until it's mapped.
Yes — strictly. Current only reads from Auvik (device inventory, network summaries, and open-alert counts) and never writes back. Auvik's one write endpoint, dismissing an alert, isn't wired into Current and can't be reached; the connector's allowlist contains only three read paths.
Three things from your Auvik dashboard: your region/cluster code (us1, us2, eu1… — read it from the dashboard URL), an API username (an Auvik user's login — ideally a dedicated service account), and an API key generated for that user. Paste them into the Auvik card under Integrations and press Test connection. Best practice is a service-account user so the key survives staff turnover.
The customer's Auvik tenant probably isn't mapped to that Current company yet. Current auto-links Auvik tenants to companies by exact normalized name, and leaves the rest for you to map on the Auvik card. Unmapped tenants still sync in the background — their devices and summary are stored — but only appear on a company record once you link them.
No. The Addigy connector is read-only. It mirrors device inventory, macOS version, FileVault/encryption and compliance status for reporting only. MDM commands (lock, wipe, restart, key rotation), the managed-admin password-reveal endpoint, and all create/update/delete calls are blocked in code — they aren't on the connector's allowlist, so Current cannot call them at all.
No. Addigy locks an account for 24 hours if you exceed roughly 1,000 requests in 10 seconds. Current budgets far below that — it waits at least a second between every request (about 1% of the limit), walks only a small bounded number of pages per run, and never retries into a rate error. A large fleet fills in over a few of the scheduled 6-hour syncs instead of all at once.
Each Addigy organization (a child organization under your MSP org) is one end-customer. Current lists all of them by name and auto-matches each to a Current company — first by the Autotask account id Addigy stores on the organization's policy (an exact match, on Autotask workspaces; on ConnectWise the name match carries the load), then by name, including lightly decorated policy names: a suffix like "Northwind Traders - Production", a site prefix, an environment tag, or an encoded character all pair to the right company as long as exactly one company fits. Anything genuinely ambiguous is listed as unmapped on the Addigy card for you to pick the company by hand. Mappings you set by hand are never overwritten by the auto-matcher, and unmapped devices still sync — they attach within seconds of you mapping the customer.
Most likely your Addigy account runs everything under one master organization and keeps customers as policies instead of child organizations — a common single-org setup. Current lists each policy as a customer in the mapping drawer, exactly like a child organization (hybrid setups with both work too). Check the Sync detail line on the Addigy connector card: it reports what the last sync found — how many child organizations and how many policies — and if your API token can't read policies, it shows the exact error so you can re-create the token with the right access.
Almost always because the match is ambiguous: two of your companies resolve to the same name — say "Acme" and "Acme Inc" — so auto-pairing would be a guess, and Current never guesses on mapping. Direct and lightly decorated names pair automatically; anything genuinely ambiguous waits on the Addigy card for you to pick by hand, on purpose. Map it once — a hand-set mapping is never overwritten, and its devices attach within seconds.
Three things. In NinjaOne, go to Administration → Apps → API, press Add, and create an API Services (machine-to-machine) application with the Monitoring scope ticked. That gives you a Client ID and a Client Secret — NinjaOne shows the secret once, so copy it before closing. The third thing is your region: NinjaOne runs separate instances (app.ninjarmm.com for North America, plus us2, eu, ca, and oc), and a credential only works against the one your account lives on. Pick it on the NinjaOne card to match the hostname you sign in at, paste both values, and press Test connection.
No. The NinjaOne connector is read-only. It reads organizations, device inventory, patch and antivirus posture, and the active alert set, and nothing else. Script execution, device commands, software deployment, policy edits, and organization management are not on the connector's allowlist, so Current cannot call them at all — and the Monitoring scope you grant in NinjaOne carries no write permission either.
The device's NinjaOne organization isn't mapped to that Current company yet. Current auto-links organizations to companies by normalized name and links only when exactly one company matches, leaving anything ambiguous for you. Open Integrations → NinjaOne → Manage → Customer mapping, find the organization on the Unmapped tab, and press Map. Its devices and alerts attach right away rather than waiting for the next 6-hour sync, and a mapping you set by hand is never overwritten by a later auto-match.
The mapped company's alert band picks it up on the next sync. The band turns critical on the first critical NinjaOne alert, and warns once critical and major alerts together reach three. Current mirrors the alerts that are active right now, so when a condition resets in NinjaOne its row leaves Current and the band clears itself — the count reflects open problems rather than everything that ever fired.
Because Inky has no pull API. Its only way to send data out is the Custom SIEM Feed, which POSTs events to a URL you provide. So Current hosts a receiver and gives you a secret feed URL to paste into Inky (Settings → Integrations → Custom SIEM Feed) — the reverse of every other connector, where you paste a key and Current reads the vendor.
No. Current keeps threat signals only — event type, verdict, threat level and category, timestamp, and the sender and recipient domains. Email bodies, HTML, subjects' contents, and attachments are stripped the instant an event arrives, before anything is written to the database, and are never stored.
Nothing yet — Awaiting feed means the receiver is enabled but Inky hasn't sent an event. Confirm the exact feed URL from the Current card is saved in Inky's Custom SIEM Feed with the JSON format, that any event filter isn't excluding everything, then use Inky's test-send. The card turns to Receiving within seconds of the first event.
Yes — completely. Unchecking a feed in the review's Data feeds panel doesn't just hide a chart: its numbers leave every page of the pack, its telemetry chapter drops out, and the AI never sees that data either — so no finding, callout, or recommended action can quietly reference something you removed. Re-check it and it comes back on the next build.
The Data feeds panel greys a feed you can't use and tells you which of three reasons applies: Not connected (set the integration up under Settings → Integrations), Connected but unmapped (the integration is on but this partner isn't matched to a company in it yet — map it), or Mapped but no data (everything's wired, but this partner genuinely has nothing there this period). Only the first two are things to fix.
Tenant admins and account executives / sales leadership. Branding lives in Settings → Branding (a logo and two brand colors), and the people who present reviews can edit it so a seller doesn't have to file a ticket to fix a logo before a QBR. Everyone else sees the branding applied but can't change it. It applies to the Strategic Business Review (the cover, the PDF, and Live mode), the partner portal header, and the emails Current sends on your behalf — campaigns, booking confirmations and reminders, partner project digests, invites, and partner notifications, which use your logo (favicon as backup) and brand colors on headers, buttons, and links.
Yes. Tenant-sent emails — campaigns, booking confirmations and reminders, partner project digests, invites, and partner notifications — carry a small, muted "Powered by Current" link at the bottom, on by default. A Tenant Admin can hide it with the "Show 'Powered by Current' on emails" toggle in Settings → Branding; flip it off and the line disappears from every branded email your workspace sends.
For readability. Brand colors are chosen for logos, not for pages of text, so a color that would make text hard to read (too little contrast against the surfaces it's used on) gets nudged just enough to clear a legibility bar — with a short note telling you it happened and why. It's a contrast guardrail, not a style opinion: a perfectly legible but unusual pick is left exactly as you set it.
No. Integration alerts are open-once and self-resolving: a rule opens one alert when it trips (not a new one every time the condition repeats), and the alert resolves itself automatically when the underlying problem clears — the backup succeeds, the detection is closed, the phishing surge subsides, compliance recovers. Nothing to dismiss by hand, and no stale alerts lingering after the fact. They're in-app only today, and outbound email/Teams notifications are off by default.
No. The three telemetry chapters read as themes, never vendor names — the partner sees "your security posture," "your fleet and network health," and "your backup and continuity picture," not the brands of your endpoint, monitoring, or backup tools. It keeps the review about their business, and it means changing a vendor never changes how the pack reads.
The same magazine the PDF prints, restaged for a room. Every chapter in the pack becomes one full-screen slide on a dark stage in your brand colors — the quarter on a page, the priced risk cards, the quarter-by-quarter road ahead, the team close — drawn from the same frozen numbers and inline edits as the printed pack, so the deck can never disagree with the document you hand over. PDF pages you attached in the wizard present too, one slide per page, after the team close. The same rules hold on screen: a chapter with no data has no slide, exactly as it has no page, and nothing is padded with a zero. Move with the arrow keys or by clicking either side of the screen; a chapter rail along the bottom shows where you are, and clicking any chapter jumps straight to it. Reviews built before the magazine redesign present in the same deck.
Everywhere it makes a review sound like yours. The tagline lands on the cover, the founding story and core values in a "how we work" band, your three uniques on the AI page, your backup methodology at the top of the backup chapter, and your account manager's sign-off on the closing team page — in both the printed PDF and the matching Live slides. The AI that drafts the review is handed your story too, so it can reference your values and uniques by name instead of inventing generic ones. Set it once in Settings → Branding → Your story (tenant admins and account executives / sales leadership can edit it); leave it blank and Current uses neutral fallbacks rather than making anything up.
From records, with the arithmetic visible. A priced risk card shows where its price came from: a price from a real quote wears a QUOTED chip, an account manager's figure wears ESTIMATE, and where no real number exists the column reads "By quote" or "Included" — never a fabricated amount. The value ledger's figures are computed from your workspace's own constants (Settings → Branding): minutes per monitoring catch, per quarantined phish, and per outage-class save, plus a downtime rate — with the factors printed beside every line, in your workspace currency. And the road ahead's total sums one-time and per-year costs separately, so nothing is inflated by mixing the two. Your internal costs and margins are never part of any of it.
Yes — Current partners get 10% off Handwrytten with the code CURRENT. Enter it in the "SignUp Code (Optional)" field on Handwrytten's sign-up form (the last box before the Terms and Conditions checkbox) before you press Sign Up. It's easy to miss because it's marked optional. Sign up at https://www.handwrytten.com?ref=otfimjl — the Handwrytten article shows exactly where the field is.
No. Test mode is on by default, and while it's on cards are accepted and processed by Handwrytten but never printed, mailed, or charged — so you can try the whole flow for free. Only when a Tenant Admin flips the Sending mode switch off test mode do real cards actually mail and bill to your Handwrytten account. See the Handwrytten article for setup and going live.
Yes. As soon as a lead arrives — from a website form or typed in with the New lead button — Current creates its company and its contact in your PSA and marks the company a Prospect, so your team finds the account where they already work. Current matches before it creates: if the lead's email domain already belongs to a company you have, the lead is linked to that company and nothing new is pushed, because an account that already lives in your PSA should never be re-created or overwritten. The contact is still created under it, so a new person at an existing company lands properly. Two things to know. This follows the CRM write switch in Settings → Integrations: while CRM writes are off nothing is pushed, and the company and contact wait in Current marked pending until writes are switched on. And on HaloPSA the client is created without a type, because Halo has no prospect field Current can set safely — the push result says so plainly rather than implying the mark was made. Leads imported from a saved list are never pushed, since those people and their companies are already in your CRM, and neither is a lead you added by hand by picking an existing person or company out of the New lead search.
Yes, and that's how New lead now opens. On Sales → Leads, click New lead and Current searches the people and companies already in your CRM. Type a name, an email address, or a company, then pick from the results. Picking a person fills in their name, email, phone, and company and links the lead to that contact and that company — nothing new is created, and nothing is pushed to your PSA, because they're already in it. Picking a company instead locks the lead to that account and leaves you to type the person, which is what you want when you have the account but not the name yet. For somebody genuinely new, choose "Not in the CRM yet? Enter it manually" and Current creates the company and the contact for you. This matters because typing a company name into a blank form was a guess: Current can't safely treat "Acme" as the same account as "Acme Industrial", so a typed name could quietly land a second copy of a partner you already had.
Yes. On Sales → Leads, click Funnels (next to the tabs, sales-leadership only) and add one — an M&A funnel beside your prospects funnel, for example. Each funnel keeps its own columns, so an acquisition doesn't have to travel the same stages as a website enquiry, and each one names the deal pipeline its green exit converts into: an M&A lead can open an M&A deal while everything else keeps opening New Logo. Switch between funnels with the tabs above the toolbar; they appear as soon as you have a second one. Your existing funnel is called Leads and still holds everything it always did — rename it to whatever you actually call it. A new funnel arrives with working columns and both exits already wired, so it's usable straight away, and you can start it from the standard columns or copy the columns from a funnel you've already tuned. To fill one: point a website form at it, choose it when you add a lead or import a list, or move an existing lead across from its row menu.
Yes. On Sales → Leads, open Funnels, click Settings on the funnel, and under "Who can see it" choose "Only the people I choose". Everyone else immediately stops seeing that funnel, its columns, its leads, and its notes — sales managers included. Being sales leadership is not a way in; only the people on the list are. Workspace admins do keep access, because they're the ones who manage the list, so there's always a way back if someone locks themselves out. You're added to the list automatically the moment you make a funnel private, so it can't vanish from under you. One thing worth knowing: the rule is absolute, so if a lead in a private funnel is somehow assigned to someone who isn't on the list, they won't see it either — which is why the Route to menu on that funnel only offers people who are.
Yes, and it can have none at all. Open Funnels → Settings on the funnel and pick one of three: use the workspace window (the default, and it names the number so you don't have to go looking), set a window just for that funnel between 15 minutes and 24 hours, or "No response timer". A funnel with no timer never shows a countdown, never flags a lead for going quiet, and never re-routes one to the next rep — which is the point for something like an M&A conversation, where a two-hour clock would be the wrong idea entirely. Everything else about the funnel works exactly as normal.
It leaves the tabs and keeps everything — its leads, their history, and its columns. Open Funnels and click Restore and it comes back exactly as it was; nothing is ever deleted. Two things Current won't let you retire: the funnel marked Default, and your last remaining funnel. Make another funnel the default first, and the Retire button unlocks. If you do retire a funnel while leads are still sitting in it, those leads show up in your default funnel rather than disappearing — a lead should never be somewhere you can't see it.
Open Sales → Leads and use Assigned to in the toolbar, then pick Mine. It applies to both the Funnel and the List, and it sticks — the page reopens on the same filter next time, on any device. The same menu holds My team (if you lead a sales team), any rep by name, and Unassigned for the leads nobody has picked up yet; there's a find box so you don't scroll a long roster. Reset next to the filters clears everything at once, and if this is a view you want back with one click, save it: Save view keeps the filter along with your columns and sort. One thing to know: an account executive can only ever load their own leads, so for a rep Mine and Everyone show the same board, and the rep-by-name and Unassigned rows are there for sales leadership.
On Sales → Leads, click "Import from list," pick any list from Sales → Lists, and choose some or all of its people. They land on the same leads board under the Lists source filter, in the first open stage, alongside your website and manual leads. Anyone who already has an open lead is shown pre-unticked and labelled before you commit, and the result tells you what happened — for example "12 imported, 3 skipped (already in the funnel)" — so nobody is skipped quietly. A lead you converted or discarded earlier is finished business and doesn't block a fresh import of the same person, and a dynamic list resolves its filter at import time so you get who is on it now. Imported leads arrive unrouted with no response timer, because they're people your team chose to work rather than an enquiry waiting on a reply; the clock starts when someone routes one. Nothing is pushed to your PSA either — these contacts and their companies are already there.
Into the list view on Sales → Leads, not out of Current. The funnel no longer keeps Converted and Disqualified columns — it has an outcome rail beside the board instead, and a lead you drop on "Drop to disqualify" leaves the board so the funnel only shows leads you can still work. Switch Funnel to List and the Status filter in the toolbar splits them by age: Discarded holds the last 30 days, and Archived holds the older ones. Both are equally restorable. Nothing is ever deleted, and there's no cleanup task to run. The quickest route is the quiet caption under the grey zone on the funnel — "5 discarded · View" — which opens the list with that filter already applied. The green zone has the matching "3 converted · View".
Open Sales → Leads, switch to the List view, and open Status in the toolbar — pick Discarded for a lead disqualified in the last 30 days, or Archived for an older one. On the row, Restore replaces the Convert and Disqualify buttons — click it and the lead goes back to the top of the funnel, ready to work again. You can also do it from the lead's drawer: click the row to open it and Restore sits in the action bar at the bottom. Age changes nothing about whether you can restore a lead; the 30-day line only decides which of the two it sits behind.
No. A note you add in the lead drawer stays in Current, on that lead, and nowhere else. It doesn't post to the company timeline, it doesn't show on the company record, and it never reaches Autotask, ConnectWise, or HaloPSA. That's deliberate: qualifying notes are working scratch, and notes about a lead nobody has qualified yet shouldn't land on an account your whole team reads. Once the lead converts, write what matters on the company or the deal, where it belongs. Adding a note does move the lead's Last touch, so a worked lead rises to the top of the list.
Click a column header. On Sales → Leads, switch Funnel to List and every header sorts: Lead, Company, Status, Source, Rep, Age, and Last touch — click once to sort, click again to flip the direction. It opens on Last touch, newest first, so whatever you worked most recently is at the top. Last touch moves when the lead's status changes, when it moves stage, when its rep changes, or when someone adds a note. Age sorts on when the lead arrived. Both sort on the real timestamps rather than the words on screen, so "today" and "3d" order the way you'd expect.
Because the integration isn't connected. Two columns — Handwrytten and Follow up — appear on Sales → Leads (between Qualified and Meeting set) only once a Tenant Admin connects your Handwrytten account in Integrations → Sales & marketing. If it's connected and they still aren't there, the card service may not be deployed in your environment yet — the connection card will say so. The Send a card button on company records follows the same rule. Don't have a Handwrytten account yet? Sign up at https://www.handwrytten.com?ref=otfimjl and use the code CURRENT for 10% off, then connect it. Full details in the Handwrytten article.
A lead you sent from moves itself into the Follow up column, and Current creates a to-do for you due about five business days later — roughly when the card should have landed — that rides your Microsoft To Do sync like your other to-dos. The card is also stamped on the lead and logged on the company timeline. Cards sent from a company record do the same (the to-do and the timeline note) with no funnel column involved.
About $3.75 in US dollars, plus postage, per live card, or whatever your Handwrytten plan pricing is — billed directly to your Handwrytten account, not through Current. The send dialog shows the price before you send, and in test mode nothing is charged at all. A Tenant Admin can also set an optional monthly card cap. See the Handwrytten article for the details.
The ones that hold real customer work — and not the four kinds of machine noise: alerts and monitoring, RMM automation, backup and BDR jobs, and spam or internal-IT chatter. Whether they're Autotask queues, ConnectWise service boards, or HaloPSA ticket types, Current highlights those with a "Recommended off" badge, but it only ever recommends — it never disables one for you. Muting a queue or board hides its tickets immediately so they stop distorting support history, sentiment, SBR stats, and AI insights; nothing is deleted in Current or touched in your PSA. Flip it back on and the tickets Current already synced reappear instantly, with new activity syncing again right away — tickets created while it was muted only return after an admin with CRM access runs a full ticket re-sync. You set this in the setup wizard's Mapping & noise step or later in your PSA's Manage drawer under Integrations; tenant admins can manage it with no CRM access. See the ticket-queue-noise article.
When you convert a won quote, the Win Quote wizard counts the labor hours off the quote's lines automatically into a "Professional-services hours sold" figure (each charge line has a Counts as sold hours checkbox, labor ticked by default), and the AI drafting the plan is told that number and your working-day window so it fits. A banner then compares the plan's task hours to what you sold, and Scale to match lines them up in one click — quarter-hour steps, never below 0.25 hours on a task, milestones untouched. It's guidance, not a lock: the project manager always has the final say.
Yes — as a first-class PSA, at the same depth as Autotask. ConnectWise PSA syncs two-way (companies, contacts, agreements, opportunities, projects, project tickets, members, and time entries), ConnectWise RMM feeds device inventory and patch posture into your business reviews, and ConnectWise CPQ won quotes flow through the same win-quote engine as ScalePad Quoter. You pick your PSA in the setup wizard, or connect it later from Integrations.
ConnectWise PSA, Autotask, and HaloPSA — one per workspace, chosen at signup and switchable later from Integrations. Current is not a PSA and does not replace yours: it expects one, and your PSA stays the system of record for tickets, contracts, and billing. If you don't run a PSA yet you can still start, but the PSA-driven features like billing sync and the whitespace grid wait until you connect one.
Yes — as a first-class PSA, at the same depth as Autotask and ConnectWise. HaloPSA syncs two-way (clients, contacts, opportunities, projects, milestones, tickets/tasks, contracts, and time), Halo stays the source of truth for time and billing while Current owns scheduling, and won Halo quotes flow through the same win-quote engine as ScalePad Quoter. HaloPSA support was added in July 2026. You pick your PSA in the setup wizard, or connect it later from Integrations.
No — one PSA per workspace (ConnectWise, Autotask, or HaloPSA), enforced at the database layer, not just the interface. Every synced record carries exactly one external identity, so Current never has to guess which system owns a company, project, or time entry. Switching is deliberate: disconnect the current PSA (a typed confirmation — nothing already pulled is deleted, and its synced projects freeze safely), then connect another from its own card.
No. The ConnectWise RMM connector is read-only twice over: the API credential is created in Asio with read-only scopes, and every request Current makes passes through a guard that only allows specific read endpoints. Automations, scripts, policy changes, and credential management are unreachable — Current reads sites, devices, and patch posture, and can never change anything in your RMM.
By authenticated polling, not a webhook — ConnectWise's callbacks carry no signature Current could verify, so Current polls ConnectWise every few minutes for won quotes and opportunities sitting at your configured Ready status-and-stage pair. Wins land in the same "Won quotes — ready to convert" queue as ScalePad Quoter wins, and the same wizard turns each into a project or post-sale ticket with charges in ConnectWise.
Yes, on an Autotask workspace. Current polls Kaseya Quote Manager every five minutes with a read-only API key you create under My account → Developer API, and a won quote lands in the same "Won quotes · ready to convert" queue as a ScalePad Quoter or ConnectWise CPQ win, converting through the same wizard into a project or a post-sale ticket with charges in Autotask. A won quote someone already converted by hand, with a project, ticket or contract created from its opportunity in Autotask, stays out of the queue, and every quote on a company record links to its opportunity as soon as that opportunity arrives from Autotask. Won means the partner accepted the quote, or a sales order exists for it; declined is a loss, and Pending approval and Approved (ready to send) are drafts. Its extra piece is what happens after the yes: the quote drawer shows the sales order and its status, what has been paid and how, and the purchase orders behind it, and when the order is marked fulfilled the project lead and whoever converted it hear about it. Every quote, at any status, shows on the company record, including the ones you raised long before you connected: the first sync imports your whole quote history. It is Autotask-only because a Kaseya Quote Manager quote carries Autotask ids and nothing for ConnectWise or HaloPSA, so those workspaces see the card but cannot connect. Current only reads Kaseya Quote Manager and can never change anything in it.
Give the history import time. The first sync brings every Kaseya Quote Manager quote onto the company records however far back it goes, and Current paces itself under Kaseya Quote Manager's API limits, so a long history arrives over a number of syncs rather than all at once. While it runs, the Kaseya Quote Manager card on Workspace → Integrations carries a line saying how many quotes it has read so far, and the line disappears when the import finishes. The "Won quotes to queue from the last" setting has no say in this: it only decides which won quotes are offered for conversion in the won-quote queue, so widening it will not make the import faster or bring more quotes across. If the card shows no progress line at all and the quotes are still missing after a few syncs, check the "Won-quote poller (Kaseya Quote Manager)" row on Sync health.
In Halo, sign in as an administrator and go to Configuration → Integrations → Halo API → Authorise a new application, choose "Client ID and Secret (Services)", note the Client ID and Client Secret, and grant the scope (Halo's own advice is "all" if unsure). Then in Current, open Settings → Integrations → HaloPSA, paste your Halo instance URL plus the Client ID and Secret, and run the test connection. Current works out your Halo auth and resource server addresses from the instance URL, and supports both hosted (yourcompany.halopsa.com) and on-premises instances. See the connect-halopsa article for the full walkthrough.
Clients become CRM companies (with Halo's native account manager filling the account-manager field), Halo Users become contacts and Agents become your team, opportunities become deals, and Halo projects — tickets with project features on — become Halo-synced projects with their milestones as phases and their child tickets or to-do items as tasks. Halo stays the source of truth for time and billing; Current owns scheduling (task start/end dates, criticality, and milestones), which it pushes back. Time logged in Current becomes a Halo action for billing, holidays and agent leave feed the scheduler, and client contracts drive MRR. See the HaloPSA field-mapping reference for the field-by-field detail.
Yes. Halo logs time as an action on a ticket, and once an action is on an invoice Current treats it as final and never edits or deletes it. Because logging billable time against a prepaid (Pre-Pay) contract draws down the client's balance in Halo, Current never re-sends a time entry blindly — every push is claimed once and confirmed by Halo's own response before it's considered done, so a retry can't create a duplicate charge or over-draw prepaid hours.
By authenticated polling — Halo's callbacks carry no signature Current could verify, and Halo has no "changed since" filter on quotes, so Current polls Halo for quotes that reached your "Accepted" quote status (the won bucket) and works out what's new by comparison. Wins land in the same "Won quotes — ready to convert" queue as ScalePad Quoter and ConnectWise CPQ. And yes — quoting is now PSA-agnostic: a won ScalePad Quoter quote converts into whichever PSA your workspace runs (Autotask, ConnectWise, or HaloPSA), building the project and pushing charges into that PSA.
Yes — Halo client contracts are read-only inbound, powering each company's MRR, customer status, and the whitespace grid. A contract's billing period (monthly, quarterly, six-month, or annual) is normalized to a true monthly figure. Halo stores that period as a numeric code whose meaning varies by version, so Current reads the human-readable period label; an unfamiliar period is left blank (which safely defaults to monthly) rather than divided by the wrong number, so MRR is never written wrong.
Task dates and status, task comments (as Halo actions), time entries, CRM company/contact/note/deal writes, and won-quote conversion (project build plus charges) all flow back to Halo — but never silently. Three gates stand in front: only HaloPSA-synced projects push at all (a Current-native project makes no Halo calls); the two-way sync switch controls task-field pushes; and CRM write mode (off by default, with a test mode that only touches "ZZ-Current Test" companies) controls every CRM write. Contracts, invoices, and the product catalog are read-only in every direction. See "What Current writes back to HaloPSA (and when)" for the full list.
Halo has no separate update call — you POST a record, and Halo creates or updates it based on whether the record carries its id. So every update Current sends includes the mirrored Halo id it stored on the first create or pull, which makes Halo update the existing record instead of quietly making a second copy; a create returns the new id and Current stores it immediately, so even a retry can't duplicate. For nested lists (a project's milestones, a ticket's to-do checklist, a Workday's holidays), Current reads the current list, merges your change onto it, and writes the whole list back — so items you didn't touch never disappear.
Yes — after every push Current reads the record back from Halo and compares what landed against what it sent. A value Halo accepted but quietly adjusted (a clamped date, a defaulted field) is reported as a residual rather than swallowed, and a failed push surfaces Halo's real error message, never a generic "sync failed." On time specifically, an invoiced Halo action is treated as final and is never edited, deleted, or retried.
A couple. HaloPSA is Current's newest PSA, so the post-sale ticket-path options (the queue/status/procurement picklists) and the ticket-sync diagnostic aren't wired for Halo yet, and Autotask project templates build only on an Autotask workspace. In each case Current shows a "not available for HaloPSA yet" message instead of a fake error — quote conversion into projects, charges, time, and the CRM writes all work now, and the deferred pieces light up as they ship.
As soon as it's won. The Commissions module reads your won deals automatically, so a deal you close lands on your next monthly statement with no data entry — it's assembled for you from your won deals, linked quotes, and goal attainment. The line starts near the bottom of the recognition ladder (Quote won) and climbs as the work becomes real. When it becomes fully Earned depends on your plan's trigger — on quote-won, on kickoff or a post-sale ticket (the default), or on invoice. So a deal can appear on your statement immediately while its line still reads Pending until the trigger is met.
Because your plan earns on invoice, and Current hasn't yet seen the deal invoiced in your PSA. Current checks Autotask, ConnectWise, or HaloPSA and moves the line to Earned once the deal is billed — you don't have to do anything. Some deal-and-reference combinations can't be matched to an invoice automatically; those stay Pending invoice rather than being guessed, and a sales leader can mark the line invoiced with one click once they've confirmed the billing. A "Pending kickoff" line is the same idea for plans that earn on kickoff: it waits for the kickoff or post-sale ticket.
No — once you submit, you can't pull it back or change it yourself. That's on purpose: a submitted statement is one you stood behind. If something needs fixing, your manager can return the statement to you with comments, and only then does it reopen for you to edit and resubmit. This keeps the review clean on both sides.
Someone else. Current will never let anyone approve their own statement — a sales manager's statement has to be approved by another sales leader or a tenant admin. It's a hard rule enforced in the database, not a setting, and it's the segregation of duties that keeps commission defensible.
Every earned line carries a 6-month clawback watch from the deal's close date — a heads-up that the commission is still inside the window where a customer could cancel or refund. Current doesn't automatically reverse your pay behind your back; if a cancellation happens, a sales leader adds a clearly-labeled negative adjustment line on a later statement, with a note explaining it. After 6 months the money is settled and the watch clears.
A Margin % component pays a percent of the gross margin — quote sell price minus quote cost — so it needs a linked quote to read those numbers from. If the deal has no quote linked, Current can't calculate the line and leaves it for your manager rather than guessing an amount. Link the quote to the deal and the line fills in on the next assembly. A TCV % line works the same way when a recurring deal has no term set — link the quote and set the term.
A sales leader can split a line between two reps — either by percentage (the shares must add up to 100%) or as a flat amount off the top, where a fixed amount goes to the assisting rep and the owner keeps the remainder. The split shows on both reps' statements, clearly attributed, so everyone sees their share and the totals reconcile. Like every manager edit, a split requires a disclosed note both people can see, and an edited line carries a MODIFIED badge — there are no silent changes to anyone's pay.
When you ask your manager (or nudge a rep) about a commission line, the message goes out as a real email from your own mailbox until your organization turns on Teams messaging — then the same asks arrive as genuine Teams 1:1 direct messages. The upgrade is a one-time Microsoft admin step: grant the Current app the Chat permission in Azure / Microsoft Entra ID and re-approve (grant admin consent) for the whole organization. After that, Current detects the new capability and switches from email to Teams automatically — nothing to change inside Current.
From your existing Sales Goals — the same "rock" your team already chases, set on the Goals page under Sales. Accelerators, goal bonuses, and President's Club all read those goals directly, so there's one quota number everywhere: change a goal in one place and every commission calculation that leans on it updates too. Commissions never keeps a separate, parallel set of targets.
Yes. President's Club is an optional leaderboard and it's off by default — sales leadership turns it on, and can turn it off any time, from the Club page. When it's off, reps still see the Club page but it shows a short teaching state explaining that leadership hasn't set it up yet, so the nav never dead-ends. Turning it off doesn't affect anyone's pay — President's Club is recognition, not commission.
Yes, by describing it. Dashboards is its own page in the left navigation, directly under Companies, and quick search finds it if you type dashboard or wallboard. It used to be the first tab on Reports, and an old link to that tab still brings you to the page. Click Add a tile and type the number you want to watch in plain words (tickets we closed this week, won revenue this quarter by rep, hours logged this week by person) and Current draws it as a gauge, a leaderboard, a trend, a donut, a bar, a table, or a single big number. Type your own request and it always asks three short questions about it, each with three suggested answers to click plus a box to type your own, and answering is optional on every one. Then it draws up to three finished tiles side by side with your real numbers so you pick the one you want, and a last step lets you set its name, shape, queues, target and colour bands with a live preview beside you. The starter chips skip the questions, because those are already worked out. One timeframe bar at the top drives every tile: Today, Week, Month, Quarter, Year, trailing 7, 30, or 90 days, or any custom range. Every tile has a Refine with AI action, so you change it by saying what's wrong with it. See the ai-dashboards article.
Because it now counts your sales pipelines rather than every pipeline you own. A sales gauge counts the boards whose type is set to new business, expansion or renewal in the pipeline manager; a projects board, an intake board or an acquisitions board is left out until you add it, and the gauge prints on its face which pipelines it counted. Two amounts moved with it. A project deal counts once instead of being multiplied by twelve, because its money is a quote price rather than a monthly bill. And a won expansion counts the increase it brought rather than a partner's whole new monthly bill, which is the rule the rep leaderboard on the Sales page already used. The number you see now is the one the Pipeline and Forecast reports have been showing all along. To put a board back into a gauge, open Edit tile, go to Filters and tick it in the pipeline list; Use my sales pipelines takes it back to the default. See the ai-dashboards article.
Yes. Open the tile menu, choose Edit tile, and the Filters section holds a pipeline list. Leave it alone and the gauge counts your sales pipelines, which are the boards set to new business, expansion or renewal, and it will pick up any sales pipeline you create later. Tick a projects, intake or acquisitions board and the gauge counts that too. Untick one of your sales pipelines and it stops counting it. Either way the tile says on its face which pipelines are in the figure, and the panel tells you which way your change moves the number before you save. One thing worth knowing before you name a list: a gauge that names its own pipelines stops following your workspace, so a pipeline you create next month will not join it until somebody ticks it. That is why leaving it on the default is the better choice whenever it fits. A pipeline set to members only appears in this list for the people on its member list, and a gauge counting it shows a smaller figure to a colleague who is not on that list, exactly the way the deal boards already work. See the ai-dashboards article.
Because some won deals have no owner, and the rows on a leaderboard have to add up to the number above them. A won deal nobody owns is grouped as Unassigned rather than dropped, on the dashboard gauge and on the rep leaderboard on the Sales page alike. Dropping those deals would give you a board that quietly does not sum to your won revenue, and a reader comparing the two screens would find them disagreeing with nothing on either one explaining why. If the row is large, that is worth knowing on its own: it is telling you how much of your won business is not credited to anybody. Set an owner on those deals and the row shrinks. See the ai-dashboards article.
Yes, and the board will say that you did. Open the tile menu, choose Edit tile, and find Who's on this board. It offers Everyone, which is the default and what every tile you already have is set to, Everyone except, where you pick the few to leave out, and Only these, where you name the handful to show. You choose from the people, partners or queues the board itself returns, not from a directory. Here is the part to know before you use it: a tile with anyone left out always prints how many on its face, in words like 3 people hidden or Only 5 people shown, and that line cannot be collapsed or tucked into the notes. Open About this number and Who's on this board lists the names, so anyone looking at the board can find out exactly who in one click, including on a lobby TV. That is deliberate. A five-row leaderboard with two colleagues removed looks exactly like an ordinary five-row leaderboard, and a reader would fairly conclude those two closed nothing, so a board is never allowed to hide people quietly. The count reflects what the tile is set to do rather than how many rows happened to appear, so it stays correct in a week where a hidden colleague had nothing to show anyway. See the ai-dashboards article.
Yes, on your ticket gauges, and the tile will say that you did. Open the tile menu, choose Edit tile, and under the filters you will find Partners on this tile and People on this tile. Each offers Everyone, which is what every tile you already have is set to, Everyone except, where you pick the few to leave out, and Only these, where you name the few to count. They are separate so you can leave out a partner, or a contractor, or both. This is not the same as Who's on this board: that one decides which rows a leaderboard draws, while these leave the work out of the number itself, so they need no breakdown and apply to a single figure, an aging histogram or a daily line just as much as to a board. The filtering happens in the database before anything is totalled, so an excluded partner's tickets cannot reach a total, an average, a percentage, a ranked row or the Other bucket. And because a single figure with work taken out of it looks completely ordinary, the tile always prints what it left out on its face, in words like 2 partners excluded, and names exactly who under About this number, including on a lobby TV. The control appears only on gauges that genuinely apply it: tickets opened, closed, open now, closed by person, average first response, average resolution time, ticket aging, the opened-versus-closed line, and SLA compliance. SLA compliance was the last one to get it, because Current only publishes an SLA percentage once enough resolved tickets carried an SLA verdict from your PSA, so narrowing that tile means narrowing the check behind it by exactly the same rule. It now does. See the ai-dashboards article.
Open the tile menu, choose Edit tile, and click Advanced under Where it comes from. It names the real tables the number is read from and the read it goes through, exactly as they are in the database. Advanced tells you where a number comes from; it does not yet let you send a tile somewhere else. Picking which of your connected systems answers a number is a change we want to get right, because two systems do not count the same events, and it will arrive as its own update. Two things worth knowing: Advanced prints table names but never lets you type one, and every read still runs as you under your own permissions. If you used the Read this from picker in the day it was available, the source you chose was never applied to the number, and the Source adjusted label it left on the tile is gone; your next save on that tile clears the leftover setting. See the ai-dashboards article.
Open the tile menu and choose Edit tile. The panel reads as eight plain sections in the order you would need them to work the figure out by hand: where it comes from, what it measures, how it is broken down, the period it covers, what it leaves in, how it is judged, how it is drawn, and what the figure is in. Each one says what it is in a sentence, says what Current chose and why so you can tell the AI's judgement from somebody's own, and hands you the control to change it with the tile drawn live beside you. Before you save, the panel says in plain words what your change will do to the number and which way it moves, and a control that only changes how the tile looks says so instead of leaving you guessing: shape, colour bands and the target never move the figure, and adding a breakdown splits the same total without changing it. A tile built before this arrived has no recorded reasoning, so those sections say the choice was Current's default rather than inventing one. Anything overridden by hand leaves the word adjusted on the tile face and is listed under About this number, and a later Refine with AI keeps your hand-set choices and tells you first if any of them cannot carry over. See the ai-dashboards article.
Yes. There is a sun and moon control in the dashboards toolbar, on the right next to the dashboard name, and it switches that page between light and dark. It changes the dashboards page only: your sidebar, projects, the CRM and every other screen stay as they are. The choice follows you rather than the machine, so a board you set to dark on your laptop is dark when you next open it somewhere else. Wall screens are already dark without you doing anything: Present mode and TV links both open dark, since a bright white board in a dim office is the first thing people ask us to turn down. In Present mode the same sun and moon control sits in the bar at the bottom, so whoever is driving can switch that session to light without changing their own desk. A TV link has nobody standing at it, so add ?theme=light to the end of the link to keep that screen light; anything else on the end is ignored and the screen stays dark, so a typo can never leave a lobby TV blank. None of the numbers change with the theme, and colours were rechecked so arcs, bars and chart labels stay readable in both. See the ai-dashboards article.
Because by default Current decides that by size, and the tile got big enough to become a hero tile: a deep ink card with the figure in large type and its change and trend line underneath. Make the tile smaller again and it goes straight back to an ordinary card. If you would rather it stopped changing when you resize it, open the tile menu, choose Edit tile, and set Tile style to Standard card to keep it an ordinary card at any size, or Always hero to keep the dark look at any size. Hero tiles look the same whether the board is light or dark, and About this number still sits underneath them exactly as it does on every other tile. See the ai-dashboards article.
Yes. Open the tile menu, choose Edit tile, and look for Tile style. Automatic is the default and is what tiles do today: make one big and it wears the dark hero look, make it small and it goes back to an ordinary card. Always hero keeps the dark look whatever size the tile is, and Standard card keeps it an ordinary card however big you make it. Once you pick either of those two, resizing never changes the look again. It only changes which card the figure is drawn on: the number, the timeframe, the queues it counts and the explanation under it are all untouched. The setting appears on single-number tiles and gauges only, because a leaderboard, a table or a chart cannot be drawn on the dark band. On a very small tile Always hero falls back to an ordinary card, since the hero look needs room to read. Your choice also survives a Refine with AI, the same way your queue and timeframe choices do. See the ai-dashboards article.
It moved to its own page. Dashboards is now in the left navigation, directly under Companies, so a board you check every morning is one click away instead of two clicks inside a reporting page. Quick search finds it too: type dashboard, dashboards or wallboard. Nothing you built changed, and nothing was lost. Every board, tile, arrangement and TV link is exactly where you left it, and the page still remembers the timeframe and the dashboard you had open. Any link you saved to the old tab takes you straight to the new page. Reports is now one page of its own, grouped Delivery, Team, Finance, Service and Sales, and it opens on Portfolio overview.
Into Reports. There is one Reports page now, with a rail down the left grouped Delivery, Team, Finance, Service and Sales, and the seven sales reports are the Sales category in it: Pipeline & forecast, Forecast accuracy, Deals by type, MRR movement, your scorecard, Whitespace coverage and Book & activity. Nothing was dropped and the numbers are the same ones. A link you saved to the old page lands on the report you had open, and an old date-range value in that link resolves to the nearest preset on the new control. The navigation carries one Reports row for everyone on staff, pinned beside My Day, Portfolio and Dashboards. The other thing that used to be called Reports, the commission statement archive, is now Statement history, so exactly one thing in Current is called Reports.
Because the rail lists only the reports your role can open, and a category with nothing in it for you is not drawn at all. The Delivery reports and Budget are for everyone on staff except account executives. Effort and Capacity are for project managers and tenant admins. Profitability is tenant admins only, because it is built on cost rates. The Service desk report and every sales report need CRM access, and inside Sales, Forecast accuracy and MRR movement also need money to be visible to you, which means an account executive, a sales manager or a tenant admin. The scorecard opens as My scorecard for an account executive, holding their own numbers. The rail is the courtesy; the wall is underneath it, where every row a report reads comes back through your own database permissions, so a report you cannot see is not reachable by editing the address either.
That the number is a fact about right now rather than a total over your date range, so there is nothing to compare it against. Active projects, open pipeline, who is over capacity and the health mix are all of that kind: they describe how things stand today, and Current does not keep a record of what open pipeline stood at on the last day of August, so it will not draw a change figure it would have to invent. Tiles that do cover the date range carry the change against the period before, and the chip beside them names the period it measured: hours logged, deals won, tickets closed, MRR added, risks opened.
Open Reports, press Schedules at the top of the page, and add one. Pick up to eight reports from the ones you can open, choose monthly on a day of the month or its last day, set the hour, and pick the period the email should describe: the previous full month is the default, with the last 30 days, the last 90 days, this quarter to date and this year to date as the alternatives. Weekly works the same way on a weekday, with the previous full week as its default period. The hour is read in your workspace time zone. What arrives is one email with one PDF attached, a cover page and then a section per report, carrying the comparison figures unless you turn Compare off. Send a test now delivers the real thing to your own address so you can read it before anyone else does, and a schedule can be paused or deleted whenever you like. You do not need to be an admin to set one up for yourself.
A tenant admin can. On a schedule, admins get two extra fields: other members of the workspace, and up to ten addresses outside it. A member's copy is worked out as that person, so nobody is emailed a figure they could not open in Current themselves, and a member whose reports all sit outside their permissions is sent nothing. An outside address has no Current account and no permissions, so it receives the reports exactly as the admin who owns the schedule sees them, and the form says so where you type the addresses. If you are not an admin, a schedule you create sends to your own inbox only.
Because that section's data could not be read just now, and Current will not print a zero over a failed read. A zero and a broken read look the same on a chart and mean opposite things, so the section carries a sentence naming what could not be read, and the rest of the report still renders. Two kinds of sentence turn up. One says the read failed and is worth trying again in a moment, which is usually a slow or unreachable source. The other says the feature turns on once the workspace finishes updating, which is what you see during a release before the database side has landed, and it clears itself. The same rule follows the report into the PDF and into a scheduled email: the email still arrives, carrying the sentence where the figures would have been, and the run is logged as partial.
No, and it does not any more. A dashboard's arrangement is shared, but what each person can see is not: a tile whose numbers your role does not reach is hidden from you. Those hidden tiles now hold their slot, so you see an empty space where one sits, and nothing you drag can move it. The gap is deliberate. Closing it on your screen meant your own edits were then saved against the tidied-up version, so making one tile slightly taller could quietly re-order three tiles you had never touched, and simply opening and closing the board could rewrite the arrangement for everyone. A visible gap is a much smaller price than that. See the ai-dashboards article.
Below laptop width the board is a single column rather than a twelve column grid, so there is no drag and there are no corner handles. Each tile carries its own controls underneath instead: a move up button, a move down button, and a height bar you drag or nudge with the arrow keys. Moving a tile there rearranges the whole board and keeps the widths you set on a laptop, so a tidy-up on a phone does not flatten your desk layout. On a laptop, grab the grip in the tile's top left corner to move it and pull any of the eight edge or corner handles to resize. See the ai-dashboards article.
You should not any more, and if you do it is worth telling us. Every window on a dashboard, on a TV board and in Reports is now cut in your workspace's time zone: today, this week, this month, this quarter all mean the same thing to everyone, whichever country they are sitting in and whichever clock their laptop is set to. Each tile prints that calendar under the number, beside the window it covers, so the two of you can compare the same words instead of guessing. The Reports header, every printed report and every TV board say it too. A workspace admin sets your zone in Settings, in the Workspace basics section. It starts on the zone Current already used for notification timing and the lead response clock, so there is nothing for you to set. Some numbers did move the day this shipped, and here is exactly which: the forecast tile and the sales reports used to cut their months and quarters at UTC midnight, so on any workspace outside UTC a deal that closed in the last hours of a month could sit in the wrong month. It now sits in yours. Totals in the middle of a window did not move.
Your workspace's, not your laptop's and not UTC. There is one zone for the whole workspace rather than one per person, deliberately: a number two people cannot compare is a number they can only argue about. So today, this week, this month and this quarter mean the same thing to everyone in the workspace, and to the TV board in the lobby, which used to count on the clock of whatever screen it was playing on. You can always see which calendar a number was counted on: every dashboard tile prints it under the number beside the window it covers, the Reports header and every printed or exported report carry it, and a TV board prints it along the bottom. It starts on the zone Current already used for notification timing and the lead response clock, so there is normally nothing to set, and a tenant admin can change it in Settings, then Workspace basics. Two limits. Quarters are calendar quarters, so a financial year that does not start in January is not supported yet. And a sales goal's progress still measures its month, quarter or year at UTC edges, because the database side that produces those actuals does, and moving one half without the other would be a worse bug than the one it fixes: a deal closed in the last few hours of a month can therefore land on the next month's goal bar while Reports counts it in the month it closed. Which period the goals page treats as the current one does follow your zone.
Settings, then Workspace basics. Only a workspace admin can change it, the card shows you the date and time in the zone you have picked before you save, and every change is recorded in the audit log. Changing it re-cuts every window on a different midnight, so counts right at the start or end of a window will move and so will the daily points on a trend. Totals in the middle of a window do not move. A TV board that is already playing follows the new zone on its next refresh, which the card warns you about before you confirm. Quarters stay calendar quarters for now: if your financial year does not start in January, tell us and we will add it.
Because Current worked that number out itself instead of using a metric from its vetted catalog, and it will not pretend otherwise. The footnote reads "AI-computed metric. Verify this number against your source before relying on it." Check it against your PSA or the matching report under Reports on the same date range, then use Mark verified on the tile menu: the footnote then names you and the date you checked it. The asterisk stays on purpose, so anyone reading the dashboard later still knows the difference between a number an engineer wrote and a number the AI assembled. Catalog tiles have no asterisk at all.
Only if you publish it. Every dashboard starts personal, visible to you alone, and you can keep as many as you like. Project managers and tenant admins can also share one with the team, in which case it has a single layout that its editors control. Sharing never widens what anyone can see: a tile whose data sits behind a wall a viewer isn't through (cross-person hours for a non-manager, CRM numbers for someone without CRM access) simply isn't shown to them, and the database enforces that, not the interface. Partners never see Dashboards or Reports at all.
Connect the integration it named, then ask again. Current builds only from systems you actually have connected, so a satisfaction tile needs CrewHu, a phishing tile needs Inky, and a warranty tile needs ScalePad Lifecycle Manager. Rather than drawing an empty tile, it names the one it needs and links you to Settings → Integrations, where a tenant admin connects it. Give it one sync cycle to land (most reporting connectors refresh every 6 hours, your PSA every 5 minutes), and the sample prompts and everything Current will build widen on their own. This is different from Current telling you it does not hold a number yet: that one is not fixed by connecting anything, and Current says so rather than sending you shopping.
Because it would not be true, and Current would rather say so than draw it. There are three different reasons and the wording tells you which one you have hit. The number needs an integration nobody has connected yet, in which case Current names that integration and points you at Settings → Integrations. The number sits behind a wall your role is not through, such as cross-person hours or CRM figures, in which case it says that kindly and never builds a substitute. Or Current genuinely does not hold the number yet, whatever you connect: technician utilization, first contact resolution, escalation rate, quote win rate, blended gross margin, revenue per technician. In that last case Current gives you one plain sentence on what is missing and offers the nearest numbers it can really draw as buttons you can click, already checked against your permissions and your connected systems. Reactive hours per endpoint used to be in that last group and is not any more: Current mirrors your PSA's service ticket time now, so ask for RHEM and you get the real gauge. See the ai-dashboards article for the full list.
By default yes, and you can change that. Average first response and average resolution time can be measured on plain elapsed time or on the hours your desk actually works, and every workspace starts on elapsed time so nothing moved under you. Elapsed time is why an 8x5 desk looks bad against the 60 minute benchmark on that tile: a ticket that lands at 5pm on Friday and is answered at 9am on Monday scores 3,840 minutes, when on an eight to five desk it took one working hour. Every published response time figure in this industry, including that one, is measured on open hours. A workspace admin sets your desk's hours in Settings, then Workspace basics: when you open, when you close, which days you work, or that you work around the clock. Holidays come from the list you already keep under Holidays, the same one the project scheduler skips. Switching to working hours makes those two numbers smaller, usually two to three times smaller for an eight to five desk, so tiles that read red can turn green. That is the correction, not a break, and each of those tiles says under its number which of the two clocks it counted on, so you never have to guess. Nothing else changes: ticket counts, open ticket aging and the trend charts are not on this clock.
Almost certainly a tenant admin switched your workspace from plain elapsed time to your desk's working hours, in Settings, then Workspace basics. On working hours only the hours the desk is open count, so nights, weekends and the days on your Holidays list stop counting, and for an eight to five desk average first response and average resolution time usually read two to three times smaller. A ticket that arrived at 5pm on Friday and was answered at 9am on Monday now scores one working hour instead of 3,840 minutes. Tiles that read red can turn green, and that is the correction rather than a break: every published response time figure in this industry, including the 60 minute mark on the first response tile itself, is measured on open hours. You can tell which clock a tile is on without asking anyone, because both of those tiles say under their number which clock they counted on, in the app, in Present mode and on a TV board. Nothing else moved: ticket counts, open ticket aging, the opened versus closed trend, hours logged and SLA compliance are not on this clock. If you need to know exactly when and who, the change is in your audit log, and a workspace can be put back on elapsed time in the same place.
It sorts itself now, and rank 1 is your fastest responder. On a number where a lower figure is the better one there is only one correct order, so average first response and average resolution time always rank fastest first when you break them down by person, queue or partner, and the tile says so under its number. There is nothing to set, and asking Refine with AI to reverse it gets you a sentence saying the board already reads that way rather than a tile that quietly changes nothing. Two things came with it. Every row says how many tickets it is an average of, and a row built on fewer than five tickets sits below the ranked rows without a rank, because one overnight ticket out of three is a fact about a ticket rather than about a person. And a board showing eight of twenty five now tells you how many it is not showing.
Because until you set your desk's hours they were measuring with two different clocks, and both were reading their source correctly. SLA compliance is your PSA's own verdict on each ticket, worked out against its own due times, which already follow the partner's SLA calendar, their priority tiers and their exclusions. First response time was Current subtracting two timestamps, which counts nights and weekends. Set your desk's hours in Settings, under Workspace basics, and the two tiles start telling the same story. Current never re-works out the SLA verdict itself, deliberately: if it did, your dashboard could disagree with the SLA report your partner gets, and then neither number is worth anything.
Because too few of your resolved tickets carried an SLA verdict for a percentage to mean anything. The tile now prints its own denominator, in the form based on 14 of 3,902 resolved tickets, and when fewer than twenty carried a verdict it hides the percentage and tells you so. A green 100 percent off three tickets is not a fact about your desk, and on a wall screen nobody can question it. Widen the timeframe, or check that your PSA is setting SLA targets on the tickets you expect. Only Autotask sends SLA verdicts into Current today, so a ConnectWise or HaloPSA workspace is not offered the tile at all. Broken down by partner, queue or person, the same floor applies to each row, and the rows it leaves out are counted on the tile face.
Ask for it by name, or pick the starter suggestion called Reactive ticket hours per endpoint. It divides the hours your team logged on service tickets in your PSA by the workstations and servers your RMM manages, and reports that as a monthly rate. Two things have to be true first: your PSA has to be one whose ticket time Current mirrors, and a tenant admin has to pick which RMM counts endpoints in Settings, under Integrations, because counting two RMMs would count the same machine twice. Until that pick is made the tile says so instead of showing a zero. On the tile you will always see which RMM was counted, how many endpoints are not matched to a partner yet, and how much of the time was entered on the day the work happened, because below about 90 percent same day entry the number is a floor rather than a measurement. Reactive means service tickets people asked for: tickets your monitoring raised automatically, and queues an admin marked as project work, are left out. It is a monthly rate, so a timeframe shorter than a week, a board set to today for instance, is answered over the 30 days ending on the day you picked, and the tile names those 30 days.
Because somebody worked those hours and Current holds no cost rate for them, a subcontractor or somebody without a Current login for instance, and pretending their time was free would flatter the number. The tile counts those hours, names them as unpriced hours, and says the margin reads higher than the truth because of them. Cost rates sync from your PSA, so the fix for these tiles is to make sure everyone who logs service time exists there with a cost rate and is linked to a Current login: the dashboard tiles price linked people only, while the renewal dossier prices every active technician straight from the PSA rate, login or not. Two more things worth knowing: managed services margin covers reactive labor only, not tools, licenses or project work, so it is not a full gross margin, and both money tiles always answer for one whole calendar month because recurring revenue is a monthly figure, so on any other timeframe, a quarter or a year included, they show a whole month and name it on the tile: the last complete month for a timeframe ending today, and the last month that had finished then for a timeframe dated further back. On a timeframe longer than a month the tile also says why it is showing one month. These dashboard tiles are tenant admins only, because they are built directly on cost rates. Account-level margin has a second home that is not admin-only: the renewal dossier's private profitability section, which sales leadership and account executives can read one account at a time, and which prices hours from every active technician's PSA cost rate whether or not that person has a Current login.
Because a zero there would be a claim, and Current will not make a claim it cannot back. Backups failing, EDR alerts open, SOC incidents and phishing caught used to show a reassuring zero both before the product had ever sent Current a record and while a read was failing, which is the worst possible place to be wrong. Now each tile says which situation you are in: waiting on the first data from that product (it is connected but has sent nothing yet, and it fills in with the first sync), could not read this number (a tile that already had a number keeps it, says it could not refresh, and lets the Updated stamp keep aging), or the number would be incomplete (only part of a large fleet could be read, so check that the product is syncing under Settings, Integrations). A genuine zero over a product that has delivered records is still shown as a zero, because a quiet week is real. Devices compliant goes further: if any connected RMM cannot be read it refuses the whole percentage rather than publishing the RMMs that did answer, prints how many devices actually reported, and says when it is mixing Windows patch compliance with Mac policy compliance.
Yes, and they now say so under the number. Every ticket tile counts machine-raised alert tickets alongside the ones people asked for, exactly as your PSA stores them, so a workspace whose RMM opens hundreds of alert tickets a month sees counts that read higher than the support load feels. Nothing about your numbers changed when that note appeared: choosing which queues a tile counts is being built, and Current will ask you which queues to include when you build a ticket tile. Until you choose, your existing tiles count precisely what they counted before, so no wallboard changes under you.
Because two things about a ConnectWise service ticket were being read wrongly, and both are now fixed. Current used to treat a ticket as closed only when ConnectWise had stamped a close time, so every ticket ConnectWise considered finished without one stayed open forever: Tickets open now and all four aging buckets read too high, Tickets closed read too low, and the opened versus closed chart showed a backlog that only ever grew. Current now trusts ConnectWise's own closed flag, and where there is no close time it uses the ticket's last update as the closing moment and says so on the tile, since a resolution time built that way is an upper limit rather than a measurement. Second, Tickets closed by person used to measure the ticket owner, which ConnectWise desks often never set, so that leaderboard was mostly Unassigned; it now measures the person the work was dispatched to and takes the name from your own resource list, so bars move and some names appear for the first time. Current re-reads the last 24 months of ConnectWise tickets once, a chunk at a time across your normal syncs, so the numbers settle over a few hours to a few days. The same correction reaches the Tickets chip on a company, the ticket figures in a Strategic Business Review, the AI company insights, whitespace signals and the renewal dossier, so a review exported last month will not match one exported today. Autotask and HaloPSA workspaces are not affected.
Because time your PSA voided and time a manager rejected stopped counting as delivered work on 26 July 2026. A voided entry is one your PSA deleted during pre-invoice review, so nobody was ever billed for it. Rejected time was turned down as not worked. Counting either one as delivered hours overstated what your team actually did, so both are now out of Hours logged, Hours by person, My hours, Budget used, the count of projects over budget, and the Effort, Capacity, Budget and Profitability reports under Reports, along with the CSV they export. Expect lower hours totals, a slightly flatter burn-rate trend and a shorter list of projects over budget: a project that was over budget only because of voided or rejected hours stops being named, which is the correction rather than a loss. Nothing was deleted. The entries stay exactly where they were on your Time page and in the task panel, marked and struck through, with the amount that is not counted printed beside the total, so you can always see what happened. Two places are deliberately different. The Budget % column and over-budget filter on the Portfolio page are the percentage your PSA reports, not Current's hours math, so they did not move. And where a figure is your PSA's own worked hours, which is the case for estimate versus actual on a synced task and for the close-out pack, it already left voided time out but can still include rejected time, because Current does not re-cut a number your PSA reported.
The number is the last one Current managed to read, and the tile says so rather than blanking or pretending. When a read fails, times out or is refused, Current keeps the number that was already on screen and prints a line in amber under it: Couldn't refresh this. Showing the last number Current read. The Updated stamp in the tile header keeps aging so you can see how old the number is, the tile retries by itself about every 90 seconds, and the line clears as soon as a read succeeds. A tile that never had a number says it could not read this one instead of showing a zero. That line now appears in the app, in Present mode and on a TV screen, so a wallboard can no longer show a frozen number silently. You will never see database wording on a tile face either: a read that takes too long says it took too long and Current will try again in a moment, and the technical detail goes to the browser console where an engineer can find it. If the line stays up for more than a few minutes, open Settings, under Integrations, and check that the product behind that tile is still syncing.
Because a ticket gauge is only as good as what your PSA sends Current, and not every PSA sends the same things. Tickets opened, tickets closed, tickets open right now, tickets closed by person, average resolution time, open ticket aging, and opened versus closed all need Autotask or ConnectWise. Average first response and SLA compliance need Autotask, because ConnectWise does not send a first response time or an SLA verdict and Current will not guess one. On HaloPSA no ticket gauge is offered yet: HaloPSA syncs your projects and time, but its service tickets do not reach Current, so those tiles would sit on zero forever and a zero on a wall screen reads as a quiet week rather than a missing feed. Nothing else is affected, since projects, hours, tasks, budget, capacity and the whole CRM are Current's own numbers and work whichever PSA you run. HaloPSA ticket sync is being built, and the gauges appear on their own once it lands, with nothing for you to switch on.
Yes. Every intake form has a hosted page of its own, and its card in Settings, Integrations, Website leads gives you two ways to use it. Copy the one-line embed snippet and paste it into whatever block your site builder uses for raw code: the Custom HTML block in WordPress, the HTML widget in Elementor, a Code block in Squarespace, an Embed HTML element in Wix, an Embed in Webflow, or straight into the page if somebody hand-writes your HTML. It is a single frame with no script and no plugin, so there is nothing to install and nothing to keep updated. If you would rather not touch the site at all, use the plain link instead: send it in an email, put it behind a button, or turn it into a QR code for a stand at an event. Leads from the link and from the embed land on the same board, tagged with the same form. The older path is untouched as well, so a WordPress or Elementor form you already built keeps posting to the same intake URL and keeps arriving as leads.
Yes, and it is set on the form rather than in your rules. Open the form in Settings, Integrations, Website leads and find Who gets the lead and choose one of three: Routing rules, One rep, or Share round-robin, which takes turns across the reps you pick, one lead each, in order. A form set to One rep or Share round-robin has already decided, so your routing rules are not read for it. Every form you already have is on Routing rules, which is exactly what it did before this setting existed, so nothing changed under you. If the named rep later leaves the workspace, is switched off, or loses CRM access, and if a group is emptied, the form falls back to your routing rules rather than dropping the lead.
It still arrives, and it is still somebody's problem. A lead that no rule and no rotation could place is marked unrouted and sales leadership is emailed about it, so it sits on the Leads board waiting to be picked up rather than disappearing. Filter the funnel by Assigned to and choose the leads nobody has picked up to see them together. The same is true when a form's chosen owner has gone: a named rep who left the workspace or lost CRM access, or a group you emptied, sends the form back to your routing rules instead of losing the lead. If you want a second set of eyes on every submission regardless of routing, add a shared inbox such as sales@northlake-it.example to that form's notify list, up to five addresses, and it gets a copy of the same lead email. Those addresses do not need a Current login, and adding one does not assign the lead or change who the response timer is running against.
Yes. Each intake form carries its own ordered list of questions that you write. A new form starts with first name, last name, work email, phone, company and a message box, and from there you add your own, reword them, move them up and down with the arrows, or delete what you do not need. A question can be Short text, Long text, an Email address, a Phone number, a Number, a Date, a Dropdown, Pick one, a Yes / no checkbox or Pick several, and each one can be required or optional. Beside each question is an Also fill setting, where you say which answer is the First name, Last name, Email, Phone, Company, Market segment, Region or Message, so Current can name the lead, match it to a company you already serve, and route it. An answer with no mapping is still captured and read back on the lead in the order it was asked. Two things worth knowing: map one question to email, because the email address is what matches a lead to an account you already have instead of creating a second copy of it; and rewording a label later is safe, because each question keeps a fixed machine name underneath, so a website form or webhook already posting to it keeps working and answers already collected keep the wording that was on screen when somebody answered them.
Yes. A tenant admin opens Settings, then Workspace basics, and picks your team's word under What do you call your customers?: Clients, Customers, Partners, Users, or Kunden (German). It is a fixed list rather than free text, so the singular, plural, and mid-sentence forms are always right, including the German capitals. Current then uses the word everywhere a person reads it: every page, the emails Current sends, the portal the businesses you serve sign into, the name of their read-only viewer role (a workspace on Clients sees Client Viewer), and anything the AI drafts for you. Workspaces that existed before the setting stayed on Partners, so nothing changed the day it shipped; a new workspace starts on Clients. Saving re-words the product for everyone in the workspace, colleagues who are signed in see the new word on their next refresh, and nothing else changes: no data, no numbers, no access.
Yes. A tenant admin opens Settings, then Workspace basics, and picks it on the Workspace currency card. There are sixteen: US, Canadian, Australian, New Zealand and Singapore dollars, Mexican pesos, pounds sterling, euros, Swiss francs, South African rand, Indian rupees, UAE dirhams, Swedish, Norwegian and Danish kroner, and Japanese yen. One currency covers the whole workspace, and every money figure follows it: deals and pipeline, MRR and margins, commissions and statements, dashboard tiles and TV boards, exports, and the reviews you send. Changing it relabels rather than recalculates, so a figure recorded as 4,000 stays 4,000 and starts reading as 4,000 of the new currency. The card says so before you save, and the change is written to the audit log. Current's own subscription is billed in the currency chosen at the plan step, one of six, and that choice is separate from this one.
No, and that is deliberate. There is no exchange-rate table and no rate-as-of date anywhere in Current, so the figure your PSA holds is the figure Current shows. That means two things worth knowing. If your PSA's base currency is different from your workspace currency, Current says so when you connect it and leaves both numbers alone rather than blocking the connection. And if a quote comes in on another currency, the deal is still created, with the mismatch flagged on the quote and in the won-quote queue, so a seller sees it before it reaches a forecast. A number Current cannot vouch for is named rather than converted.
Because the currency has not been set yet. Every workspace that existed before this setting started on US dollars so that nothing moved the day it shipped, and a new one is pre-set from the time zone you signed up in. A tenant admin changes it in Settings, then Workspace basics. Two things are US dollars on purpose whatever you pick: your Current subscription and its invoices, which are our price rather than your books, and the screenshots in this help center. Six of the sixteen print a plain $ inside the workspace, the five dollars and the Mexican peso, with the three-letter code on the Settings card and in your export headers, so a Canadian workspace reads $ on screen and CAD where it matters.
It still becomes a deal, and the difference is flagged rather than hidden. A quote carries the currency it was priced in, and when that is not your workspace currency the won-quote queue marks the row, the detail drawer names both currencies, and the conversion wizard repeats it on the charges step before anything reaches your PSA. Nothing is converted, so the charges your PSA receives are the same numbers the quote states. Check them against the currency your PSA bills in before you continue. A quote that carries no currency at all is not treated as a mismatch, because an unknown currency is not evidence of one.
Yes, that is what a checkpoint is: the ordered list of questions a stage asks before a deal is allowed onto it. Open Deals, choose Edit columns, and press Checkpoint on the stage you want. Each question is either one of five built-in deal numbers — Monthly recurring, Hardware / one-time, Projected close, Forecast, Contract term — or one of that pipeline's own custom fields, and you can write a new field from inside the same dialog. Fields come in eight kinds: Money, Number, Percent, Text, Date, Dropdown, Checkboxes and Yes / no, with Dropdown and Checkboxes taking the answers you allow, typed one per line. Sales Managers and admins with CRM access set checkpoints up; everyone else answers them. Deals you already have are untouched — nothing is scanned and nothing is flagged, and the questions are asked the next time somebody moves a deal. Zero counts as a real answer, so a deal with no hardware can say zero one-time and never be asked again. Won and Lost can carry a checkpoint too, and those questions appear inside the close dialog. Cancelling the editor writes nothing, so you can open a checkpoint, read it, and back out.
Because that stage has a checkpoint on it, and the deal is missing at least one of the answers it asks for. The dialog is headed "Before this moves to" and the stage's name, and it shows only what is still blank — anything the deal already carries is not asked again. Fill it in and press Save and move: the answers are written to the deal and the move completes in the same motion. Cancel, press Escape, or click the background and the card goes back where it was with nothing written, so a card you dropped by mistake costs you nothing. Only the stage you dropped on is asked, never the columns you dragged past. There is no way around it for anyone, including sales managers and workspace admins. Your sales leadership decides which stages ask what, in Deals → Edit columns → Checkpoint.
No. A checkpoint question can point at a field on the company rather than a field on the deal, and then it is asked once. The rep answers it in the same move dialog as everything else, under a line reading "Saved on the company, so every deal for it starts with this answer"; the answer lands on the company record and shows on the company page in the Your fields band, with the rest of that account's key facts. Every later deal with that company arrives already carrying it, so the checkpoint has nothing left to ask and the move goes straight through. There is one copy of the answer, so changing it on the company record changes it for every deal. Current Sales OS uses this for ICP fit — whether a business is the size, the location and the technology you serve well is true of the business rather than of one deal. Sales leadership adds these from the same Add a question menu in Deals → Edit columns → Checkpoint, where they sit under Company facts. Two things to know: a deal with no company linked yet is not asked its company questions, and if you cannot edit that company — an Account Executive reads every account but edits the ones in their own book — Current names the answers it could not save and moves the deal anyway.
Yes, per pipeline, in Deals → Edit columns → Quote automation. Two of the moves are yours to set: "When a quote is created, move the deal to" and "When a quote is sent, move the deal to", each offering that pipeline's own working columns and Off. Deals only ever move forward this way and a closed deal is left alone, so an automation can never drag a card backward or reopen finished work. Two more are built in and are not settings: a signed or won quote moves its deal to Closed Won, and a lost quote moves it to Closed Lost. A won quote still pays commission, because a quote your rep built, sent and won is a win made in Current. What each quoting tool can report differs: ScalePad Quoter sends created and sent as they happen, ConnectWise CPQ and Kaseya Quote Manager send wins, revisions and losses, and HaloPSA sends wins only — so the created and sent moves are worth wiring up where Quoter is what you quote in. Separately, one pipeline in the workspace can be marked "New quotes start deals in this pipeline", and a quote built for a company with no open deal then opens one there instead of hanging unattached.
Tick the reminder box in the dialog that records the loss. Closing a deal as Lost and disqualifying a lead both offer "Remind me about this later", with quick picks for 1 week, 1 month, 3, 6 or 12 months, or a date you choose, plus a line for anything the reminder should say. It creates a to-do on your own list called "Follow up:" and the record's name, linked to the company and to the deal or contact, and the reason you gave for the loss travels into its notes so you do not retype what you just typed. It shows on My Day, rings the in-app bell at the reminder time, and syncs into your Microsoft To Do like every other Current to-do. The box starts unticked, the loss is recorded whether or not you use it, and a reminder that could not be created tells you so rather than taking the close down with it.
Because both of those rules start switched off, and somebody has to turn them on. In Deals → Edit columns, under "How deals move", each pipeline has "Deals move one stage at a time" and "Deals can't move backward". They belong to that one pipeline, so a tightly run New Logo board and a loose Projects board can each work the way they should. Sales Managers and admins with CRM access set them; a rep sees the effect rather than the switch. Two moves are always allowed whichever way the switches are set: closing a deal as Won or Lost from wherever it is, and reopening a closed deal onto any stage — a rule that blocked an early close would only teach people to drag a card through columns it never really visited. When a rule turns a move down, the message names the rule and what to do instead, and a bulk move reports how many deals it held back for that reason.
Switch the deals board from Raw to Weighted. The two words sit in a cell marked Totals at the end of the stat strip above the board, and choosing Weighted turns every one of those numbers, plus the subtotal on each column header, into value multiplied by win probability, so a 10,000 deal at 30 percent counts as 3,000 instead of 10,000. Nothing about your deals changes and nothing new has to be filled in: the probability comes from the default on the stage a deal is sitting in, which sales leadership sets in Edit columns, and any single deal can carry its own number in the Win probability field in its drawer. It starts on Raw, it is yours alone rather than the whole team's, and Current remembers which way you left it, so the board opens the way you read it last. To look at a slice instead, the Chance menu in the toolbar filters the board to one band: Likely is 70 percent and up, Toss-up is 40 to 69, and Long shot is under 40, which is also where a deal with no probability and no stage default lands, because an unknown chance is worth planning for as the low one. That filter saves into a view with the rest of them, so "my Likely deals" is one click.
Open the menu behind your initials at the top right, choose Learn Current, and press Show me on the Take the tour step. It runs the same short guided tour you were given the first time you signed in, matched to your role, and you can take it as many times as you like. Learn Current is where your whole journey lives, and its Walkthroughs list is the longer version: do-it-with-me walkthroughs that sit beside you while you create a project, log a time entry, move a deal forward, and go on through the admin, project, sales and insight sets, each showing roughly how long it takes before you start. You only see the ones that fit your role, so a salesperson is not offered the time-entry one. The rows on the setup cards in the corner that have a walkthrough behind them, and the journey steps on Learn Current, also carry a Show me link, which starts the same thing on the page where the work happens. The screen tours are separate again: each key screen runs its own once, and the New here? card at the top of that page replays it.
Which setup steps and walkthroughs you have finished and the date each one was finished, which phase of the learning journey you are in (Day 1, Week 1, Month 1, or Knows Current with the month), and how many of the screen tours you have seen, as one figure. 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 a step, does not time you, does not rank you against your teammates, and has no leaderboard anywhere. Your own Getting started card shows you the same steps and carries a line saying plainly that your workspace admins can see which of them you have finished, so nothing about it is behind your back. The reason it exists is so an admin can spot the person who never got their PSA identity linked and go and help them, not to score the team. Two more things worth knowing: steps that do not apply to your role or to a workspace with no PSA are shown as not applicable rather than as missing, so you are never marked behind for something that was never yours to do; and nothing from a session where someone from ITPartners+ is inside your workspace helping is credited to you or to anyone else, because the database refuses that write rather than the screen hiding it. The steps Current works out from your real data are the exception: if your PSA identity gets linked while someone is helping you, that step reads as done, because it is done.
You can skip it, and it never locks anything. Skip this step is on screen for the whole walkthrough, and closing it stops the walkthrough rather than the work. A walkthrough waits for you rather than clicking through on its own, so nothing is on a timer either: it highlights what to press next and sits there until you have done it, however long that takes. The first-time-entry one is offered above the form on your very first entry only, and you can fill the form in and save it without ever pressing the offer. Skipping is not final: everything is in the Walkthroughs list in the menu behind your initials and on Learn Current, so you can come back to one weeks later when you actually need it.
Tag them as you meet them, then filter to them later. Every lead can carry a temperature — Hot, Warm, or Cold — set with one click from the lead card on the funnel or from the lead drawer, and a tagged lead shows a small flame and the word on its card so the board tells you where the heat is at a glance. When you get back, open the Temperature filter beside Assigned to, choose Hot, and you have the three conversations that were worth having out of a hundred badge scans; Untagged finds the ones nobody has judged yet. Temperature is a column on the list and it comes out in the CSV export, it saves into a view with your other filters so "my Hot leads" is a pill you click, and a website form can set it on the way in if you map one of its questions to Temperature. Leads start untagged and stay that way until somebody decides, so a funnel nobody has tagged works exactly as it does now.
Almost always because of how each side turns a contract line into a monthly figure. Current reads every recurring line on your active contracts and states it in months on its own period: a service quoted per year is divided by twelve, a quarterly one by three, and only then is anything added up. Most PSA reports normalise on the contract's billing period instead, so an annually quoted service sitting inside a monthly billed contract reads as a twelfth of its real value there and at full value here. Two other differences account for most of the rest. Current counts active recurring lines only, so a line that ended, or one your PSA has retired, drops out on the day it does rather than lingering in a period total. And one-time work, projects and time and materials are not in the number at all, because recurring means recurring; if you are comparing against something that includes them, the two were never measuring the same thing. When you want to check a single account, open its company record: the recurring revenue there is the same number this tile totals, worked out the same way, so an account that disagrees is one contract line to look at rather than a whole report to reconcile.
By whether they had any recurring revenue before. Current compares each account's recurring revenue at the two edges of the window you are looking at. An account with none at the start and some at the end is new business, and that means their first ever recurring contract, not their first contract this year. An account that had some and now has more is expansion; less is contraction; and an account whose last active recurring contract ended is churn. Because it compares the edges rather than watching events go by, a renewal behaves the way you would expect: a contract that ends while its replacement starts inside the same window is still one account, so it lands as whatever it actually changed by, or as nothing if it renewed flat. It never appears as a churn and a new sale at the same time. Accounts that came with a business you bought are the one exception, and they get their own bucket so a purchase never reads as a record month of new business. Current works out which accounts those are from a company field in your PSA that a tenant admin or sales lead points it at, so there is nothing to tag by hand. Until that field is chosen the bridge says no acquisitions are marked rather than showing an empty bar, because no acquisitions and no field configured are different facts.
Because Current only started writing your recurring revenue down each day when this shipped, and it will not invent what it did not record. From that day on there is one row per account per day, which is where the change since last month, the sparkline under the total and the bridge all come from. For a window that reaches back before then, Current rebuilds the picture from the start and end dates on your contracts, priced at today's line prices, and labels every rebuilt point on the tile face so you can see which part of the line is a record and which part is a reconstruction. A long flat stretch at the beginning of a two year chart is usually the gap rather than a flat two years. What Current will not do is price the past from seat counts. It has kept the number of seats on each service since July 2026, and it would be easy to multiply those by today's prices and call it history, but a headcount from March tells you nothing about what March was billed at, and a confident wrong number is worse than a labelled gap.
Whichever rule you pick, and Current asks you once rather than deciding for you. When you build a recurring revenue leaderboard by rep, one of the questions it asks is how to attribute a dollar, with three answers: the account manager on the company, which is the default and the best populated because your PSA syncs it; whoever won the business, meaning the owner of the won deal behind the account, falling back to the account manager where there is no won deal; or split evenly across the account's co-owners, again falling back to the account manager. Your answer is written onto the tile, printed on its face so anyone reading the board knows which rule produced it, and you can change it any time in Edit tile. Accounts that no rule can answer collect in an Unassigned row instead of being dropped, so the board still adds up to your workspace total and you can see how much of it is waiting on a missing field. Changing the rule changes the leaderboard and nothing else: the total, the bridge and retention are about the book rather than about people, so they read the same whichever rule is set. Anyone with CRM access can open these boards, the same wall that already governs won revenue by rep.
The account one. Huntress issues two kinds and they behave differently in the way that matters here. The account-level key is read-only by design: write capability was never added to it, so a connector holding one cannot isolate a host or delete an organization no matter what any code asks it to do. A user key mirrors the permissions of the person it belongs to, which means it is only as read-only as that person's role is today — promote them next quarter and the key quietly gains write access, and nothing tells Current that happened. So generate the account pair on the API Credentials page in your Huntress portal, reachable from the menu at the top right or under Account Settings. If your organization's policy pushes you to a user key anyway, make it belong to a user whose account-level role is Read-Only, and know that the role is now the thing keeping it read-only. Either way, Current's own allowlist is the belt that always holds: it names five read endpoints and nothing else, so every isolate, uninstall, delete and incident-close path is unreachable from Current's code regardless of what the credential could do.
Because two different numbers are easy to mix up, and Current keeps them apart. Huntress records a lifetime incident-report count on each organization: every report ever raised for that partner, including everything closed, dismissed, and long forgotten. On a partner Huntress has protected for a few years that figure runs into the hundreds and means the service has been working. The number that matters day to day is the open count, and it comes from the reports themselves — a report is open while its status is sent or auto-remediating, and closed, dismissed and partner-dismissed reports are not. The company alert band and the security card read the open count; the lifetime figure is shown as history where it makes sense and is never presented as something to act on. If a status ever arrives that Current does not recognise, it is counted as unknown rather than as open, so a new Huntress status can never inflate an alert on its own.
Only the headcount. Huntress's API exposes one security-awareness number — how many learners an organization has — and nothing else: no phishing simulation results, no course completions, no per-learner detail, and no campaign endpoint. Current mirrors that learner count and shows it as a sign the partner has the product, which is a real answer to what an account actually has. It cannot show you a phish-prone rate or a completion percentage from Huntress, because those numbers are not in the API to read. If awareness reporting matters to your reviews, that comes from a dedicated awareness platform: connect KnowBe4, whose reporting API does carry phishing test results and training campaign completion, and those numbers land in the People section of a company record and the security chapter of a review.
Two things: your console address and a Service User token. The address is the web address you sign in to SentinelOne at, something like https://usea1-999-yourcompany.sentinelone.net — every SentinelOne customer has their own, so there is no list to choose from. For the token, sign in at the All Customers (Global) view and go to Settings → Users → Service Users → Actions → Create New Service User. Choose Account scope, which covers every one of your partners' sites, and the Viewer role, which is read-only. Do not use a personal API token from your own user record: those expire after 30 days and stop working the moment that person leaves. SentinelOne asks how long the token should last and defaults to a year — write that date down, because the expiry cannot be changed later and a token cannot be renewed in place. Copy the token before you close the page; SentinelOne shows it once. Then paste both into Integrations → SentinelOne and press Test connection.
No. The SentinelOne connector is read-only. It reads your site roster, endpoint protection state, and the open threat list, and nothing else. Network isolation, killing or quarantining a process, disk rollback, agent uninstall, remote scripts, policy and exclusion edits, and token management are not on the connector's allowlist, so Current cannot call them at all — the connector checks every request against a list of five read addresses before sending it, and refuses anything else. That matters more here than with most integrations, because the SentinelOne API can genuinely take a machine off the network, so the guarantee is enforced in code rather than promised in documentation. The Viewer role you grant in SentinelOne is a second lock on the same door. Current also deliberately does not store file paths, file hashes, sign-in names, IP or MAC addresses, or installed software — the verdict and the count come across, the forensic detail stays in your console, and the company card links you there when you need it.
The endpoint's SentinelOne site is not mapped to that company yet. Current links sites to companies by name and links only when exactly one company matches, leaving anything ambiguous for you rather than guessing. Open Integrations → SentinelOne → Manage → Customer mapping, find the site on the Unmapped tab, and press Map — its endpoints and threats attach right away rather than waiting for the next six-hour sync, and a mapping you set by hand is never overwritten by a later automatic match. If it is not one company but all of them that are missing, check the scope of your Service User instead: a token created at Site scope sees one site and looks exactly like a small partner base. The connector maps on the site, which is SentinelOne's level for one partner — an account is usually your whole book, and a group is a slice inside a single partner, so neither would land data where you want it.
Because the role on the API user was attached to a single organization instead of being left unscoped, and nothing anywhere reports that as an error — from ThreatLocker's side the answer it gave was correct. In the ThreatLocker Portal, a role added to an API user without choosing an organization applies across your whole tree; a role added with one organization picked applies to exactly that one. The connector then syncs perfectly, the card goes green, and it covers one partner. Current watches for this: when a sync finds a single organization, the card names it and tells you what to change. The fix is in the Portal under Manage, then Users, then API Users — remove the role from the API user and add it back with the organization selector left empty, then press Sync now on the card in Current. The other thing worth checking while you are there is that the role really is view-only: View Computers, View Organizations and View Unified Audit, and nothing that edits or installs anything.
Because blank and zero are different answers and Current will not print one for the other. Blank means Current was not able to ask: either the API user's role is missing the View Unified Audit permission, or the daily read has not run yet on a freshly connected workspace. Zero means Current did ask and ThreatLocker's answer was that nothing was blocked in that window — which is a real state, and on a well-tuned allowlist it is a good one. A card that showed zero when nobody had asked would be telling you your Zero Trust product caught nothing when in fact it was never queried, and that is the kind of number that falls apart in front of a partner. The card names which of the two you are looking at, and if the permission is the reason it says so and tells you what to add. One thing worth knowing: the per-machine three-day denial count that ThreatLocker puts on each endpoint does not need that permission at all, so even a workspace that cannot grant Unified Audit access still has a blocked-executions story to tell.
No, and that is deliberate. Current stores how much was blocked, not what was blocked. Each denial record in ThreatLocker names the file path, the process and the user who was at the keyboard, which is end-user detail that has no business sitting in a company record where an account manager, an account executive and anyone else with access to that company can read it. It is also enormous: a busy workspace produces those records by the million every day, and mirroring them would flood the vendor's API and Current's database to no purpose. So Current asks ThreatLocker for the total and stores the number — how much was blocked in the last day and the last week, and how much of that was ringfencing specifically, per partner. That is what a business review is built from: your endpoint protection blocked this many unauthorised executions this quarter, and we cover this share of your machines. When somebody needs to know what a specific block was, that investigation belongs in the ThreatLocker portal, where the full record lives and where the person looking at it is doing so deliberately.
In the AutoElevate portal at msp.autoelevate.com, signed in as an Administrator. Add a user first: Users, then + at the top of the grid, type Service, a name such as Current integration, Role Read Only, Company Access All, and Save. Open that user, find the API Keys card and press +. In the New API Key dialog, name the key, keep the Scheme on Bearer, set Expires to 1 year, and set Scope to Full access, then press Add. AutoElevate shows the token once, starting aeb_, so copy it before you press I've saved this. Paste it into the API token box on the AutoElevate card in Integrations and press Test connection. The read-only part comes from the role rather than the key: a key can never do more than its user's role allows, and the Read Only role has no permission to approve, deny or change anything. That is why Full access on that user is safe, and why the user must stay on Read Only, because raising the role raises the key with it. Full access is also the only scope that can reach rules and elevated sessions. AutoElevate lists rules among the Read Only role's permissions but doesn't name elevated sessions, so the key may still be refused sessions; if it is, everything else syncs and the company card leaves the sessions section out rather than showing zero. A Limited key with Read companies, Read computers, Read locations and Read elevation requests ticked also works, but AutoElevate can't grant the rules and elevated-sessions permissions one at a time, so those two stay unread. Never tick Write elevation requests or Write computers.
It means a company has computers where AutoElevate is not controlling admin rights, and has not been for a while. A computer counts once it has spent 30 days or more in audit mode, or a day or more in technician bypass. Audit is the mode AutoElevate starts in after install, and CyberFOX recommends 30 to 60 days of it while you learn what a company's users need, so 30 days is the point where that onboarding window has had its chance. Technician bypass times out after 15 minutes by default, so a computer still in it a day later is worth a look. The entry is a warning, and it turns critical when any of the computers is in technician bypass. It clears when the machine moves to Live or Policy, or leaves Current after dropping off AutoElevate's list (two complete reads without it), and every open one clears the moment AutoElevate is disconnected. Reconnecting doesn't reopen a cleared entry; if computers are still past the threshold, the next complete sync opens a new one. The days are measured from when Current first saw the computer in that mode, because AutoElevate doesn't publish when a mode changed, so the alert can't fire in the first 30 days after you connect (the first day, for technician bypass). A computer whose mode Current doesn't recognise never counts toward it.
No. AutoElevate's API can approve or deny a request, and approving or denying one can also create a permanent rule for a computer, a location, a company or your whole account. Current calls neither. Every request it makes is a read, checked before it is sent against a list of six exact addresses (companies, locations, computers, elevation requests, rules and elevated sessions), and the list is matched exactly rather than by prefix. That matters here because approve and deny sit under the same elevation-requests address as the read Current makes, so a prefix match would let them through. The part of the connector that sends requests can't send anything but a read, and the Read Only role on the key's user is a second lock: AutoElevate itself would refuse an approval from that key. Changing a computer's mode and editing a rule aren't in the connector's code either.
Because a business review needs to say what a company's users needed elevated and how it was handled, and it doesn't need to say which person asked. A company record is read by account managers, account executives and anyone else with access to that company. So Current keeps what was requested, its state and when. It never reads the field naming the person who asked or the note a technician typed when denying a request, and never stores the person on an elevated session. The request text is AutoElevate's own description, such as Install Foo.exe, and it can carry a name, so Current cleans it before storing it. It turns encoded characters back into plain ones first, so an encoded path is cleaned like a plain one. Then the whole folder name after a profile folder (Users, Users$, home, home$, Profiles, Profiles$, Documents and Settings or RedirectedFolders, on any drive and inside a network path) is replaced, so C:\Users\jsmith\ becomes C:\Users\…\; email addresses become [email]; DOMAIN\user and user@DOMAIN sign-in names become [account], including one written after a switch such as /user: and one in accented or non-Latin letters; and the text is cut at 160 characters. A name typed into the description as plain words, such as "for John Smith", matches none of those patterns, so Current cannot recognise it and stores it as written. Machine names are stored, because a technician needs to know which computer to look at, so a hostname that contains a person's name will show on the card. When you need to know who asked, that record is in the AutoElevate portal. As of September 2026, AutoElevate's API sends the description empty on every request, so the card shows "No description recorded" and the most-requested lists stay hidden until AutoElevate fills it in.
In your Veeam Service Provider Console: Configuration (top right) ▸ Access Management ▸ REST API Keys ▸ New ▸ Simple Key. Give it a description, switch Read-only access ON, save, and copy the key — the console shows it once. Mint it against a service account with the Portal Readonly Operator role rather than against a person: a VSPC key never expires on its own, so it stays valid until the user behind it is disabled or deleted, and a key created by someone who later leaves stops working the day their account is disabled. Use a provider-level account, because a key minted against a company-scoped user can only see that one company and looks like a broken sync. Paste the key and your console address, including the port, into Integrations → Veeam Service Provider Console and press Test connection: Current makes one read and stores the key server-side only.
Because the console is yours, not Veeam's — it runs on your infrastructure, so Current has to reach it across the internet. Three things stop that, and none of them is the key. The console may not be published to the internet at all, in which case publish it or allowlist Current's egress. The API port may differ from the one you sign in on: 1280 is the documented default for both, but the API port can be set separately at install time and 1281 is a common alternative, so try the other one. Or the console may present a self-signed or private-authority certificate, which Current will not accept — there is no option to skip certificate checks to reach a backup console, so install a publicly trusted certificate. Current's message names which of these it hit rather than telling you to regenerate a key that was fine.
No. The Veeam API is a full management interface for a backup estate — it can create and delete customers, suspend a customer's access to their own backups, start and stop jobs, restart agents, install software, reboot machines, resolve alarms, send invoices, and mint further API keys. Current calls none of it. The connector holds a list of exactly ten read addresses and every request is checked against that list before it is sent, so every one of those actions is unreachable rather than merely unused — a bug in Current cannot reach them either. Veeam can also issue the key itself as read-only, and the setup steps ask you to. An alarm clears in Current because it cleared in Veeam.
In x360Portal: sign in at partner.axcient.com as an administrator, then Settings ▸ API Keys ▸ Add API Key, fill in the details, and press Generate API Key. Copy it when it appears. One detail matters more than it looks: a key carries the product permissions of the administrator who created it, so make it from an admin who can actually see x360Recover — a key made by one who cannot will sign in perfectly and then read nothing, which shows up as a connection that tests fine and reports zero partners. It is also worth using a service-style admin account rather than a person's, because every administrator in your organization can see and delete every key, including ones somebody else made. Paste the key into Integrations → Axcient in Current and press Test connection: Current sends it as a header, reads back the Axcient organization it belongs to, and shows you that organization's name so you can confirm it is the right tenant before anything is stored. There is no region to pick and no second field — Axcient runs one global service and one key covers every partner you back up.
Because both tools are watching the same backups and counting them their own way, so they were never meant to agree. Some backup-monitoring products read Axcient directly, which means a workspace with both connected has the same machines mirrored twice — once as Axcient protected systems and once as monitored backup jobs. Neither figure is a total of the other, and one machine running several jobs shows up once on the Axcient side and several times on the monitoring side. That is why the two sit on separate cards on a company record, each naming where it came from, instead of being added together: there is no shared machine identifier between them that would let Current merge them reliably, and merging them on matching names would be guesswork. Read each card as its own view of the same fleet.
A protected system counts as failing when Axcient's own health verdict reads Troubled or Unprotected, or its most recent restore point is more than three days old, or its last boot-verification run failed and that run is itself more than three days old. Warned is a caution rather than a miss and does not count on its own. Parked does not count either: it is Axcient's word for a partner you have deliberately suspended, and a paused backup is a decision rather than a fault — Current treats it exactly as it treats a paused backup from any other product. Two more gaps are deliberately left as unknown rather than filled in. A system with no boot-verification record is not counted as failed, because that feature is optional and its absence says nothing about whether the machine would boot. And a health word Current does not recognize counts as unknown rather than as a pass or a failure, so a new Axcient status can never quietly turn into a green number. The restore point itself is read as the most recent of the three Axcient tracks — local, vault and cloud — because which of them exists depends on how the system is protected: a Direct-to-Cloud machine has no local restore point at all.
In the Slide Console. A Slide API token carries the role of the user who creates it, so first add a user with the Read Only role for Current (or use one you already have), sign in as that user, open My Settings then API, and create the token there. That caps it at Slide's end as well as at Current's. Copy it as it appears and keep it somewhere safe, and give it a name a colleague will recognise later, something like Current reporting. Then paste it into Integrations, Slide in Current and press Test connection: Current sends it as an Authorization header, reads your account once to prove it and your client list once to see what it can reach, and stores it on its servers only. There is no region to pick and no second field. Slide runs a single service, and one Slide account covers every customer you back up, with each customer as a client inside it, so this is one token for the whole estate rather than one each. If the test succeeds but reports no clients, the clients have not been created in Slide yet, and until they are, every box and protected system arrives unfiled and maps to nobody.
Because the two tools are counting different things about the same machines. Slide counts protected systems, which is machines. A backup-monitoring product counts backup jobs, and one server can carry several jobs, so a single machine that runs a system backup and a database backup shows up once on the Slide side and twice on the monitoring side. Neither figure is a total of the other. Some monitoring products also watch Slide directly, which means a workspace with both connected has the same estate mirrored twice from two angles. That is why the two sit on separate cards on a company record, each naming where it came from, rather than being added together: there is no shared machine identifier between them that would let Current merge them reliably, and merging on matching names would be guesswork. Read each card as its own view of the same fleet.
No. Slide's API is a full management interface for a backup estate, and Current calls none of that half of it. Creating a file restore, exporting an image, booting a virtual machine, deleting a snapshot, pausing or resuming a backup, editing a schedule or a retention policy, rebooting or powering off a box, and changing a network or VLAN are all absent from the connector's code. Every request is checked against a fixed list of read addresses before it is sent, and the list is matched exactly rather than by prefix, which matters here because Slide's writes sit at addresses that begin the same way its reads do: the address that lists protected systems is one character from the one that edits a system, and the address that lists virtual machines creates one when it is asked differently. Matching exactly makes those unreachable rather than merely unused, including by a bug in Current. Two of Slide's own reads are excluded on purpose as well: the file search inside a protected system, and the browse view of a live restore. Both would let Current look at a customer's own documents, which is not something a CRM should ever do. Your billing with Slide, the people in your Slide account, and the audit log are never read either.
A protected system counts as failing when its last good backup is more than three days old, or its most recent attempt failed, or its last boot verification came back with a warning or an error, or Slide itself has an open alert saying the system's backup failed or that it is not backing up. One definition drives the company card, the backups-failing alert and the dashboard tile, so the three can never disagree. Paused systems are left out because pausing is a decision somebody made, and Current treats it the way it treats a paused backup from any other product; the count of paused systems is shown on its own line so it stays visible without being called a fault. Sealed systems are left out for a different reason worth knowing: sealed means the encryption key is unloaded, so no backup can run at all until somebody loads it again. That is a real problem, but it is a different problem from a backup that tried and failed, so it gets its own count rather than being folded in. Three more gaps stay unknown rather than being filled in: a boot check that was skipped, is pending or never ran is unchecked and sits outside both halves of the verified figure, with the card printing how many answered; a canceled backup is neither a success nor a failure, because a run somebody stopped has no outcome; and a status Current does not recognise counts as unknown rather than quietly becoming a green number.
No — one key covers every console your UniFi account can see. Ubiquiti's Site Manager service is account-wide, so you create a single key at unifi.ui.com under Settings → API Keys, paste it into the UniFi card in Current once, and every console that account reaches shows up on the first sync. There is no region to pick and no per-site credential. The thing to check is which UniFi account you create the key on. A key made on one technician's personal account reads only the consoles that person owns, and a site still running a self-hosted UniFi Network application rather than a cloud-adopted console never appears at all. Neither of those shows up as an error — the estate just looks smaller and perfectly healthy — so after the first sync, compare the console count Current reports against the number of locations you actually manage. If it is short, the fix is the account the key belongs to, not the key itself. And copy the key when you create it: UniFi shows it once and never again.
Because the UniFi account behind the key is an admin on that console rather than its owner or a super admin, and UniFi only returns a device list to the latter. It is a permission gap, not an empty network. Current recognises the shape — a console whose sites report devices while the device list comes back with none — and labels it on the card as devices not visible to the connected account, rather than printing a zero. A zero there would misstate that partner's estate, and it is the kind of number that ends up in a business review. To fix it, raise that UniFi account's role on the console to owner or super admin at unifi.ui.com, then press Sync now. If the console genuinely has no devices, Current leaves the count blank rather than green: unknown and zero are different answers, and only one of them is safe to show a partner.
No, and it is built so that it cannot. Every request Current makes to UniFi runs through a read-only guard listing exactly four endpoints: the console list, the site list, the device list, and the circuit metrics. Anything not on that list is refused before the request is sent, so a code change cannot quietly widen it. That matters more here than with most feeds, because UniFi publishes one route — its connector passthrough — that reaches straight into a console's own management interface, where adopting or restarting a device, shutting a switch port, blocking a client, reordering firewall rules and changing an SSID all live. That route is absent from Current's list and no part of the connector can build its address. Ubiquiti's own API keys are read-only today as well, which helps, but Ubiquiti has said write endpoints are coming and that write access can be switched on for an existing key. The guard in Current does not depend on that setting, which is the point of having it.
Two things, and the first one matters more than it looks. In Meraki, sign in as a read-only administrator and go to Organization → Configure → API & Webhooks → API keys and access, then press Generate API key. Making the key from a read-only administrator means Meraki itself refuses every write, because Meraki's rule is that a read-only administrator can only make GET requests — worth doing, given the same API can reboot devices, cycle switch ports, and delete an organization. Meraki shows the key once, so copy it before you close the page, and note that each person can hold only two keys at a time: if the Generate button is greyed out, that administrator already has two. The second thing is your Meraki cloud. Meraki runs five separate ones — Global, Canada, China, India, and US Government — and a key only works against the one your organizations live on. Pick it on the Meraki card to match the address you sign in at, paste the key, and press Test connection.
No. The Meraki connector is read-only. It reads your organizations, their networks, the device list with each device's status, WAN uplink state on MX, MG, and Z-series devices, and licence posture, and nothing else. Meraki's API can reboot a device, power-cycle a switch port, move licences between organizations, create administrators, and delete an entire organization — none of those paths are in the connector's code, so Current cannot call them even by accident. Generating the key from a read-only Meraki administrator adds a second layer on Meraki's own side. There is no setting anywhere in Current that turns Meraki writing on.
Both are Current declining to invent a number. Meraki reports WAN uplinks only for MX, MG, and Z-series devices, so a site built entirely from switches and access points has no uplink to report — that is correct rather than a fault, and Current leaves it blank instead of claiming the site is up. Licences work the same way: Meraki answers that question differently depending on which licensing model an organization runs. A co-termination organization gets one expiry date covering everything and no expiring counts at all; a per-device organization gets the counts, with the thresholds Meraki itself used, and no single date; an organization on the newer subscription model is not mirrored yet. Rather than printing a zero from the half Meraki did not answer — which would read as nothing is expiring on an organization Current never asked — the card says the figure was not reported.
Three values from one downloaded file. In FortiCloud, sign in at support.fortinet.com/iam, create a permission profile granting read access to Asset Management, then go to Users → Add New → API User, pick that profile, and choose Download Credentials on the success screen. The file holds the API key (you paste it as the username), the password, and the client IDs the user may use — assetmanagement is the one that reaches asset data. Paste all three on the Fortinet card and press Test connection. One warning worth reading twice: pressing Download Credentials again resets that user's password every single time, so re-downloading the file to check a value will break a connection that was working.
Because every asset is registered to one FortiCloud account with no folders, which is a common setup. Fortinet publishes no endpoint that lists your partners — its multi-tenancy is account- and folder-shaped — so Current works the roster out from the assets themselves: an asset folder when Fortinet returns one, otherwise the account, otherwise a single bucket holding everything. One row means one grouping was found, not that assets are missing; the card shows the asset count beside it. To split them per partner, organize assets into asset folders in FortiCloud (Fortinet recommends folders and organizational units over the older asset groups), and the next sync lists each folder as its own row.
No. Two Fortinet endpoints exist in the connector's code: the sign-in call that mints a short-lived token, and the asset search. Registering a serial, consuming a licence code, downloading licence keys, editing an asset's description or address, managing folders, and decommissioning a unit are all absent from the connector, so they cannot be reached even by a bug. The paths are matched exactly rather than by prefix, which matters because the asset search sits under the same prefix as the register and decommission calls. Fortinet issues one token scope covering both reading and writing, so keep the API user's permission profile to read access on Asset Management — that is the second layer, on Fortinet's side.
Because KnowBe4's Reporting API is built around one console at a time. A token is created inside a specific partner's KnowBe4 account, every endpoint it reaches is unqualified — there is no account parameter anywhere in it — and the account endpoint returns exactly one account. There is no vendor-level key that reads all your partners at once, so Current's KnowBe4 card takes a list instead of a single credential: one row per partner, each with a name you choose, the region that partner signs in at, and their own Reporting API token. Add up to 25. A partner with no row sends no data, and Test connection checks every row and tells you which ones answered, so a single missing token does not stop the rest from syncing. Get each token in that partner's console under Account Settings, Account Integrations, API, where you tick Enable Reporting API Access and then Create New API Token — and copy it before you close the box, because KnowBe4 shows it once.
No, and it cannot. KnowBe4's API does offer that — there is an endpoint that lists the named recipients of a test with who clicked, and another that returns a full employee directory with email addresses, job titles, phone numbers and a per-person score for how often that individual falls for a simulated phish. Neither is on the connector's list of permitted reads, so neither is reachable, and a code bug cannot reach them either. What Current stores is the counts KnowBe4 already puts on the test itself: how many were sent, delivered, opened, clicked, replied, entered credentials, enabled a macro, and reported it. Those answer the question an account manager actually asks — is this partner's staff getting better — without a name attached. The training figures work the same way: Current reads the per-person enrollment rows to count how many are past due and discards every one of them, so no employee record is written anywhere. Adding per-person data later would be a privacy decision with a review attached, not a setting.
Because nothing has been measured yet, and 0% would read as a perfect result. A dash means that account has no completed phishing test that reported a rate — either the partner has not run one, or the results have not synced yet. The same rule runs through the whole feed: a training campaign KnowBe4 will not calculate a percentage for shows as still calculating rather than 0% complete, and if the daily training roll-up does not finish, all four enrollment counts stay blank together rather than showing a partial number, because three people overdue reads as a small problem when the real figure is three hundred. When a rate does appear, it is from the most recently started completed test, not an average across tests — an average of a 500-person test and a 6-person one produces a number that matches nothing in the partner's own KnowBe4 console, which is a bad thing to be holding in a meeting. The delivered count is shown beside it so the rate always has its denominator.
Less than you might expect, and the list is short enough to read. For each person Current keeps their Duo username, the display name Duo holds, their email address, their Duo account status, whether they are enrolled in multi-factor, when they last signed in, and how many phones, hardware tokens and security keys they carry as counts. That is the whole set. It does not store phone numbers, date of birth, first or last name separately from the display name, aliases, notes, custom attributes, or anything at all about a password. Their enrolled devices are stored as devices — platform, model, operating system version, and the screen lock, encryption and tamper state Duo reports — with no phone number attached. Sign-in activity is counted per day and nothing else survives: not the IP address a person signed in from, not the city or country, and not which application they signed in to. Those last three are on every event Duo returns and Current reads past them, because a daily count answers the question a business review asks and a location history does not. Everything Duo does mirror sits behind the same wall as the rest of a company record: partner viewers cannot reach it, and that is enforced at the database rather than by hiding it in the interface.
Almost always, they are in bypass. Bypass is a Duo status that lets a person sign in with their password alone, and it exists for good reasons — somebody breaking a phone the morning of a board meeting, an account being migrated — but the account keeps looking completely normal afterwards, so bypass tends to be granted once and never taken away. Current counts anyone in bypass as at risk for exactly that reason, and it is usually the most useful thing this connector surfaces. The other three cases are disabled, locked out, and never enrolled. All four mean the same thing to somebody with a stolen password: no second factor. One more case is worth knowing about. If Duo reports a status Current does not recognise, that person is counted as unknown rather than as fine, and the raw status is kept so it can be classified later. Silence and an unfamiliar word both read as we do not know, never as no problem, because a coverage number that quietly rounds unknowns down to healthy is a number that falls apart the first time a partner asks which people it covered.
No, and there are two independent reasons rather than one. The first is the credential itself. The Help article asks you to tick exactly three read permissions on the Duo Admin API application and leave every write permission off, which means the key you hand Current has no write capability to use. That is the stronger of the two guarantees, because it holds regardless of what any code does. The second is Current's own code. The connector names five read endpoints and calls nothing else, so every management endpoint the Duo Admin API exposes is unreachable rather than merely unused: it cannot create or delete a person, send one to the trash, enrol or remove an authenticator, create an administrator, change account policy, or create or delete a customer subaccount. Issuing a bypass code is the one worth naming on its own, since it is the endpoint that would matter most: Current can read that somebody is in bypass and can never put them there. One read is excluded too — the endpoint that returns another Duo application's secret key. It is technically a read, which is precisely why the connector works from a list of exact allowed paths rather than a rule that says reads are safe.
No — it is right for what had arrived by then, which is why the tile still draws it. That line appears on every tile fed by your PSA when the connection has delivered nothing for six hours or more, and it states the measured age rather than a promised cadence: hours up to two days, days after that. A connector can read connected in Settings and still be well behind, and this is the only place that shows on the number itself. It is pinned, so it also reaches a wall screen, where nobody is there to open a caret. It clears itself the moment a sync lands.
Because a zero out of a period Current holds nothing for is a claim about a quiet quarter made from history nobody has. Ticket tiles are measured against the oldest ticket in your PSA mirror; a timeframe that ends before that date is refused, with the date on the tile so you know where to move it to. A timeframe that starts earlier and ends inside your history still draws, with a line saying the earlier stretch is empty rather than quiet. Reactive hours per endpoint, effective hourly rate and managed services margin have their own start date — the oldest logged hour, which usually begins the day the connection was switched on rather than the day your tickets do — and say so by name, because otherwise a period before it would read as zero hours, a hundred percent margin and an infinite hourly rate.
Before a board draws, Current works out which of your systems can actually feed each number. That check is one read, and if it is slow or fails, the tiles draw anyway and each says it was drawn without it. It is a statement about the check, not about your data: the figures on screen are the same figures, and nothing has been held back. The read retries on its own, backing off as it goes so it never floods, and the line disappears the moment the check lands. It never appears over a check that has already answered, including one answered a few minutes ago and still in hand.
The screen tells you. A TV link asks Current for fresh numbers about once a minute; after a few of those in a row come back with nothing, or after five minutes with no successful refresh, a wide banner appears across the top of the wall saying what time the numbers on screen are from and that Current has not been able to refresh the screen. The time is in your workspace's own time zone rather than the TV's, because a media player's clock is often hours out or set to UTC. The board underneath stays and dims instead of going blank, since numbers labelled as old are more use to a room than an empty wall, and the banner disappears by itself the moment a refresh gets through. There is a second place to check without walking to the screen: the TV links panel on the dashboard tells you when that link was last opened and how many tiles it last drew.
Almost. Two things read differently on a wall, both on purpose. A TV shows no comparisons against the previous period and no movement arrows on leaderboard rows, so the same board is a little plainer there than on a desk. And a workspace running several screens shares a small queue: if three TVs happen to refresh at the same moment, a fourth waits about half a minute and takes its turn inside the same minute, with nothing on that screen changing while it waits. Everything else matches, including which tiles a TV link is allowed to show, which is decided tile by tile and described in the dashboards article.
Yes. On the Booking page, each question has a Choices button. List the answers one per line (up to twelve, each up to 80 characters) and the booking page shows a dropdown for that question. The booking is refused if the answer is not one of the choices, which is what makes the answers countable later. Clear the list and the question goes back to free text. Choices work well for a question like "How did you hear about us?", where a fixed set of answers is more useful than a paragraph.
It is one required dropdown on the create-workspace form, answered once by the person who creates the workspace and never asked of invited teammates. A referral or "somewhere else" opens an optional box for a name or a place. The answer is stored beside the workspace so ITPartners+ can see which channels bring in workspaces that stay; it is never shown to other workspaces and never sold or shared.