Skip to main content

​
How syncing works

After you connect and bind an integration:
  1. Initial backfill. Email sources walk history recent-first in 30-day windows (about a year by default), so the freshest material is searchable almost immediately while older history fills in behind it. Calendars sync a rolling window around today. Procore backfills from a configured start date. File sources ingest everything in the bound folder.
  2. Incremental sync. Connections re-sync automatically about every 15 minutes. Sources that support push notifications (Gmail, Outlook, Teams, Box, AI Employee Inbox) sync near-real-time — a notification from the provider nudges the connection to sync right away.
  3. Manual sync. Every account card has a Sync now button, and each project binding has its own Sync button on the Projects page.
As data lands, Brink links cross-references automatically — an RFI number mentioned in an email or Slack message links to the Procore RFI — and registers citation anchors so assistant answers can point at the exact source message, record, or PDF page.

​
Status indicators

Each integration card shows a freshness line: Connection health states:
  • Connected — everything is working.
  • Needs attention — the authorization expired. Brink stops syncing this connection until someone clicks Reconnect; retrying a dead grant on its own is pointless.
  • Connection error — the last sync failed; the error is shown on the account card.
After repeated failures, syncs back off automatically (up to a maximum of 6 hours between attempts). The connection’s Details view shows this explicitly: “N consecutive sync failures — syncs are backing off.”
Turn on Integration failures under Settings → Organization settings → Email notifications to get failing connections reported in your org digest email, including which need a reconnect.

​
Inspecting a connection

Click any integration card to open its drawer, then Details on an account to see:
  • Scope bindings — which projects this account feeds
  • Available resources — browse what can be bound
  • This connection — live pipeline stages (running / queued / idle)
  • Recent syncs — completed runs with row counts

​
Disconnecting

Disconnect (on the account card, with a confirmation) genuinely severs the link: Brink revokes the grant with the provider where the provider supports it, and deletes the stored credentials either way.
Microsoft (Outlook, Outlook Calendar, Teams) offers no revocation endpoint. Brink deletes its stored tokens, but you may also want to remove the Brink app under your Microsoft account’s app permissions.
You can only disconnect your own personal connections — never a colleague’s.

​
Who can do what