# Secrets editor is read-only for my own public app

**URL:** <https://discuss.streamlit.io/t/secrets-editor-is-read-only-for-my-own-public-app/122911>\
**Category:** Show the Community!\
**Tags:** session-state, discussion\
**Created:** [October 20, 2026, 9:15pm UTC](https://discuss.streamlit.io/t/secrets-editor-is-read-only-for-my-own-public-app/122911 "2026-10-20T21:15:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![manosv18](https://sea2.discourse-cdn.com/streamlit/user_avatar/discuss.streamlit.io/manosv18/32/78327_2.png) [@manosv18](https://discuss.streamlit.io/u/manosv18)\
**Post date:** [October 20, 2026, 9:15pm UTC](https://discuss.streamlit.io/t/secrets-editor-is-read-only-for-my-own-public-app/122911/1 "2026-10-20T21:15:33Z")

</div>

Hello,

My Streamlit Community Cloud app is deployed from my public GitHub repository `manosv18/managers-lab`, branch `main`.

I own the repository and can access its GitHub settings. In Community Cloud, I can open Settings, reboot the app, and use Edit with Codespaces. However, the Secrets text area is completely read-only: I cannot place the cursor, select text, or edit it, and the Save changes button remains disabled.

I corrected my Streamlit email identity to `manosv18@gmail.com` and reconnected GitHub as `manosv18`, but the problem persists. Rebooting the app and refreshing the browser did not help.

Could you help restore editing access to the Secrets settings for my app?

Thank you.

---

<div class="post-metadata">

**Author:** ![Justin15](https://sea2.discourse-cdn.com/streamlit/user_avatar/discuss.streamlit.io/justin15/32/78801_2.png) [@Justin15](https://discuss.streamlit.io/u/Justin15)\
**Post date:** [November 5, 2026, 3:34am UTC](https://discuss.streamlit.io/t/secrets-editor-is-read-only-for-my-own-public-app/122911/2 "2026-11-05T03:34:25Z")

</div>

When the **Secrets** editor (`secrets.toml`) in Streamlit Community Cloud stays locked in read-only mode even though you own the public GitHub repository (`manosv18/managers-lab`) and can trigger **Reboot** / **Edit with Codespaces** , the cause is a **cached GitHub OAuth permission mismatch on the original deployment record** after changing your email identity.

### Why It Happens

Streamlit Community Cloud gates write access to **Settings → Secrets** by checking whether your currently active GitHub OAuth token has `admin` / `push` permissions on the deployment’s bound repository ID. When you updated your email to `manosv18@gmail.com` and reconnected GitHub, Community Cloud kept the original app deployment record tied to the pre-update identity/token scope, putting the Monaco Secrets editor into viewer-only (`readOnly: true`) mode.

### 2-Step Fix to Restore Full Secrets Editing

1. **Refresh the Streamlit GitHub OAuth Token Scope** :
  - Sign out of `share.streamlit.io`.
  - Go to **GitHub → Settings → Applications → Authorized OAuth Apps → Streamlit** and click **Revoke**.
  - Sign back into `share.streamlit.io` with **Continue with GitHub** (`manosv18`) so GitHub issues a fresh OAuth token with full repository write permissions.

2. **Re-bind the Deployment Record (Takes 30 Seconds)**:
  - If the Secrets box on the existing deployment still loads read-only after step 1, click **Delete app** on the Community Cloud dashboard (this only removes the cloud container instance, your `manosv18/managers-lab` GitHub repo is untouched) and immediately click **Create app** → select `manosv18/managers-lab` (`main`).
  - Creating the deployment under your freshly connected `manosv18` identity immediately unlocks the **Secrets** text area and enables **Save changes**.