Managing a connection
A connection's tabs, primary and summed sources, Sync Now, pausing, editing a key, Disconnect vs delete, Slack and Teams alerts, and calendars.
Answered from these docs only, by a model that cannot see your account. Check the pages it cites.
Checked against the product on November 9, 2026
Once a platform is connected, everything about it lives on the connection's own page: open Integrations in the sidebar and click the connection. Anyone on the account can open it. Only Owners and Admins can sync, pause, edit, reconnect, disconnect or delete a connection, or change which one an account reads from. Any member can link it to initiatives, change how it's linked and unlink it.
The connection's tabs
- Connection — Connection Details (status, account, sync schedule, when it last synced, and any error), the Connection Check, and Metric Categories, which says where each category this connection can supply reads from
- Initiatives — the initiatives it's linked to, and the role and mappings for each. See Linking connections to initiatives.
- Customers — Stripe only, for Owners and Admins: which initiative each customer's payments count toward
- Spend — for connections with a bill (Anthropic, Claude Enterprise, OpenAI, GitHub, AWS, Azure, Google Cloud, Snowflake, Databricks, QuickBooks, Xero and American Express): what the provider billed over the reporting period. QuickBooks and Xero list the bills behind the total; the others list the monthly totals.
- Metric Queries — Snowflake, Databricks, BigQuery and SQL Server: your own queries, each feeding one metric from your warehouse, with every version of its SQL and what each returned. See Metrics from your own data warehouse.
- Metric Entries — the readings the connection has brought in
- Sync History — every sync run, with its records and any error
- Synced Records — Owners and Admins only: the platform's own rows as they arrived
- Platform — the platform's page: what it captures, and Add Another Connection for a second account. How to Connect, the platform's steps, is on the connect form.
Primary sources and summed sources
Roiva's shared metrics, such as deals won, support tickets opened or cloud spend, each read from one connection per category: its primary source. The first connection that can serve a category becomes its primary, with two exceptions below: AI assistants and Coding assistants.
Organization Settings → Metric Sources, which Owners and Admins open, lists every category, the Metrics it feeds, the connection it Reads from and the others that could also serve it. Pick another connection under Change and click Set. Changing the primary re-points every formula, page and chart and rewrites nothing, and every connection keeps syncing under its own keys either way. The same choice is on a connection's own page, under Metric Categories: Read from this one.
When a connection becomes the AI assistants source. Each of these becomes the source only once its sync finds something to read, and none is offered for it before then:
- Microsoft 365 Copilot: a Copilot license
- ChatGPT Enterprise: a ChatGPT seat
- Claude Enterprise: seats assigned
- Gemini in Google Workspace: someone who used Gemini in the last 30 days
- Glean: someone who used Glean's Assistant, counted in the latest month its sync reads (in a month's first week, the month before counts too)
- AWS: Amazon Quick seats
Each becomes the source only while no other connection holds it, a disconnected one included, and nobody has chosen the source themselves.
Keeping the AI assistants source. Roiva never moves AI assistants from one connection to another on its own, whatever each one reads: the first to find seats or users keeps the category, even once its licenses lapse, until someone chooses another. When you connect an assistant while another connected connection holds AI assistants, the notice says so.
A disconnected connection keeps the category so that reconnecting it takes it back, and until then no other connection becomes the source on its own. Choosing another source, or none, in Metric Sources takes the category from a disconnected connection too, and reconnecting it doesn't take it back.
When Roiva asks you to choose. Roiva tells you when the source reads nothing and another connection has seats or users to read, in two cases:
- A Microsoft 365 Copilot, Claude Enterprise, Gemini in Google Workspace or Glean connection holding AI assistants has read nothing for over a week (its tenant's Copilot licenses lapsed, its organization with no seat assigned, nobody in its Workspace has used Gemini in the last 30 days, or nobody has used Glean's Assistant this month).
- A disconnected connection still holds it.
Another connection only counts while it still syncs: a paused one isn't offered. Owners and Admins see either case in the Inbox, and Metric Sources says so on the AI assistants row; choose the source there, or reconnect the disconnected one.
Coding assistants. A ChatGPT Enterprise connection becomes their source only once its sync reads a day someone used Codex, since a workspace may use ChatGPT and not Codex, and on the same terms: only while no other connection holds them, a disconnected one included, and nobody has chosen their source themselves. It isn't offered for coding assistants before it has read a Codex day. When a disconnected connection still holds coding assistants and another has something to read for them, Roiva tells you the same way.
Summed sources. Cloud cost, AI cost and Workflow automation work differently, because each source is a separate bill or run log: an AWS account and a Google Cloud project don't report the same spend. When a second source for one of these connects, Roiva reads the category as All connected sources, summed, marked Combined. If someone has already set how the account reads that category, their choice stays. Other categories, such as CRM deals or Support tickets, can be summed from the same picker where Roiva can add them up, but never automatically: two CRMs often hold the same deals. Coding assistants can't be summed at all.
An initiative can read a category from a different connection, or add it up across the connections linked to it, on its own Measurement → Connections tab. Adding up there counts only that initiative's linked connections, never the account's others. If none of its linked connections serves the category any more (each one is unlinked or disconnected), the initiative reads the account's choice until one does again, and Metric Sources stops listing it. Metric Sources lists the exceptions in force under each category.
Syncing
Connections sync nightly at 2:00 AM UTC. Slack and Zapier are the exceptions: Slack only posts alerts, and Zapier sends data to Roiva as your Zaps run. Sync Now at the top of the connection's page runs a full sync straight away. Progress shows on Sync History. When the platform has revoked Roiva's access, Reconnect takes Sync Now's place, and Sync Now moves to the … menu.
Pause Sync, in the … menu, stops the nightly sync, and the connection shows Paused until someone chooses Resume Sync. Nothing it already synced changes. A paused Zapier connection refuses the runs your Zaps post, so their webhook step fails until it's resumed, and those runs aren't recorded.
Editing a connection
Choose Edit in the … menu to rename the connection, add a description, or change the platform's settings. For a platform that takes an API key, the API Key / Secret field is left blank: leave it blank to keep the current key, or paste a new one to replace it. Saving a new key starts a sync with it straight away, unless the connection is paused. To try the key the connection already holds, choose Reconnect in the … menu instead: it runs the Connection Check, and starts a sync only if the key works. Sign-in platforms don't have a key here; Reconnect takes you through the platform's approval again (see Why is my integration not syncing?).
Disconnect or delete
Disconnect, at the bottom of the … menu, stops syncing immediately. For Google Workspace, Jira, QuickBooks, Slack, Xero and Zendesk it also asks the platform to revoke Roiva's access, and so does Delete Connection. For Zendesk that's a connection that signed in to Zendesk; one that uses an API token is left as it is, so delete the token in Zendesk's Admin Center. For any other platform, remove Roiva in that platform's own settings as well. Jira is asked but unconfirmed: Atlassian doesn't say whether a grant was there to end, so remove Roiva in your Atlassian app settings too if you need to be sure. Microsoft 365 can't be revoked for you: where an admin approved Roiva for your whole organization, only a Microsoft Entra admin can remove it.
The connection moves to Disconnected, folded under its count at the bottom of the Connections page, and no longer counts toward your plan's connection limit, but it isn't deleted: everything it synced and booked stays. A connection nothing ever came in through (never synced, no data, no costs or value booked from it, no readings, no initiative linked to it, no support ticket about it) is deleted instead, since there's nothing to keep, and the confirmation says so before you choose. Slack and Teams channels are always kept.
Disconnecting a Google Cloud, BigQuery or Gemini Code Assist connection deletes the Google service account Roiva created for it, which ends Roiva's access whatever your IAM still grants. Reconnect creates a new one under the same email: grant it the roles again, since Google doesn't carry grants over to a new account.
For a sign-in platform, connecting the same platform account again usually brings that connection back, active. Disconnecting a Zapier connection retires its ingest URL for good: Reconnect issues a new one, shown once, to paste into each Zap.
Delete Connection, under Danger Zone at the bottom of the Edit Connection page, or in the … menu once the connection is disconnected, removes the connection permanently:
- The cost entries, value entries and metric entries it recorded stay on your initiatives.
- Its place on the initiatives it's linked to, its sync history and its synced records go. A bill an allocation rule split stays, because the allocation reads from it.
- If you later connect the same platform account again, and Roiva can tell it's the same account, the new connection takes back what the deleted one left behind, so its history isn't booked a second time.
Deleting is refused while Roiva posts cost-allocation journals for the connection's bills: locking an accounting period posts them through the connection, and reopening one reverses them the same way. Disconnect it instead, and reconnect it if a period needs reopening. See Allocation rules and accounting periods.
What Roiva keeps from each platform lists, platform by platform, what a connection syncs and which fields of each record it keeps.
Slack and Microsoft Teams channel posts
A Slack connection posts to one channel, picked in Roiva. Open the connection, and under Channel choose Find channels and pick one; you can change it whenever you like. Every public channel in the workspace is offered. A private one appears once you type /invite @Roiva in it, because Slack does not tell Roiva about a private channel it isn't in.
One Slack workspace can hold several connections, each posting to its own channel with its own posts ticked — so the channel finance reads need not be the one IT reads. Connect Slack again to add one. Organization Settings → Chat Channels shows every channel's posts side by side, and warns when no channel carries a kind of work.
For Teams, set up a workflow in the Teams channel that sends webhook alerts, then paste its URL into the Webhook URL field of your Microsoft 365 connection. Teams does not tell Roiva which channel a workflow posts to, so name the connection after the channel.
Either one can post:
- Stage changes — an initiative submitted for review, approved, live, completed and so on
- Value entries — submitted for review, approved or disputed
- Notes — Decision, Blocker and Update notes. General notes and replies are never sent.
- Budgets — a budget set or revised, and a budget increase sent to the Owners for approval, approved or rejected. See Budgets and budget vs. actual.
A new connection sends all of them. To send fewer, Edit the connection and untick them under What to post. A connection whose posts were chosen before Budgets existed keeps sending just those: tick Budgets to add it. Untick everything to keep the connection without sending anything. Only an active connection posts, so a paused one is quiet.
A connection can also post the account's Inbox to its channel on a schedule. It's off until you set how often under Post the Inbox to this channel on the connection's Edit page, with what's worth sending beside it. Which parts of the Inbox sends some kinds of row to this channel and others elsewhere, and says which kinds no channel posts.
Send Test Message in the … menu posts one message to the channel, so you can watch it arrive. On Microsoft 365 it shows once a webhook URL is saved.
Choosing calendars (Google Workspace and Microsoft 365)
A Google Workspace or Microsoft 365 connection counts meetings across the calendars you pick in its Calendars section. Until Roiva has listed them, it reads the connected person's own calendar only. Choose Find calendars to list the calendars that person can already open, such as their own, their team's or a room's, then tick the ones to count and choose Save calendars. A meeting on more than one of them counts once. The next sync measures what's picked, and earlier months are measured again from those calendars. Find calendars again refreshes the list.
Members see how many calendars the connection syncs; an Owner or Admin changes them.
Next
- Connecting your first integration — connecting another platform
- Why is my integration not syncing? — errors, Reconnect and the Connection Check