How integrations work
There are three concepts to understand, and they build on each other:1
Connect an account
An integration is a type of source (Procore, Slack, Box, …). Connecting creates an account — an authorized link between Brink and that tool, established through the provider’s own sign-in and consent screen. Brink never sees your password.
2
Bind resources to projects
A scope binding maps one external resource — a Procore project, a Slack channel, a Box folder, a mail label — to one Brink project. A connected integration with no binding delivers nothing, so this step is not optional.
3
Sync
Once bound, Brink backfills history and then keeps the source in sync automatically. You can also trigger a sync manually at any time with Sync now.
Organization vs. personal connections
Every integration connects in one of two modes:- Organization connections are set up by an owner or admin from the Integrations page. The data is shared with the projects it’s bound to.
- Personal connections are set up by any member from Profile → My integrations. Data from a personal connection is only visible to you — it powers your own assistant and is never shared with your team.
Available integrations
Where to find things
- Integrations page (
Integrationsin the sidebar) — browse the catalog, connect organization accounts, see sync status, and manage each connection from its drawer. - Profile → My integrations — connect and manage your personal accounts.
- Projects page — each project card has an Integrations tab where you bind resources and trigger per-binding syncs.
- Onboarding — the setup wizard’s Connect your tools step offers the organization-level integrations when you first create your org.
Who sees what
Brink resolves visibility for every piece of ingested data, in strict order:- Private — anything from a personally connected account is visible only to that person. No setting can widen it.
- Project-scoped — data bound to a project is visible to that project’s members.
- Organization-wide — shared, non-mail sources with no project binding.
If a provider’s OAuth app hasn’t been configured for your deployment yet, clicking Connect creates a demo connection seeded with sample data (you’ll see account names like
demo-* and resources like “Demo Tower”). Contact Brink to enable the real connection.
