Skip to main content
Integration administration controls which connected app providers are available to users. End users still connect their own accounts where required. Use this page for organization-level setup. Use Connected apps for end-user connection and usage guidance. Google and Microsoft integrations require organization-owned OAuth apps. Create a Google Cloud OAuth client or Microsoft Entra app registration, then select Use Organization OAuth App and save its credentials in Sofie before enabling the provider.

​
Provider setup guides

Microsoft 365

Register a Microsoft Entra app and enable Microsoft 365 access.

Google Workspace

Configure a Google Cloud OAuth client for Gmail, Calendar, and Drive.

Salesforce

Create a Salesforce connected app for CRM access.

Slack

Create the Slack app and connect a Slack workspace.

Microsoft Teams

Configure an Azure Bot and distribute Sofie’s Teams app.

Messaging destinations

Approve automated post destinations and check connection health.
Slack and Teams require an organization app installation and a personal identity link for each user. Slack users also authorize their own research and send-as-user access. Outbound automation uses separate destination controls. Follow the messaging guides above for those setup flows.

​
What admins control

Depending on enabled providers, administrators may control:
  • Which integrations are available.
  • Whether a provider is enabled or disabled.
  • Organization-owned OAuth app credentials for Google and Microsoft.
  • Provider-specific configuration such as tenant or authentication base URL fields.
Integration cards may show capabilities such as:
  • Email.
  • Calendar.
  • Files.
  • Contacts.
  • CRM.
  • Teams messaging when enabled.

​
Enable a provider

1

Open Organization Settings

Go to Organization Settings.
2

Choose Integrations

Open Integrations when the tab is available.
3

Review provider capabilities

Check whether the provider supports the source or action users need.
4

Choose configuration

For Google and Microsoft, click Show Details under OAuth Configuration and select Use Organization OAuth App. Enter the credentials from your organization’s app. Use the provider guide for other integrations.
5

Enable the provider

Turn the provider on.
6

Save settings

Save and test with a small user group before broad rollout.

​
Rollout checklist

Before enabling an integration broadly, confirm:
  • Which teams need it.
  • Which capabilities they need.
  • Whether users need to connect their own accounts.
  • Whether connected app actions can create, update, send, or delete external items.
  • Whether training or internal guidance is needed.
  • Who owns support for connection failures.
Integration changes can affect systems outside Sofie. Test carefully and follow your organization’s connected app approval process.

​
User connection versus admin enablement

Admin enablement makes a provider available. User connection gives Sofie access to that user’s account where required. If a user cannot use an integration, check:
  • Provider is enabled for the organization.
  • Feature is available in the environment.
  • User has connected their account.
  • User has permissions in the external system.
  • The requested item exists and is accessible to the connected account.
  • The action is supported by the provider.

​
OAuth configuration guidance

Configure your organization’s OAuth app only in the secure organization settings UI. Google and Microsoft require your organization’s own apps. Do not put credential values in:
  • Chat prompts.
  • CoDrafts.
  • Shared Workspaces.
  • Public documentation.
  • Screenshots used for broad training.
Use placeholders when documenting internal setup, such as client ID or redirect URI, not real values.

​
Test after changes

After enabling or changing an integration:
1

Connect a test account

Use an account with representative but limited access.
2

Test read actions

Search or retrieve a file, event, message, or CRM record.
3

Test write actions only when safe

If the provider supports changes, use a test item and review every confirmation.
4

Test Workspace import

Import a file into a Workspace if that is part of the user workflow.
5

Document user guidance

Tell users what the integration is for and what actions need review.