> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/connect-and-authorize/add-write-access-to-an-existing-connection.md).

# Add write access to an existing connection

Reauthorize a Podigee connection with the exact write permissions required for a task.

Replace or reauthorize a read-only connection when the intended Podigee task requires write access.

## Before you start

* Identify the task and its required scopes.
* Confirm that the connected Podigee account is correct.
* Finish or record any active operation before you change the authorization.
* Do not grant media or listener access when the workflow does not need it.

## Check the current access

Ask the agent to report the connected account and scopes. You can also run a Podigee health check with write readiness enabled.

If the result names a missing scope, record that exact scope. Do not add unrelated permissions.

## Reauthorize a browser connection

1. Open the app or connector settings in the AI application.
2. Disconnect the Podigee connection when the application cannot request an access upgrade in place.
3. Connect Podigee again.
4. Review the selected Podigee account.
5. Review the expanded permissions.
6. Approve only the permissions required for the task.
7. Run a read-only account check before you make a change.

Reauthorization creates a current authorization. It does not make an old preview confirmation valid again.

## Replace a personal access token

A token's scope set does not expand after creation. Create a replacement token with the required scopes, update the protected client secret, verify the replacement, then remove the old token.

## Expected result

The current connection reports the required write scope and the correct account. A dry run of the intended write tool returns a preview instead of an `insufficient_scope` error.

## If write access is still unavailable

Run the Podigee connection health check. The account can remain read-only because of subscription, rollout, account permission, plan, or product readiness. Do not retry a write that the health check reports as unavailable.

## Next step

[Preview a change before it runs](/documentation/start-here/ai-agents/make-changes-safely/preview-a-change-before-it-runs.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/connect-and-authorize/add-write-access-to-an-existing-connection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.