Documentation

Console

Users

The Users table matches the Apps console: search, filter, sort, download, and a detail slider. The extra action is New user.

What New user actually does

It does not create a password and it does not invent a new LoginSign account. It puts an email on the organization list. That person then signs in with the existing LoginSign social login (Google, Apple, GitHub, and the other methods enabled in Settings).

  1. Admin opens Users and clicks New user.
  2. Enters a name and the email that person already uses at Google / Apple / GitHub.
  3. Optionally assigns roles. Admin lets that person open the console and change everything.
  4. The row appears as Invited. Sessions stay 0 until they sign in.
  5. They open the organization login (/org/:slug/login or the custom domain) or sign in on bookmer.com. bookmer.com sends a single membership straight to the organization and several memberships to /org/choose.
  6. If the provider email matches, they get in. The row becomes signed in and links to their LoginSign account.
  7. If the email does not match, they stay out. Social login alone is not enough.

Why there is no password

LoginSign already is the login. The organization login shows the same providers as Settings. Adding a user is an allow-list. Removing or disabling a user takes that email off the list.

Status

  • Invited — on the list, has not signed in yet.
  • Signed in — organization login succeeded with that email.
  • Disabled — still listed, cannot open the collection.

Windows username and authentication code

These fields are only used for Windows / workplace login (Enterprise, on-premise). They do not change Google, email, or passkey sign-in.

  • Windows username — DOMAIN\user or the short account name. The reverse-proxy header must match this mapping.
  • Authentication code — stored as a hash. Set, replace, or clear it from the user slider. Whether the login page asks for it is the On-premise policy.

Full integration steps: Authentication codes.

Seats

The table header shows used seats versus the live plan limit. New user is disabled when no seats remain or when the organization is locked for billing. Adding or re-enabling a member past the limit returns MEMBER_LIMIT.

Sharing with members

Members can share only folders and links they created themselves, and only with other people on this Users list. Blueprint items are not shareable and are never published as a public page.

Owner API

GET    /api/developer/teamspaces/:id/members
POST   /api/developer/teamspaces/:id/members
PATCH  /api/developer/teamspaces/:id/members/:memberId
DELETE /api/developer/teamspaces/:id/members/:memberId

POST body: { name, email, permissionNodeIds?, windowsUsername?, authCode? }.PATCH body: { name?, status?: "ACTIVE" | "DISABLED", permissionNodeIds?, windowsUsername?, authCode? }.authCode: null clears the hash. Responses include authCodeSet, never the code.