# 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. > > Source: https://roiva-staging.com/docs/managing-a-connection > Checked against the product on September 22, 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 those links and remove them. #### The connection's tabs - **Connection** — **Connection Details** (status, account, sync schedule, when it last synced, and any error), the **Setup Check**, and which metric categories this connection is the source for - **Initiatives** — the initiatives it's linked to, and the link each one has. See [Linking connections to initiatives](https://roiva-staging.com/docs/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, OpenAI, GitHub, AWS, Azure, Google Cloud, Snowflake, QuickBooks and Xero): 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 and BigQuery: 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](https://roiva-staging.com/docs/warehouse-metric-queries). - **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. The Setup Guide 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. **Integrations → Sources** lists every category, the connection it **Reads from**, and the others that **Could also serve it**. An Owner or Admin picks another connection and clicks **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: **Make this the source**. 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 summed, on its own **Measurement → Sources** tab. The Sources page lists those exceptions 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. #### 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 Setup 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?](https://roiva-staging.com/docs/integration-not-syncing)). #### Disconnect or delete **Disconnect**, at the bottom of the **…** menu, stops syncing immediately. For Google Workspace, QuickBooks, Xero and Slack it also asks the platform to revoke Roiva's access, and so does **Delete Connection**. For any other platform, remove Roiva in that platform's own settings as well. 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 leaves the Connections list and no longer counts toward your plan's connection limit, but it isn't deleted: everything it synced and booked stays. For a sign-in platform, connecting the same platform account again usually brings that connection back, active. **Delete Connection**, under **Danger Zone** at the bottom of the **Edit Connection** page, removes the connection permanently: - The cost entries, value entries and metric entries it recorded stay on your initiatives. - Its links to initiatives, 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](https://roiva-staging.com/docs/allocation-rules-and-accounting-periods). [What Roiva keeps from each platform](https://roiva-staging.com/docs/reference/stored-data) lists, platform by platform, what a connection syncs and which fields of each record it keeps. #### Slack and Microsoft Teams notifications 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 notifications ticked — so the channel finance reads need not be the one IT reads. Connect Slack again to add one. For Teams, set up a workflow in the Teams channel that sends webhook alerts, then paste its URL into the **Notification 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 Owner for approval, approved or rejected. See [Budgets and budget vs. actual](https://roiva-staging.com/docs/budgets-and-budget-vs-actual). A new connection sends all of them. To send fewer, **Edit** the connection and untick them under **Notifications to send**. A connection whose notifications 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. **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** card. 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](https://roiva-staging.com/docs/connecting-your-first-integration) — connecting another platform - [Why is my integration not syncing?](https://roiva-staging.com/docs/integration-not-syncing) — errors, Reconnect and the Setup Check