External provider integrations.
OneOrg lets admins connect external tools so users can bring provider data into dashboards, agents, widgets, and workflows without configuring each feature separately.
Connect external providers
Integrations are managed from the connected accounts and organization integration areas. Admins or authorized users connect providers such as GitHub, Slack, Jira, Linear, Figma, Notion, Zendesk, and other business systems. Depending on the provider, the connection may use OAuth, an API key, or provider-specific setup fields.
Once a provider is connected, OneOrg can use that connection in the places users work: dashboard widgets, AI queries, project context, and automation triggers. The user experience is configuration-first. Connect the provider, confirm the account or workspace, then choose where that provider's data should appear.
Integrations also create a cleaner governance boundary. Access is tied to the organization and to the user's role. Admins decide which integrations are available, and users interact with approved data sources through OneOrg rather than scattering credentials across individual tools.
The result is a shared integration layer for the workspace: connect once, reuse where the UI allows it.
Before rolling an integration out broadly, confirm who owns the connected account, which workspace it points at, and which OneOrg features should be allowed to use that data.
Treat integrations as shared operating infrastructure. Connect only providers the organization is ready to govern, then decide which projects, dashboards, agents, or workflows should use them. A good integration has a clear owner, a known account or workspace, and a reason users can understand. Avoid connecting providers just because they are available. Unused connections create confusion during troubleshooting and increase the surface area admins need to review. When a team needs personal authorization, use connected accounts instead of organization-level integration settings. When the same provider should support many users or workflows, move it into the governed organization path.
Personal vs organization connections
Use integrations when OneOrg needs live or reusable data from external systems: repositories, tickets, analytics, design files, documents, support systems, calendars, or team communication tools. They are the right fit when a provider should become part of dashboards, agents, or workflow context.
Do not use integrations for one-off event delivery to your own receiving URL. Use webhooks for that. Do not use them to bypass provider permissions; OneOrg can only use the access granted by the connected account or organization credential.