---
url: https://docs.repoos.org/native-auth.md
---
# Native authentication

RepoOS native authentication controls which email addresses can sign in to a
repository and which role each address has. Telegram uses those same existing
accounts; it does not create a separate allowlist or role system.

For setup, login methods, sessions, roles, and managing the allowlist, see the
[Authentication guide](/authentication). For the identity and authorization
decision behind Telegram, see [Telegram](/telegram) and the
[native authentication architecture notes](../docs/native-auth.md).