How SchemaBounce reaches your tools
SchemaBounce reaches a tool like Google Drive, Microsoft 365, or Jira in one of three ways. Each one has a single job, and each is set up in one place.
| Name | What it does | Who sets it up | Where |
|---|---|---|---|
| Connections | Let agents work in your tools, live, as you or as a shared account. | Anyone (Personal), a team's head (Team), admins | Agents, Connections |
| Data sources | Copy data from a tool into SchemaBounce, continuously. | Admins | Pipelines, Sources |
| File storage | Where SchemaBounce keeps its own files: SchemaBounce storage, or your company's Google Drive or Microsoft 365 account. | Admins | Files, Admin, Backends tab |
Slack, WhatsApp, and Git are workspace integrations under Settings, Integrations. They connect the workspace to a channel or a repository; an agent never uses them to act as a person.
Which one do I need?
- Should an agent read or change things in the tool while it works? Use a Connection.
- Do you want the tool's data copied in, kept current, and queryable? Use a Data source.
- Should the files SchemaBounce and your agents write live in your own Google Drive or Microsoft 365? Set File storage.
- Is it Slack, WhatsApp, or a Git repository? Use Settings, Integrations.
Connections have three levels
| Level | What it is | Used for |
|---|---|---|
| Personal | Your own account | Only your messages and runs. In a shared chat, a colleague's message never uses it. |
| Team | A shared or service account for one team | The team's messages, and its agents' scheduled runs, where it's granted to the agent. |
| Workspace | A company service or shared account | Anyone's messages and scheduled runs, where it's granted to the agent. |
Every tool call has an actor: the person whose message caused it. When an agent calls a tool, SchemaBounce picks the actor's own Personal connection first, then a Team connection, then one the agent owns, then a Workspace connection. If none fits, the tool answers that you need to connect your account, and the rest of the run carries on.
Scheduled runs, webhooks, workflows, and messages from Slack or WhatsApp have no person behind them. They never use a Personal connection, only Team or Workspace ones.
Team and Workspace connections must be a shared or service account, such as [email protected], never someone's personal login. A personal login leaves with its owner; a shared account stays with the company.
A Personal connection is never shared with a colleague or a team. To give others access to a tool, add a Team or Workspace connection.
Approving an agent's action does not change whose account it uses. If you approve a colleague's request, it still runs as your colleague.
Each connection card shows whose account it is: Your account, Team account, or Company account. Each tool call in an agent chat carries the same label beside the tool name, so you can see whose account that call used. A colleague's call that used their own account shows Sender's account. See MCP ownership and sharing for grants, sharing, and tool limits.
File storage is one company account
File storage is set once per workspace by an admin, in Files, Admin, Backends.
- Sign in with a shared company account, not your personal login.
- On Google's consent screen, tick the Google Drive box. Without it, the connection is refused and nothing is stored.
- You come straight back to the Backends tab when the provider is done.
- Choose where new files go, so they belong to your organization rather than to one account:
- Google Drive: click Choose shared drive folder and pick a folder in a shared drive. A folder in someone's My Drive is refused, and so is one the connected account can't add files to.
- Microsoft 365: click Choose SharePoint library, search for the site, and pick one of its document libraries.
Until you choose, new files go to the connected account's own My Drive or OneDrive, and the Backends tab says so. Files stored earlier stay where they are and stay readable. If you disconnect and connect again, choose the location again.