OpenText Directory Services - Marq Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Marq

1. Automated User Provisioning for Brand Template Access

Data flow: OpenText Directory Services → Marq

When new employees, contractors, or agency users are added to OpenText Directory Services, their identity and group membership can be pushed to Marq to automatically create accounts and assign the correct template access. This reduces manual onboarding effort and ensures users only see approved brand assets and document templates based on their role, department, or region.

2. Role-Based Access Control for Marketing and Operations Teams

Data flow: OpenText Directory Services → Marq

Marq can use directory group membership from OpenText Directory Services to control who can edit, approve, or publish branded materials. For example, marketing managers, regional teams, and external agencies can be assigned different permissions based on their directory roles, helping enforce governance over brand content and reducing the risk of unauthorized edits.

3. Centralized Deprovisioning When Employees Leave or Change Roles

Data flow: OpenText Directory Services → Marq

When a user is disabled, removed from a group, or transferred to another department in OpenText Directory Services, Marq access can be updated automatically. This prevents former employees from accessing brand assets and ensures users no longer retain permissions that are no longer appropriate, improving security and compliance.

4. Synchronization of User Profile Attributes for Personalized Workspace Setup

Data flow: OpenText Directory Services → Marq

Directory attributes such as name, email, department, location, and business unit can be synchronized into Marq to prefill user profiles and tailor workspace access. This supports faster setup for distributed teams and helps route users to the correct templates, folders, or brand kits without manual configuration.

5. Regional or Business Unit Template Distribution

Data flow: OpenText Directory Services → Marq

Organizations operating across multiple regions or business units can use OpenText Directory Services groups to determine which Marq templates are available to each audience. For example, a North America sales team can be granted access to one set of approved collateral while EMEA teams receive localized versions, improving consistency and reducing content duplication.

6. Controlled Access for External Agencies and Contractors

Data flow: OpenText Directory Services → Marq

External users managed in OpenText Directory Services can be provisioned into Marq with tightly scoped permissions and expiration-based access aligned to project timelines. This is useful for agencies, freelancers, and temporary staff who need to collaborate on branded content without exposing broader internal assets.

7. Audit-Ready Identity Governance for Content Operations

Data flow: OpenText Directory Services → Marq

By using OpenText Directory Services as the system of record for identities and group assignments, Marq access decisions can be tied to a governed directory structure. This supports auditability for who had access to create, edit, or approve branded materials at any point in time, which is valuable for compliance, internal controls, and brand governance reviews.

8. Self-Service Access Enablement Through Directory-Driven Groups

Data flow: OpenText Directory Services → Marq

Business users can be granted access to Marq through standard directory group membership rather than manual ticket-based requests. When managers or IT administrators update group membership in OpenText Directory Services, access to Marq is adjusted automatically, reducing help desk workload and accelerating access for teams that need to produce marketing or operational content quickly.