> For the complete documentation index, see [llms.txt](https://streamsmanager.gitbook.io/streams-manager/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://streamsmanager.gitbook.io/streams-manager/plex-bans/requiring-users-to-change-their-plex-account.md).

# Requiring users to change their Plex account

Streams Manager now allows admins to tag their users to force them to change their Plex account before they can subscribe or be re-invited to your Plex server. This can be very useful if your Plex server has been banned and you provisioned a new server and want to get your users on the new server.

This feature is available on the Users page using the `Edit` individual user option or via `Bulk Edit` functionality. Once you tag a user as required to change their Plex account, users will get a banner on the My Account page instructing them to change their Plex account and be given a button `Change Your Plex Account` to do this. They would simply enter the new Plex email address and the system will verify it, make updates in the system to use the new Plex account and re-invite the user to one of your Plex servers.

Also, ensure that Plex account change processing is enabled in `Settings->Miscellaneous.`


---

# 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://streamsmanager.gitbook.io/streams-manager/plex-bans/requiring-users-to-change-their-plex-account.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.