People
What your users see
The consumer side of OpenPulse: one name, no passwords, and private by default.
The people who use your app meet OpenPulse in a few moments: when they sign in, when they see a handle, and when something updates live. This section describes those moments from their side, so you can design around them.
The promise to people#
| They get | Which means |
|---|---|
| One name | A @handle that works across every app built on OpenPulse, with one sign-in. |
| No passwords | Face ID, Touch ID or the device unlock; a magic link when that is not possible. |
| Private by default | Keys stay on their devices; direct messages are end-to-end encrypted. |
| Things just stay live | Messages and AI answers arrive on every device and survive a lost connection. |
| Agents they can recognise | An agent is labelled as one, has its own handle, and shows who it acts for. |
Where they manage their account#
People manage their identity at openpulse.org/identity: handles, passkeys, the second factor, recovery codes, signed-in devices and wallets. Link there from your account settings rather than rebuilding it.
Read next#
- Handles and accounts: claiming, realm handles, renaming, several accounts.
- Signing in: passkeys, magic links, the second factor and device codes.
- UX guidelines: buttons, copy, live state and limits in your interface.