Connectors in Team and Enterprise organizations
In an organization, each member connects their own GitHub account; there is no shared, organization-wide GitHub connection. Admins can’t connect or disconnect apps for other people today, but they can see connection activity in the audit log.
How connections work in an organization
- One person, one connection. Each member approves GitHub themselves from Settings → Integrations or Add from GitHub in a chat.
- Membership is checked. A connection can only be tied to an organization you are an active member of. Pending invitations don’t count.
- What a member brings in is theirs. Files added from GitHub become part of that member’s chat, under the organization’s usual chat and data rules.
What admins can see
When a member disconnects an integration, Syntic records it in the organization’s audit log. People with access to Settings → Audit Logs can review it. See Admin settings.
What admins can’t do yet
The following controls are not available yet. They are planned for the connector directory.
- Turn connectors on or off for the whole organization.
- Choose which apps members may connect.
- Connect an app once on behalf of everyone.
- Revoke another member’s connection from Settings.
If a member leaves, ask them to disconnect GitHub first, and to remove Syntic from their GitHub account’s authorized apps. See Connectors security and privacy.
Enterprise
Enterprise customers who need a specific connector or admin control can ask through sales@syntic.ai or Contact sales.