Wrike - OpenText Identity and Access Management Integration and Automation

Common Integration Use Cases Between Wrike and OpenText Identity and Access Management

1. Automated user provisioning for project teams

When a new employee, contractor, or agency user is added in OpenText Identity and Access Management, their account and role can be automatically created or updated in Wrike. This ensures project managers, creative contributors, and external collaborators receive the correct access without manual setup.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: Faster onboarding, fewer access errors, and reduced administrative effort
• Typical outcome: Users are assigned to the right Wrike spaces, folders, or projects based on identity attributes such as department, role, or location

2. Role-based access control for sensitive projects

Wrike project access can be aligned with identity roles managed in OpenText Identity and Access Management. For example, only approved users in legal, finance, or executive roles can access confidential workspaces, budget tracking, or client-sensitive deliverables.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: Stronger governance and reduced risk of unauthorized access
• Typical outcome: Access to high-sensitivity projects is automatically restricted based on role, group membership, or policy

3. Single sign-on for distributed teams and external collaborators

Users can authenticate once through OpenText Identity and Access Management and then access Wrike without repeated logins. This is especially useful for marketing teams, agencies, and professional services organizations that work across multiple systems and need secure but frictionless access.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: Better user experience, fewer password resets, and improved adoption
• Typical outcome: Employees and approved external users access Wrike through a centralized authentication process

4. Automated deprovisioning when users leave or change roles

When a user is disabled, moved to a different team, or removed from a client engagement in OpenText Identity and Access Management, their Wrike access can be revoked automatically. This prevents former employees or expired contractors from retaining access to active projects and files.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: Improved security posture and lower compliance risk
• Typical outcome: Access removal is immediate and consistent across all Wrike workspaces and projects

5. Access governance for external agencies and temporary workers

Organizations often use Wrike to coordinate work with agencies, freelancers, and consultants. OpenText Identity and Access Management can enforce time-bound access, approval-based onboarding, and policy-driven permissions for these users so they only see the projects they are assigned to.

• Data flow: Bi-directional, with identity policy enforcement from OpenText Identity and Access Management and workspace assignment in Wrike
• Business value: Controlled collaboration with third parties and reduced exposure of internal information
• Typical outcome: External users are granted access only for the duration and scope of the engagement

6. Centralized identity-driven access for multi-department work management

Large enterprises often manage marketing, operations, product, and professional services work in Wrike. By integrating with OpenText Identity and Access Management, access can be standardized across departments using a single identity source, making it easier to manage users across multiple Wrike spaces and teams.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: Simplified administration and consistent access policies across the organization
• Typical outcome: Departmental access is assigned automatically based on identity attributes and organizational structure

7. Audit-ready access tracking for compliance and security reviews

Wrike activity and access events can be aligned with identity records in OpenText Identity and Access Management to support audits, investigations, and periodic access reviews. Security teams can verify who had access to which projects and when, especially for regulated or client-facing work.

• Data flow: Wrike to OpenText Identity and Access Management, with identity correlation and policy review
• Business value: Better auditability and easier compliance reporting
• Typical outcome: Access certifications and investigations are faster because project access can be tied back to authoritative identity data

8. Secure workflow access for approval-based processes

Wrike approval workflows for creative assets, project requests, or deliverable sign-off can be restricted to authorized approvers defined in OpenText Identity and Access Management. This ensures only the right managers, reviewers, or compliance stakeholders can approve work at each stage.

• Data flow: OpenText Identity and Access Management to Wrike
• Business value: More reliable approvals and stronger process control
• Typical outcome: Approval permissions are automatically assigned based on job function, team, or policy