# Enterprise

Enterprise adds organizational governance for collaborative Workspaces. Policies help administrators establish authentication and publication requirements while individual resources retain their access boundaries.

Workspace administration does not automatically reveal private conversations or external account credentials.

## Review policy controls

| Control | Purpose | Boundary |
| --- | --- | --- |
| Marketplace publishing restrictions | Constrain outward publication and updates | Existing exposed listings require separate withdrawal. |
| Required SSO | Require organizational sign-in for applicable access | Configuring a connection and requiring its use are separate steps. |
| Required two-factor authentication | Require applicable members to enroll a second factor | Account enrollment and Workspace enforcement are separate. |

Eligible Owners and Admins manage available controls in **Settings → Workspace → Policies**. Review prerequisites, effective dates, and the people affected before changing a requirement.

## Prepare authentication changes

Confirm the administrator can satisfy the policy before enabling it. For SSO, verify the organizational connection and domain and check the required sign-in flow. Communicate the transition to members and use the policy's displayed state to distinguish setup, grace period, and enforcement.

Do not assume a plan downgrade disables an authentication requirement or guarantees recovery access. Resolve organizational sign-in and policy changes before making a subscription change that could affect their administration.

## Availability boundaries

Zero-data-retention-only inference remains planned and is not documented here as an available policy. Combined audit history and deletion-retention capabilities still require operational acceptance before this guide can offer them as dependable recovery or compliance workflows. Do not rely on a future feature to preserve data you intend to delete.

Enterprise configuration is not a blanket compliance guarantee. Review the specific control, its covered access paths, and your application responsibilities. [Permissions](/docs/concepts/permissions), [Security](/docs/services/security), and [Subscriptions](/docs/billing/plans) explain the related boundaries.

## Example: prepare an authentication policy

Before requiring organizational sign-in, confirm that the organizational connection works and that the administrator can meet the requirement. Review the displayed transition state and the affected membership before enforcement.

Verify the intended access path after the change. Keep resource permissions separate from authentication policy; a successful organizational login is not a grant to private content. See [Permissions](/docs/concepts/permissions).