# Remove access when someone leaves

Source: https://zotonic.com/docs/3056/remove-access-when-someone-leaves

URI: https://zotonic.com/id/3056

Language: en

Remove login methods and permissions without deleting their authored content.

**Access needed:** Site administrator; identity-provider or integration access may also be needed.

First identify the person, the accounts they use, and which content or responsibilities need transferring.

1. Review their user groups, collaboration memberships, API credentials, and any external sign-in method.
2. Remove the memberships that grant access and save.
3. For a local username/password account, open **Set username / password** and choose **Delete Username**. Read the confirmation carefully.
4. Disable the account at an external identity provider and revoke separate integration tokens where applicable.
5. Arrange invalidation of existing sessions with the site's authentication administrator; removing a password alone is not proof that every existing session is gone.
6. Test that the former access methods fail and that the replacement owner can still do the work.

Keep the person resource when it is needed for authorship or records. Unpublishing a person page is not an account-deactivation procedure. Do not delete their content merely to remove a login.

The built-in `admin` account is configured separately; this username-deletion dialog does not manage it. Handle emergency administrator credential rotation through site configuration.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/3056?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/3056?language=en>)
