Accounts and sign-in
Choose account types, configure sign-in and manage account lifecycle.
An account determines who someone is and what they can access. A sign-in method determines how they prove it is their account: an email link, FreeIPA credentials, a passkey or approval in a paired app.
Configure installation-wide policy in Administration → Accounts & sign-in. Create and manage individual users, groups and requests in Accounts. People manage their own devices in My account → Security.
Use the avatar menu to open Profile settings or Sign out. Signing out ends the current browser session.
Choose Deutsch or English beside the legal links on sign-in and recovery pages. The choice also applies after sign-in and is saved in this browser.
Before your first use
After signing in, review and accept this Cloud's terms and acknowledge its privacy policy. This is required once, regardless of whether you sign in with an email link, FreeIPA, a passkey or a paired app. Until you confirm, you cannot open applications or use the new session for API access. You can cancel and sign out instead. Later sign-ins continue directly to your destination.
Operators configure the documents under Administration → Legal. Configure them before inviting users. Existing sessions remain valid after an upgrade; accounts without a recorded acceptance are asked at their next sign-in.
Start with your scenario
- Cloud-managed accounts only: allow Login, give it your company label, and disable Guest and FreeIPA in Account types.
- Invited guests: allow Guest, leave self-registration off, and optionally hide Guest from the general login page.
- Existing FreeIPA directory: connect FreeIPA, review group scope and keep its account category allowed.
- Use an authenticator app: configure app sign-in, then pair a device. This works for eligible local and FreeIPA accounts.
Choose a task
| Task | Guide |
|---|---|
| Choose allowed accounts and visible login entries | Account types and sign-in |
| Allow registration or FreeIPA requests | Registration & requests |
| Connect a directory and control synchronization | FreeIPA |
| Configure the authenticator website | App sign-in |
| Pair, rename or revoke a device | Devices |
| Assign UID/GID, home and shell | Linux identities |
| Configure expiry, reminders or run maintenance | Account lifecycle |
| Show manual follow-up instructions | Notices after changes |
| Point help links at your own documentation | Documentation website |
Linux identities add UID/GID, home and shell attributes to accounts. Assigning them does not enable computer login, sudo or shared storage.
Application authors should use Identity and access. Authenticator authors should use the App approval API.