> ## Documentation Index
> Fetch the complete documentation index at: https://sofiedocs.usetransfer.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration administration

> Enable organization-level connected app providers and understand how integration administration affects Sofie users.

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](/integrations/connected-apps) for end-user connection and usage guidance.

## Provider setup guides

<Columns cols={3}>
  <Card title="Microsoft 365" icon="mails" href="/admin/integrations/microsoft-365">
    Register a Microsoft Entra app and enable Microsoft 365 access.
  </Card>

  <Card title="Google Workspace" icon="mail" href="/admin/integrations/google-workspace">
    Configure a Google Cloud OAuth client for Gmail, Calendar, and Drive.
  </Card>

  <Card title="Salesforce" icon="cloud" href="/admin/integrations/salesforce">
    Create a Salesforce connected app for CRM access.
  </Card>
</Columns>

## What admins control

Depending on enabled providers, administrators may control:

* Which integrations are available.
* Whether a provider is enabled or disabled.
* Whether Sofie uses default OAuth configuration or organization-owned OAuth configuration.
* Provider-specific configuration such as tenant or authentication base URL fields.

Integration cards may show capabilities such as:

* Email.
* Calendar.
* Files.
* Contacts.
* CRM.

## Enable a provider

<Steps>
  <Step title="Open Organization Settings">
    Go to **Organization Settings**.
  </Step>

  <Step title="Choose Integrations">
    Open **Integrations** when the tab is available.
  </Step>

  <Step title="Review provider capabilities">
    Check whether the provider supports the source or action users need.
  </Step>

  <Step title="Choose configuration">
    Use the configuration option your organization supports.
  </Step>

  <Step title="Enable the provider">
    Turn the provider on.
  </Step>

  <Step title="Save settings">
    Save and test with a small user group before broad rollout.
  </Step>
</Steps>

## 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.

<Warning>
  Integration changes can affect systems outside Sofie. Test carefully and follow your organization’s connected app approval process.
</Warning>

## 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

If your organization uses its own OAuth app, configure it only in the secure organization settings UI.

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:

<Steps>
  <Step title="Connect a test account">
    Use an account with representative but limited access.
  </Step>

  <Step title="Test read actions">
    Search or retrieve a file, event, message, or CRM record.
  </Step>

  <Step title="Test write actions only when safe">
    If the provider supports changes, use a test item and review every confirmation.
  </Step>

  <Step title="Test Workspace import">
    Import a file into a Workspace if that is part of the user workflow.
  </Step>

  <Step title="Document user guidance">
    Tell users what the integration is for and what actions need review.
  </Step>
</Steps>