LogSureTeams and sign-in
Invite your team with a link, give each person a role, limit them to the apps they work on, and see who changed what. Everyone signs in with a password and two-factor, or with a passkey.
Roles
| Role | Can |
|---|---|
| Viewer | Read everything, including the inbox and waitlists with email addresses |
| Member | A viewer, plus request and signup statuses, notes, deleting and archiving, error triage, and exports |
| Admin | A member, plus app settings, rules, segments, funnels, experiments, feature flags, feature switches, apps and server keys, privacy requests, AI access, and the team and audit log |
| Owner | Everything. There is one owner, who cannot be changed or removed by an admin. |
Devices, AI connections, your profile, two-factor and passkeys are each person's own. AI keys and connections are capped by the person's role: a viewer's can read analytics and the inbox, a member's can also change, and only admins and the owner can give the settings access.
Settings › Team
- Invite: choose a role, optionally the apps, and how long the link works (48 hours by default, up to a week). The link is shown once; send it yourself. Whoever opens it picks a username and password and joins.
- Per-app access: a member or viewer limited to some apps sees only those, everywhere: the overview, the inbox, the waitlist, the bell and the API. Other apps answer as if they did not exist.
- Change or remove: change a person's role or apps, sign them out of every session, device and AI connection at once, or remove them.
- Require two-factor: turn it on, and anyone without two-factor can only set it up until they do. A passkey counts.
- Audit log: who did what and when: sign-ins, team changes, settings, keys, feature switches, imports, experiments and more, newest first.
Two-factor sign-in
Under Settings › Security, turn on two-factor with an authenticator app and keep the recovery codes. Pairing the iPhone, Mac and terminal apps and turning on the MCP server need it, because devices and AI connections skip the password and the code.
Passkeys
Add a passkey under Settings › Security (it asks for your password, and your code if two-factor is on). Then sign in with it from the sign-in page, which offers your passkeys as soon as you click into the username field. A passkey checks that it is you on the device, so it stands for both the password and the code.
- Up to 20 per person, each with a name and the provider it is kept in (such as iCloud Keychain, Google Password Manager, Windows Hello, 1Password or Bitwarden) and whether it syncs.
- Browsers allow passkeys only over HTTPS or on
localhost. They belong to the console's host (CONSOLE_HOST), and stop working if it changes. - When the team requires two-factor and a passkey is your only second factor, sign in with the passkey.
Not built yet: transferring ownership, and single sign-on with OIDC or LDAP.