> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Admin Panel

Open the Warp Admin Panel to manage team or workspace settings, check plan restrictions, and configure shared controls.

Use the browser-based [Warp Admin Panel](https://app.warp.dev/admin/) to manage team or workspace membership, billing, and shared configuration.

Your [role](https://docs.warp.dev/knowledge-and-collaboration/roles-and-permissions/) determines administrative access; your plan and workspace policies determine editable settings.

## Accessing the Admin Panel

### For team admins

1.  Open the [Admin Panel](https://app.warp.dev/admin/) in a browser and sign in.
2.  Confirm the selected team or workspace before changing a setting.
3.  Open the section for the setting you want to change.

In the Warp Factories web app, admins can also open the account menu and click **Admin panel**. See [Opening the Admin Panel](https://docs.warp.dev/factories/managing-plans-and-billing/#opening-the-admin-panel) for the factory billing route.

![Admin Panel with AI, privacy, code, billing, and sharing settings](https://docs.warp.dev/_astro/admin-panel-overview.DwOcO89f_Z1BJwa7.webp?dpl=dpl_2jwMhLeAUG9YKDij1xVF5dRK7bKv)

The Admin Panel groups shared configuration by topic.

### For team members

Team members see enforced settings in their personal Warp Settings. A disabled control can show “Your organization has configured this setting.” Ask the appropriate team or workspace admin to review it.

## How settings enforcement works

Being an admin does not make every setting editable. In Enterprise workspaces, workspace admins can enforce supported settings across teams or let each team decide. See [Workspace settings and team settings](https://docs.warp.dev/enterprise/team-management/workspaces/#workspace-settings-and-team-settings).

### Setting enforcement levels

| Setting state | What it means |
| --- | --- |
| Organization enforced | Members cannot override the configured value |
| Respect User Setting | Individual members control their own preference |
| Tier restricted | The plan does not permit changing the control |

For supported workspace settings, **Respect Team Setting** delegates the choice to the team. Enforced values are locked for team admins.

Test policies with an approved group before broader enforcement. Confirm the selected scope before saving.

## Plan limitations

A plan-locked setting shows “Configuring this setting is not available on your plan.” Review [plans, pricing, and refunds](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/) for the distinction between Terminal subscriptions and factory plans.

See [Managing admins](https://docs.warp.dev/knowledge-and-collaboration/roles-and-permissions/#managing-admins) for multiple-admin availability by product and plan.

Warp Factories plan differences include:

| Plan | Data controls and usage visibility |
| --- | --- |
| Start | Does not include Scale’s shared data controls or per-user team usage reporting |
| Scale | Admins control content collection, cloud conversation storage, and telemetry collection; admins see per-user team usage totals with unlimited history, while non-admins see only their own usage |
| Enterprise | Adds enforced secret redaction, a control to restrict direct API inference to the US, and customer-hosted data storage; usage reporting includes per-user and cost-type breakdowns, including workspace platform usage |

The direct API inference control is not a guarantee that all data stays in the US. For customer-hosted run data, see [Self-hosted data storage](https://docs.warp.dev/factories/self-hosting/data-storage/).

## Admin Panel sections

### AI settings

Configure agent autonomy and command permissions for the selected team.

-   **AI in remote sessions** - Controls availability during SSH sessions and other remote connections.
-   **Prompt summarization caching** - Controls provider caching used for long conversations. Provider retention follows the selected model and inference configuration. See [model retention policies](https://docs.warp.dev/agents/inference/model-choice/#zero-data-retention-policies).

#### Autonomy settings

Configure approval behavior for applying code diffs, creating plans, executing commands, and reading files. The available choices include **Agent Decides**, **Always Ask**, **Always Allow**, and **Respect User Setting**.

See [Agent Profiles and permissions](https://docs.warp.dev/agents/capabilities/agent-profiles-permissions/) for the action permissions and personal configuration.

#### Directory and command control

Directory allowlists identify approved paths, such as `~/git/internal-tooling` or `/home/user/repos/public-*`. Command allowlists and denylists use regular expressions.

Caution

Command denylist rules take precedence over command allowlists and autonomy settings. A matching command still requires explicit approval.

### Privacy settings

**Content collection for service improvement**

The “UGC Data Collection” dropdown controls how Warp collects your team’s content to improve the service:

-   **Disabled** - Warp doesn’t collect team content for service improvement
-   **Enabled** - Allow data collection for service improvement
-   **Respect User Setting** - Let individual users decide

Telemetry collection is separate from team content collection. Neither control changes [provider retention requirements](https://docs.warp.dev/agents/inference/model-choice/#models-requiring-provider-retention) or disables product storage.

**Cloud conversation storage**

Controls cloud sync of personal Terminal conversations. Disabling it doesn’t disable factory or other cloud agent run storage. See [product storage](https://docs.warp.dev/support-and-community/privacy-and-security/privacy/#product-storage) for run-data categories and storage options.

**Enterprise secret redaction**

Enterprise teams can configure common secret patterns and custom regex patterns for redaction before requests reach LLM providers. See [Secret redaction](https://docs.warp.dev/support-and-community/privacy-and-security/secret-redaction/) for scope and configuration.

#### Managing team content collection in the Admin Panel

Admins can review team content collection in a browser. Editable choices depend on the plan and workspace policies:

1.  Open the [Admin Panel](https://app.warp.dev/admin/) for the team and go to **Privacy**.
2.  If “UGC Data Collection” is editable, choose **Disabled** to stop team content collection, or **Respect User Setting**, if available, to defer to individual preferences.
3.  After changing the value, reload the page and confirm it persists.

Plans that lock collection off keep it **Disabled**; admins cannot enable it or delegate to individual preferences. Ask a workspace admin about workspace-enforced values. For personal controls, see [browser privacy preferences](https://docs.warp.dev/support-and-community/privacy-and-security/privacy/#how-to-disable-telemetry-and-crash-reporting).

### Code settings

Configure Codebase Context for team repositories. Where the control is available, choose **Disabled**, **Enabled**, or **Respect User Setting**.

Repository and file limits depend on the plan. See [Codebase Context](https://docs.warp.dev/agents/capabilities/codebase-context/) for indexing behavior and limits.

### Models settings

Use the **Models** page for the controls included in your plan:

-   **Enterprise model restrictions** - Admins can enable or disable individual models and configure [BYOLLM routing](https://docs.warp.dev/enterprise/enterprise-features/bring-your-own-llm/). Self-serve plans don’t include a team-wide model-blocking control.
-   **Shared provider credentials** - Configure [team-managed API keys and endpoints](https://docs.warp.dev/enterprise/enterprise-features/team-managed-keys-and-endpoints/) on plans that include that control. Sharing credentials isn’t a model restriction.
-   **Enterprise custom routers** - Share [routing rules](https://docs.warp.dev/agents/inference/custom-routers/#team-synced-routers) with the team. A router’s choices are separate from enforced model availability.

**Models with provider-specific data retention requirements**

Some models require provider retention and aren’t covered by [Zero Data Retention (ZDR)](https://docs.warp.dev/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr), even when team content collection is disabled. Review the complete [exception list on the model-choice page](https://docs.warp.dev/agents/inference/model-choice/#models-requiring-provider-retention). For Enterprise teams, these models are **disabled by default**. A workspace admin must explicitly enable them before team members can use them.

Self-serve customers must review their selected models and overrides using the [Terminal procedure](https://docs.warp.dev/agents/inference/model-choice/#reviewing-inference-and-privacy-in-terminal) or [factory ZDR guidance](https://docs.warp.dev/factories/zero-data-retention/).

### Billing settings

On **Billing**, review usage and the controls available for your plan. Self-serve [spend limits and auto-reload](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) control additional purchases. Enterprise [pools and spending controls](https://docs.warp.dev/enterprise/support-and-resources/billing/) follow the contract.

Enterprise supports monthly workspace, team, and per-user spend caps, separate local and cloud spending limits, and usage alerts.

For browser-based factory funding, upgrade, and payment routes, use [Managing factory plans and billing](https://docs.warp.dev/factories/managing-plans-and-billing/).

### Sharing settings

Configure direct-link and public-link access for Warp Drive resources:

-   **Direct link sharing** - Determines whether resources can be shared by link and whether access is limited to team members.
-   **Anyone with link sharing** - Determines whether people outside the team can open a shared resource.

See [Warp Drive sharing](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/) before changing access to existing resources.

### Platform settings

Configure shared cloud-agent settings for the selected team.

-   **Agent artifact attachments** - Choose **Disabled**, **Link only**, or **Embed** for screenshots and videos. See [Screenshots and videos in pull requests](https://docs.warp.dev/agents/capabilities/computer-use/artifacts-in-prs/) for the security implications.
-   **Enabled GitHub Orgs** - Associates a team with GitHub App installations for the supported standalone cloud-agent workflows.

In the Admin Panel, open **Platform**. Under **Enabled GitHub Orgs**, select the team’s organizations.

![Enabled GitHub Orgs setting in the Admin Panel Platform section](https://docs.warp.dev/_astro/admin-panel-enabled-github-orgs.DgeT9Y28_ZqBhXs.webp?dpl=dpl_2jwMhLeAUG9YKDij1xVF5dRK7bKv)

The Platform section includes team GitHub authorization.

Repository access comes from the GitHub App installation’s selection in [GitHub settings](https://github.com/settings/installations). Personal API key, agent API key, and integration-triggered runs use different identities. See [Team GitHub authorization](https://docs.warp.dev/platform/team-access-billing-and-identity/#team-github-authorization) rather than applying one identity rule to every workflow.

## Multi-admin functionality

### Promoting and demoting admins

Follow [Promoting or demoting admins](https://docs.warp.dev/knowledge-and-collaboration/roles-and-permissions/#promoting-or-demoting-admins) to change administration access on a supported plan.

## Troubleshooting

### Users can’t see new settings

Confirm that you changed the intended team or workspace and that the setting isn’t delegated to the user. Check the affected user’s membership and reload Settings before testing again.

### Setting is grayed out in Admin Panel

Check whether the control is restricted by the plan or locked by a workspace policy. Ask a workspace admin about an enforced value. Use [plans and pricing](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/) for plan requirements.

### Command allowlist not working

Check the regex, autonomy setting, and command denylist together. A matching denylist rule still requires approval. See [Agent Profiles and permissions](https://docs.warp.dev/agents/capabilities/agent-profiles-permissions/).

### Responding to security incidents

Review the affected run, [agent permissions](https://docs.warp.dev/agents/capabilities/agent-profiles-permissions/), and applicable team and workspace policies.

## Support

For access problems, contact [support@warp.dev](mailto:support@warp.dev) or your Enterprise support channel.

## Related pages

-   [Managing team membership](https://docs.warp.dev/factories/teams/)
-   [Roles and permissions](https://docs.warp.dev/knowledge-and-collaboration/roles-and-permissions/)
-   [Workspaces for Enterprise teams](https://docs.warp.dev/enterprise/team-management/workspaces/)
-   [Managing factory plans and billing](https://docs.warp.dev/factories/managing-plans-and-billing/)
-   [Getting started for admins](https://docs.warp.dev/enterprise/getting-started/getting-started-enterprise/) - Configure Enterprise SSO, membership, and policies
