Add staff logins for an inbox

Add a login directly#

Open your project > Database > Tables & records. Select a Form inbox. In Staff login table, enter a name, email, and unique 12–128-character password, then click Add login. The manager controls these rows. No public signup is offered. Passwords are hashed on the server and never returned.

Sign in on your website#

Use the custom staff login example in Build your own login page. POST /__cloudauro/staff/login with {email,password}, X-CloudAuro-Staff: 1 and same-origin JSON. The browser stores a host-only HttpOnly SameSite=Strict session cookie; production uses Secure cookies. Sessions last 12 hours. GET /__cloudauro/staff/me checks the login; POST /__cloudauro/staff/logout signs out. Login attempts are limited by IP and email.

Read requests#

A staff login can read only its assigned Form inbox using the existing CloudAuroData SDK or same-origin /__cloudauro/data/TABLE/rows endpoint. It cannot edit/delete requests or manage CloudAuro. Staff login pages and static files are public; the server protects inbox data.

Reset or disable access#

Use New password > Reset password on the row, or Disable login. Both revoke existing sessions. Enable login allows future sign-ins. There are at most 20 staff rows per database. Staff credentials are excluded from customer data snapshots; operator database backups include them.

Previous visitor accounts#

Website accounts has been retired. Its signup/login pages, SDK, and management APIs are unavailable. Existing visitor credentials are retained only as inactive archived records. Old visitor sessions are revoked, and former Member data tables become Private without deleting their records. Use custom tables for data and manager-created staff logins for private inboxes.