---
title: "Identities Workspace"
slug: "identities-workspace"
status: "update"
updated: 2026-06-30T06:27:08Z
published: 2026-06-30T06:28:18Z
canonical: "docs.plainid.io/identities-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.

# Identities Workspace

{{variable.Identities Workspace former}} is where you manage all your Identities (Dynamic Groups), manage Permissions, and more. Because many organizations maintain multiple types of Identity definitions (for example: internal users, external users, service accounts, etc.), the information for each type of user may come from different Identity Sources.

Each Workspace can support multiple Identity Sources (Main, AUX, and Context) but only one Main Source. Creating multiple Workspaces lets you access and use Identity data from multiple Main Sources. Multiple Identity Workspaces enable greater flexibility when building Policies because this lets connect Dynamic Groups, managed by different teams, all within the same Environment. 
    
By default, one Identities Workspace is created automatically when a new Environment is added to a Tenant. Additional Identity Workspaces can be created by Environment Admins (see [Managing Workspaces](/v1/docs/managing-workspaces)). 
    
When you click on the Identities Workspace, a list of currently defined Dynamic Groups for that Workspace is displayed.
 

![image.png](https://cdn.document360.io/726c7002-05a9-480e-b986-42c9e8824acd/Images/Documentation/image%28248%29.png){height="" width=""}


Dynamic Groups can be created directly in the Identities Workspace or while creating a Policy in the Policy Wizard. See [Managing Dynamic Groups](/v1/docs/managing-dynamic-groups){target=`_blank`}.
    

## Information Sources

The {{variable.PlatformName}} supports flexible data modeling that enables the use of External Data and Identity Sources with minimal customization. The Platform supports all relevant leading protocols (for example, Microsoft Active Directory, SQL, SCIM, JWT, etc.). 

Once you have defined an External Data Source, you need to map Attributes created within the {{variable.PlatformName}} to the External Source. Based on these mappings, the Identity Template is created at runtime.
 
 {{snippet.Default User Workspace}}