---
modificationDate: November 17, 2026
title: Protected resources
description: Learn how to restrict who can interact with sensitive Expo Services resources, such as the update channel your production app uses.
---

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](https://docs.expo.dev/llms.txt) or append .md to any documentation URL.

# Protected resources

Learn how to restrict who can interact with sensitive Expo Services resources, such as the update channel your production app uses.

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/eas/protected-resources/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/protected-resources/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: Expo Services > Reference
Pages in this section:
- [EAS and Expo service names](https://docs.expo.dev/eas-to-expo.md)
- [Webhooks](https://docs.expo.dev/eas/webhooks.md)
- [Protected resources](https://docs.expo.dev/eas/protected-resources.md) (this page)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

You can mark some Expo Services resources as protected. Only members with the Release Manager, Admin, or Owner [role](https://docs.expo.dev/accounts/account-types.md#manage-access) can take protected actions on these resources. This is similar to the concept of protected branches on Git hosting services like GitHub, where only members with elevated permissions can push to them.

## Expo Workflows and protected resources

Workloads triggered by GitHub events, App Store Connect events, or a schedule act as the [GitHub App robot](https://docs.expo.dev/accounts/programmatic-access.md#github-app-robot). This robot has the Developer role by default. To let these workloads access protected resources, give the robot the Release Manager role on the [Access tokens](https://expo.dev/accounts/%5Baccount%5D/settings/access-tokens) page.

## Protected channels

When you protect an [Expo Update](https://docs.expo.dev/eas-update/how-it-works.md) channel, only Release Managers, Admins, and Owners can:

-   Publish updates to a branch the channel points to. This includes `eas update`, republishing, and rollbacks.
-   Rename or delete a branch the channel points to.
-   Edit the channel. This includes changing which branch it points to, starting or ending a rollout, and pausing or resuming updates.
-   Delete the channel.
-   Remove protection from the channel.

Members with other roles can still view a protected channel and its branches. Developers can publish to branches that no protected channel points to.

### Protect or unprotect a channel

```sh
# Protect a channel
eas channel:protect production

# Remove protection from a channel
eas channel:unprotect production
```

Only Release Managers, Admins, and Owners can run these commands. Run either command without a channel name to pick one from a list. Both commands require EAS CLI 24.0.0 or later.

> When you [transfer a project](https://docs.expo.dev/accounts/account-types.md#transfer-projects-between-accounts) to another account, Expo Services removes protection from all of its channels. Protect them again in the new account if needed.

## Protected credentials

When you turn on credentials protection for an account, only Release Managers, Admins, and Owners can view, create, change, or delete [build](https://docs.expo.dev/app-signing/app-credentials.md), submission, and push credentials stored on Expo servers. Protection applies to every project in the account. Developers lose access to these credentials.

To turn credentials protection on or off, go to [**Credentials**](https://expo.dev/accounts/%5Baccount%5D/credentials) in your account and use the **Protect credentials** switch. Only Admins and Owners can change this setting.

## Protected environment variables

Environment variable protection applies to [environment variables](https://docs.expo.dev/eas/environment-variables.md) that belong only to the `production` environment. When you turn it on for an account, only Release Managers, Admins, and Owners can view and manage these variables. Protection applies to account-wide and project variables in every project of the account. Members with other roles don't see these variables. Variables that also belong to another environment, such as `preview`, aren't protected. One exception: only Release Managers, Admins, and Owners can create or change a project variable that applies to `production` and has the same name as a protected account-wide variable.

To turn environment variable protection on or off, go to [**Environment variables**](https://expo.dev/accounts/%5Baccount%5D/environment-variables) in your account and use the **Protect production environment variables** switch. Only Admins and Owners can change this setting.
