Skip to main content

Overview

Portkey enables organization owners and admins to enforce request guardrails at the organization level. This feature ensures that API requests made within the organization comply with predefined policies, enhancing security, compliance, and governance.

How It Works

Organization owners can define input and output guardrails in the Organisation Guardrails section. By default, these guardrails are enforced on API requests across workspaces in the organization.
  • Input Guardrails: Define checks and constraints for incoming LLM requests.
  • Output Guardrails: Ensure LLM responses align with organizational policies.
The guardrails available here are the same as those found in the Guardrails section of the Portkey platform. Multiple providers are supported for setting up guardrails.

Guardrails Docs

Learn about the different Guardrails you can set up in Portkey

Configuration

Setting Up Guardrails Requirements

  1. Head to Admin Settings on the Portkey dashboard
  2. Navigate to the Organisation Guardrails section
  3. Add your Input and/or Output Guardrails
  4. Save your changes
Once configured, these guardrails are enforced on API requests across the organization, unless a workspace is explicitly excluded (see below).

Workspace Exclusions

Organization owners and admins can exclude specific workspaces from organization-level input and/or output guardrails. Exclusions are managed separately for input and output guardrails, so a workspace can opt out of one without opting out of the other. When a workspace is excluded from org-level input or output guardrails:
  • The corresponding organization default guardrails are not applied to requests in that workspace
  • Workspace-level guardrails (if configured) continue to apply independently
This is useful when a workspace needs a different compliance postureβ€”for example, an internal sandbox that should not inherit production org defaults.

Managing Exclusions via API

Use the Admin API to list and update workspace exclusions. Paths differ by entity type (input-guardrails or output-guardrails):

Update Workspace Exclusions

Exclude or include workspaces from org-level input or output guardrails

List Workspace Exclusions

List workspaces excluded from org-level input or output guardrails

Permissions

These scopes are available on Admin (organisation-service) API keys only. See API Keys (AuthN and AuthZ) for the full scope list.

Example: Exclude a workspace from org input guardrails

To remove an exclusion (re-apply org defaults to the workspace), call the same endpoint with "excluded": false.
How exclusions interact with workspace guardrailsWorkspace exclusions only clear organization-level defaults for that workspace. They do not remove or disable workspace-level guardrails. Configure those separately in workspace settings if needed.

Enforcing Workspace Level Guardrails

Set default input and output guardrails for a specific workspace

Configure Guardrail Access Permissions

Control who can view and manage guardrails within workspaces

Best Practices

  • Clearly communicate org-level guardrail requirements to developers in your organization.
  • Use workspace exclusions sparingly, and document why a workspace is opted out.
  • Prefer workspace-level guardrails when a team needs additional checks on top of org defaults, rather than excluding the workspace entirely.

Support

For questions about configuring organization-level guardrails or troubleshooting issues, contact Portkey support or reach out on Discord.
Last modified on July 28, 2026