Name the outcome before changing the user
Three requests can sound similar: remove a name from the television login screen, stop a person using the server, or let a cataloguer inspect items without playing them. They need different controls. Start with the intended outcome and identify the exact local user, especially where several household accounts have similar display names.
Use the control with the required effect
In Emby’s user settings, hiding an account removes it from visual login screens; the person can still enter their username and password manually. Disabling a user terminates that user’s existing sessions. Separately, Allow media playback can be turned off for an account that should browse the library without playing media. These documented effects explain why hiding a tile does not accomplish account suspension and why a visible library does not always imply playback permission.
Check the intended account after the change
Suppose an administrator is preparing a read-only catalogue review for a collaborator. They should examine the playback permission for that collaborator rather than disabling the account and then treating failed sign-in as a player error. Conversely, an account that should stop accessing the server needs the relevant access decision, not just a tidier login screen. Record the control changed and verify its expected result using that account. If other permissions are also being adjusted, list those separately so that a later support request can explain which result came from which choice.
Questions, answered
Does hiding an Emby user revoke their login?
No. Hiding removes the visual login tile; the user can still enter credentials manually.