---
title: "Integrations Workspace"
slug: "integrations-workspace"
status: "update"
updated: 2025-06-22T15:46:35Z
published: 2025-06-22T15:46:35Z
canonical: "docs.plainid.io/integrations-workspace"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plainid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Workspace

The Orchestration Workspace is designed to represent all current connections to SaaS Applications and list all Policy Orchestration Points (POPs) available within the Environment.

[SaaS Authorization Management](/v1/docs/saas-policy-management-authorizers){target=`_blank`} provides out-of-the-box support to leading SaaS vendors and is managed within the Orchestration Workspace.. It enables the Platform to integrate with SaaS vendors to provide standardization and centralized Authorization management while supporting distributed deployment across the organization’s technology stack.

The Orchestration Workspace is used to **discover**, **map**, and **manage** SaaS vendor authorization policies using the vendor's native APIs. It allows your organization to centralize control over Policies originating in third-party applications, while still respecting the structure and constraints of each vendor's authorization model.

Each Orchestration Workspace includes:

- A list of **Policy Orchestration Points (POPs)** that define the integration between your {{variable.PlatformName}} Tenant and a specific vendor tenant.
- A view of the **Vendor Policies and Objects** discovered through the connection.
- Tools to **discover**, **manage**, and **sync** Authorization Policies between systems.

:::(Info) (Additional Information)
> For more on POPs, see [Managing POPs](/v1/docs/managing-pops){target=`_blank`}.  
> For details on supported vendors and authorizers, see [SaaS Authorization Management](/v1/docs/saas-policy-management-authorizers){target=`_blank`}.
:::

### Permissions
{{snippet.Permissions}}

---

### Creating an Orchestration Workspace

To begin using {{variable.Orchestrationproductname}}, you first need to [create an Orchestration Workspace](/docs/creating-a-new-workspace). By default, Environment do not have an Orchestration Workspace. They must be created manually.

Once you have created the Orchestration Workspace, you can manage POPs. Initially, when an Orchestration Workspace is created, the Workspace will be empty, as no POPs have been created yet. Refer to [Managing POPs](/v1/docs/managing-pops){target=`_blank`} for instructions on how to create a POP.

---


### Workspace Layout and Actions

When accessing an Orchestration Workspace, you  can:

- [View and manage all POPs](/v1/docs/managing-pops){target=`_blank`} connected to the Workspace.
- Initiate a [Discovery Process](/v1/docs/discovery-process){target=`_blank`} to retrieve authorization-related data, such as Roles, Resources, and Policies, from the vendor.
- Browse discovered Vendor Policies and Objects, including seeing a **[side-by-side comparison of PlainID and Vendor Policies](/v1/docs/orchestration-side-panel){target=`_blank`}** in their **native terminology**.
- Identify changes made by the vendor since the last sync through warning indicators.
- Deploy Policies from PlainID to the vendor.


This streamlined environment helps ensure consistency and traceability across authorization models, regardless of the vendor’s native structure.