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

# Integrations

> Securely store and manage AI provider credentials across your organisation with centralized governance controls

<Note>
  **For Organisation Admins:** This page is for managing credentials across multiple workspaces. To use AI models in your workspace, see the [Model Catalog](/docs/aigw/product/model-catalog) documentation.
</Note>

**What are Integrations?**
A place to store credentials once and share them with multiple workspaces.

**Why use them?**

* **Save time:** Store API keys once, use in many workspaces
* **Control access:** Decide which workspaces can use which credentials
* **Control models:** Enable or disable specific models at the Integration level
* **Set limits:** Different budgets and rate limits per workspace

**How it works:**

1. Store credentials here (creates an Integration)
2. Choose which models are available (enable/disable models)
3. Share with workspaces (they see it as a Provider in their Model Catalog)
4. Each workspace can use the same credentials with different limits, but only access models you've enabled

**Simple analogy:** Like a shared password vault. Store your OpenAI API key once, then share it with multiple workspaces. Each workspace can use the same credentials but with different budgets and rate limits.

When you create an Integration, you control:

* **Who** can use these credentials (which workspaces)
* **What** models they can access
* **How much** they can spend (budget limits)
* **How fast** they can make requests (rate limits)

## Why Use Integrations?

Instead of each workspace entering the same API keys separately, store them once and share them:

1. **Save time** - No need to re-enter credentials in each workspace
2. **Control access** - Decide which workspaces can use which credentials
3. **Set limits** - Different budgets and rate limits per workspace
4. **Stay secure** - API keys are encrypted and never exposed to end users
5. **Track everything** - See usage and costs across all workspaces

## Understanding the Integrations Dashboard

Navigate to the [Integrations page](https://stratacloudmanager.paloaltonetworks.com/) in your Prisma AIRS AI Gateway organisation settings. The page is organized into three tabs, each serving a distinct purpose:

* **`All`**: This is a comprehensive list of all 50+ providers the AI Gateway supports. This is your starting point for connecting a new provider to your organisation.
* **`Connected`**: This tab lists all the integrations that you have personally connected at the organisation level. It's your primary view for managing your centrally-governed providers.
* **`Workspace-Created`**: This tab gives you complete visibility and governance over any integrations created *by Workspace Admins* for their specific workspaces. It ensures that even with delegated control, you maintain a full audit trail and can manage these instances if needed.

## Creating an Integration

Let's walk through creating an Integration for AWS Bedrock as an example:

<Steps>
  <Step title="Navigate to Integrations">
    From your admin panel, go to [**Integrations**](https://stratacloudmanager.paloaltonetworks.com/) and click **Create New Integration** (or click **Connect** from the **`All`** tab).
  </Step>

  <Step title="Select Your AI Provider">
    Choose from 200+ supported providers. Each provider may have different credential requirements.
  </Step>

  <Step title="Configure Integration Details">
    * **Name**: A descriptive name for this integration (e.g., "Bedrock Production")
    * **Slug**: A unique identifier used in API calls (e.g., "bedrock-prod")
    * **Description**: Optional context about this integration's purpose
    * **Endpoint Type**: Choose between Public or Private endpoints
  </Step>

  <Step title="Enter Provider Credentials">
    Each provider requires different credentials:

    **For OpenAI:**

    * API Key
    * Optional: Organisation ID, Project ID

    **For AWS Bedrock:**

    * AWS Access Key
    * AWS Secret Access Key
    * AWS Access Key ID
    * AWS Region

    <Card href="/docs/aigw/product/model-catalog/connect-bedrock-with-amazon-assumed-role" title="Connect Bedrock with Amazon Assumed Role">
      How to integrate Bedrock using Amazon Assumed Role Authentication
    </Card>

    Similarly for:

    * Azure OpenAI
    * Google Vertex AI
    * Anthropic
    * Gemini
      and more...
  </Step>
</Steps>

***

# Configuring Your Integration Access & Limits

After creating your Integration, you'll need to configure three key aspects that work together to control access and usage:

<CardGroup cols={2}>
  <Card title="Workspace Provisioning" icon="users" href="/docs/aigw/product/model-catalog/workspace-provisioning">
    Which teams and projects can use these credentials
  </Card>

  <Card title="Model Provisioning" icon="cubes" href="/docs/aigw/product/model-catalog/model-provisioning">
    Which models the Integration exposes, plus custom models and pricing
  </Card>

  <Card title="Budget Limits" icon="credit-card" href="/docs/aigw/product/policies/budget-limits">
    Financial guardrails, per workspace, cascading to every provider
  </Card>

  <Card title="Rate Limits" icon="stopwatch" href="/docs/aigw/product/policies/rate-limits">
    Velocity controls, per workspace, by request or token
  </Card>
</CardGroup>

Budget and rate limits are configured within Workspace Provisioning and provide financial and usage guardrails for your AI operations.

## Monitoring and Analytics

### Tracking Spending and Usage

Track spending, usage, and 40+ crucial metrics for any specific AI integration by navigating to the Analytics tab and filtering by the **desired key** and **timeframe**.

***

## FAQs

<AccordionGroup>
  <Accordion title="How are provider API keys stored?">
    Your API keys are always encrypted and stored in secure, isolated vaults. They are only decrypted in-memory, within sandboxed workers, at the exact moment a request is made to the provider. This ensures the highest level of security for your credentials.
  </Accordion>
</AccordionGroup>


## Related topics

- [Integrations](/docs/aigw/product/mcp-gateway/integrations.md)
- [Get integrations](/docs/aigw/api-reference/integrations/get-integrations.md)
- [Post integrations](/docs/aigw/api-reference/integrations/post-integrations.md)
- [KMS Integration](/docs/aigw/product/enterprise-offering/kms.md)
- [Suggest a new integration!](/docs/aigw/integrations/llms/suggest-a-new-integration.md)