Workspaces
Focus
Focus
Prisma AIRS

Workspaces

Table of Contents

Workspaces

Create and manage workspaces in Workspace Management to organize team access and resources in Prisma AIRS, and switch between workspaces.
Where Can I Use This?What Do I Need?
  • Prisma AIRS, AI Gateway
  • Prisma AIRS, AI Red Teaming
  • Prisma AIRS, AI Supply Chain Security
  • Prisma AIRS, AI Agent Identity
  • Prisma AIRS license
  • Strata Cloud Manager access with a role that can manage workspaces
Workspaces are isolated, managed environments within your Strata Cloud Manager tenant that allow you to separate teams, projects, and resources across Prisma® AIRS™ while drawing from your organization's shared license capacity. Each workspace automatically pairs with an underlying Strata Cloud Manager Scope to enforce role-based access and data isolation.
When a new Prisma AIRS tenant is activated, a default workspace (tagged with the Default workspace badge) is automatically created on the backend. Create, view, and inspect workspaces under Prisma AIRS > Workspace Management. Creating a workspace automatically provisions a corresponding Strata Cloud Manager Scope, inheriting tenant users and service accounts mapped to that scope. Switch seamlessly between workspaces within supported Prisma AIRS modules including AI Gateway, AI Red Teaming, AI Model Security, and AI Agent Identity to isolate observability metrics, virtual API keys, providers, configs, guardrails, scan results, and agent identities.

Key Roles and Responsibilities

  • Tenant Admin (tenant-level role): Creates workspaces, assigns Workspace Admins, and removes tenant-level Prisma AIRS roles from users and service accounts that should be restricted to specific workspaces.
  • Workspace Admin (workspace-bound role): Configures and manages AI Gateway resources (providers, virtual keys, guardrails, and configs) within their assigned workspace.
  • Active Users and Service Accounts (workspace-bound role): Consume AI Gateway resources within their assigned workspace(s).

Workspace Access and Isolation

Workspace access is governed by where a Strata Cloud Manager IAM role is granted:
  • Tenant-level roles: Grant access to all workspaces in the tenant, including any workspaces created in the future. Only users with a tenant-level role can create new workspaces.
  • Workspace-bound roles: Grant access only to the workspace tied to that specific Strata Cloud Manager Scope. Users cannot see or discover workspaces they are not assigned to (the API returns a 404 response rather than 403).
  • Roles are additive: Assigning a workspace-bound role does not restrict a user who still holds a tenant-level role—the broadest grant always wins.
  • Default workspace behavior: Your tenant's automatically provisioned default workspace uses the scope workspace_default. All resources created before workspaces were enabled remain in workspace_default and cannot be moved to another workspace.
Creating a workspace does not automatically isolate existing users or service accounts, because pre-existing accounts already hold tenant-level roles. To enforce isolation between teams, follow the exact order in the Manage User and Service Account Access section below—removing tenant-level roles before assigning workspace-bound roles will lock users and automation out.

Create a Workspace

Create a workspace in Workspace Management.
  1. In Strata Cloud Manager, go to AI SecurityWorkspace Management.
  2. Click + New Workspace in the top-right corner of the table.
  3. In the Add New Workspace dialog, enter the following details:
    • Workspace Name (Required): Enter a unique, descriptive name for the team or environment.
    • Short Description (Optional): Provide a concise summary of the workspace's purpose.
  4. Click Add New Workspace.
    Prisma AIRS provisions the workspace and binds a new Strata Cloud Manager Scope in the background. Once complete, a confirmation banner ("Workspace has been added successfully") appears and the workspace is listed in the Total Workspaces table.

View Workspace Details

View the workspaces in your tenant and the details of each workspace.
  1. In Strata Cloud Manager, go to AI Security.
  2. Select Workspace Management.
  3. In the Total Workspaces table, review the available workspaces in your tenant:
    • Name: The display name of the workspace. Your tenant's automatically provisioned workspace is labeled with a Default workspace badge.
    • Description: Optional summary of the workspace's purpose or owning team.
    • Users: The total count of users and service accounts with access to the workspace.
    • Created / Last Updated: Timestamps indicating when the workspace was provisioned and last modified.
  4. Click any workspace row to open its details drawer, where you can view:
    • Workspace UUID (displayed in the drawer header and URL, required for Workspace Service and Admin API calls).
    • Status: Displays whether the workspace is Active.
    • Scope Name: The auto-generated Strata Cloud Manager Scope identifier bound to the workspace.
    • Users & Services: A searchable list of all users and service accounts assigned to the workspace, along with their Email, Type (User or Service Account), and assigned Role (e.g., superuser, ai_sec_admin, soc_admin).

Manage User and Service Account Access

Restrict users and service accounts to specific workspaces through Strata Cloud Manager Identity and Access Management (IAM).
Because Prisma AIRS Workspaces are backed by Strata Cloud Manager Scopes, user and service account permissions are governed through Strata Cloud Manager Identity and Access Management (IAM). To restrict users and service accounts to specific workspaces without disrupting active traffic, complete the following steps in order:
  1. Assign workspace-bound roles:
    1. Open AI SecurityWorkspace Management and click the target workspace to open its details drawer.
    2. Click Access Management at the top of the drawer (or go to SettingsIdentity & Access in Strata Cloud Manager).
    3. Assign each user and service account the appropriate Prisma AIRS role scoped specifically to that workspace's Scope Name (resource format: prn:<tsg_id>::::<scope_name>).
      • Bind each service account to only the single workspace it serves. If an automation pipeline serves multiple teams, create separate service accounts per workspace.
      • Users who still need access to pre-existing configurations in the default workspace must also be granted a role on the workspace_default scope.
  2. Verify workspace access:
    Return to the workspace details drawer to confirm the Users & Services list reflects the assigned roles, and verify that users can access the workspace in the relevant Prisma AIRS modules.
    IAM role changes can take a few minutes to propagate across Prisma AIRS (tokens expire after 15 minutes). If a newly granted workspace is not immediately visible, refresh your session or generate a new token.
  3. Remove tenant-level Prisma AIRS roles:
    In Strata Cloud Manager IAM, remove tenant-level Prisma AIRS roles from any user or service account that should only access specific workspaces.
    If an administrator also manages non-workspace-aware Strata Cloud Manager services (such as firewalls or DLP) in the same tenant, remove only their tenant-level Prisma AIRS roles and retain the roles required for those other services.

Switch Workspaces

Select a workspace as your active context across supported Prisma AIRS modules.
Once a workspace is created, you can select it as your active context across supported Prisma AIRS modules:
  1. In the left navigation menu under AI Security, expand a supported module (such as AI Gateway, AI Red Teaming, AI Model Security, or AI Agent Identity) and select any view.
  2. Click the Workspace selector dropdown in the top-left breadcrumb bar (next to the AI Gateway label).
  3. Select the desired workspace from the list.
    All dashboards, analytics, logs, virtual keys, and configurations update immediately to reflect only the data scoped to that workspace.