> For the complete documentation index, see [llms.txt](https://docs.zephyrintel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zephyrintel.com/administration-zephyr-staff/simulate-a-user/what-simulation-changes.md).

# What simulation changes

Starting a simulation switches several things at once, so what you see matches what the simulated user would see.

* **Organization scope**: every request Signal makes is scoped to the simulated user's organization, the same way it would be if that user were signed in.
* **Staff access**: your own staff identity is set aside for the session. You lose access to Organization Admin until you stop simulating.
* **Cached data**: Signal clears its local cache and reloads data under the simulated user's scope, so you are not looking at a mix of your own cached data and theirs.
* **Feature flags**: features that are turned on or off per organization are evaluated for the simulated user's organization, not yours.
* **New data**: anything you create while simulating, such as a new asset or customer, is attributed to the simulated organization and follows that organization's ownership policy, not your own.

### Where you see it in Signal

The amber **Simulating user** banner stays visible at the top of every page while a simulation is active, so you always know you are not looking at your own account.

### Notes

* Stopping the simulation restores your own staff session and clears the cache again, so the next page load reflects your own scope.