OpenText Directory Services - Sanity Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Sanity

1. Centralized user provisioning for content teams

Data flow: OpenText Directory Services → Sanity

Use OpenText Directory Services as the authoritative identity source to automatically provision editors, approvers, and administrators in Sanity. When a user is added to a directory group such as Marketing, Legal, or Regional Content Ops, Sanity can assign the correct workspace access and role permissions without manual setup.

• Reduces onboarding time for new content contributors
• Ensures access is aligned to organizational structure
• Minimizes security risk from stale or incorrect user accounts

2. Automated role updates based on directory group changes

Data flow: OpenText Directory Services → Sanity

When employees change departments or responsibilities in OpenText Directory Services, their Sanity permissions can be updated automatically. For example, a user moved from Content Author to Content Approver can be reassigned to the correct workflow role immediately, keeping publishing controls accurate.

• Keeps content governance in sync with HR and IT changes
• Prevents unauthorized publishing access
• Supports least-privilege access policies

3. Single sign-on for distributed content operations

Data flow: OpenText Directory Services → Sanity

Integrate directory-based authentication so employees use their existing enterprise credentials to access Sanity. This is especially useful for global teams working across multiple brands or regions, where a single login experience improves adoption and reduces password-related support tickets.

• Simplifies access for editors and reviewers
• Reduces help desk workload for password resets
• Improves security through centralized authentication controls

4. Automated deprovisioning when employees leave the organization

Data flow: OpenText Directory Services → Sanity

When a user account is disabled or removed in OpenText Directory Services, Sanity access can be revoked automatically. This is critical for contractors, agencies, and temporary staff who may have access to sensitive content, campaign assets, or unpublished pages.

• Closes security gaps quickly after offboarding
• Protects unpublished and confidential content
• Supports audit and compliance requirements

5. Content access segmentation by business unit or region

Data flow: OpenText Directory Services → Sanity

Directory groups can be mapped to Sanity workspaces, datasets, or content permissions to separate access by region, brand, or business unit. For example, EMEA marketing teams can be restricted to EMEA content models and assets, while global admins retain broader oversight.

• Supports decentralized content operations
• Prevents accidental edits across markets or brands
• Improves governance for multi-entity organizations

6. Approval workflow routing based on organizational hierarchy

Data flow: OpenText Directory Services → Sanity

Use directory attributes such as department, manager, or role to route content approvals in Sanity. A legal reviewer, regional manager, or product owner can be automatically assigned to approve specific content types, reducing manual coordination and speeding up publishing cycles.

• Shortens review and approval turnaround times
• Aligns content governance with organizational accountability
• Improves consistency in regulated publishing processes

7. Shared identity data for audit and compliance reporting

Data flow: Bi-directional

Synchronize user and group metadata between OpenText Directory Services and Sanity to support audit trails and compliance reporting. Sanity activity logs can be tied back to verified directory identities, helping teams answer who approved, edited, or published specific content and under which role.

• Strengthens traceability for regulated industries
• Supports internal and external audits
• Improves accountability across content operations