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

# Organization settings and security

> Manage Sofie organization settings, brand settings, integration availability, authentication policy, and security review surfaces.

Organization settings control shared Sofie behavior for your company. Depending on your permissions, you may see **General**, **Brand**, **Integrations**, and **Security Center** areas.

<Note>
  This page documents administrator-facing workflows at a high level. Exact options depend on your organization package, feature flags, and permissions.
</Note>

## Deeper guides

<Columns cols={2}>
  <Card title="Organization settings" icon="building-2" href="/admin/organization-settings">
    Manage organization name, passkey policy, and brand settings.
  </Card>

  <Card title="Microsoft SSO" icon="key-round" href="/admin/microsoft-sso">
    Set up Microsoft Entra ID sign-in and plan magic-link rollout.
  </Card>

  <Card title="Orchestration sharing controls" icon="workflow" href="/admin/orchestration-sharing-controls">
    Turn off unrestricted sharing and grant sharing access through roles.
  </Card>

  <Card title="Integration administration" icon="plug" href="/admin/integration-administration">
    Configure connected app availability and rollout.
  </Card>

  <Card title="Security Center" icon="shield-alert" href="/admin/security-center">
    Review events, alerts, access review snapshots, and recovery activity.
  </Card>

  <Card title="Users, groups, and roles" icon="users" href="/admin/users-groups-roles">
    Understand the full access model.
  </Card>
</Columns>

## Organization settings

Use **Organization Settings** for shared configuration.

Common tabs include:

| Tab              | Use it for                                                                          |
| ---------------- | ----------------------------------------------------------------------------------- |
| **General**      | Organization name and authentication policy.                                        |
| **Brand**        | Company logo and colors used in Sofie-generated document styling.                   |
| **Integrations** | Organization-level connected app availability and OAuth configuration when enabled. |

## General settings

General settings may include:

* Organization name.
* Whether passkeys are required for privileged users.
* Whether passkeys are required for all users.
* Whether email magic links are disabled when SSO is enabled.
* Microsoft Entra ID sign-in settings when your organization uses them.

Before changing authentication policy:

* Confirm the rollout plan.
* Confirm affected users have supported devices.
* Confirm SSO works before disabling magic links.
* Communicate the change before enforcement.
* Know who can help users who are blocked.

<Warning>
  Authentication policy changes can block users from Sofie until they complete required setup. Coordinate changes with your organization’s administrator or IT owner.
</Warning>

## Brand settings

Brand settings can affect how company details appear in CoDraft-related output.

You may be able to configure:

* Organization logo.
* Primary color.
* Secondary color.

Logo uploads may require JPG, GIF, or PNG files and a file size below the limit shown in the app.

Use brand settings for company presentation. Do not use them to imply document approval status.

## Integration administration

Organization-level integration settings control which connected apps can be enabled for users.

Depending on your environment, admins may configure:

* Microsoft.
* Google.
* Salesforce.
* Other organization-enabled providers.

Integration cards can show capabilities such as:

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

When configuring integrations:

* Confirm which provider capabilities users need.
* Decide whether to use Sofie-provided OAuth configuration or organization-owned OAuth configuration when available.
* Keep credential handling limited to authorized administrators.
* Test with a small group before broad rollout.
* Document which teams should connect their accounts.

<Warning>
  Do not paste credential values into public documentation, chat prompts, or shared drafts. Use only the secure fields provided in organization settings.
</Warning>

## Security Center

Administrators with access may see **Security Center**.

Security Center can help review:

* Security events.
* Alerts.
* Access review evidence.
* Recovery-related activity.

Use Security Center to inspect activity and prepare access review material. Do not treat it as a substitute for your organization’s required security process.

## Admin change checklist

Before saving administrator changes, check:

* Who is affected.
* Whether the change is reversible.
* Whether users need communication.
* Whether passkeys or sign-in settings could block access.
* Whether connected app changes affect external systems.
* Whether Workspace membership also needs updates.
* Whether the change should be tested with a smaller group first.

## Related docs

* [Account settings](/account/account-settings) for personal profile, signature, and notification settings.
* [Microsoft SSO](/admin/microsoft-sso) for Microsoft Entra ID sign-in setup.
* [Security and passkeys](/account/security-and-passkeys) for user-level passkey guidance.
* [Users, groups, and roles](/admin/users-groups-roles) for access management.
* [Connected apps](/integrations/connected-apps) for end-user integration behavior.