Users and invites

Users and invites are managed by the server operator with the server's admin CLI.

Inviting someone

crewdesk-hub invite add --email sam@example.com --note "Pilot"   # open 7 days; --days 0 never expires
crewdesk-hub invite list                                          # open invites; --all for used, revoked, expired
crewdesk-hub invite revoke --email sam@example.com

E-mails of a domain the server allows need no invite. Everyone else is refused at sign-in with a message saying why (not invited, invite expired, access revoked).

Then send the person what they need: the installer line for your server, and the reminder to sign in with that e-mail and to link their own AMP organization. See What you need.

Checklist for a new user

• They signed in and accepted the consent (crewdesk-hub user list).
• Their limits are right (crewdesk-hub limits). By default: 2 turns at once, 30 turns an hour, 3 rounds of server calls per turn and a daily token budget (a warning at 100%, refused at 120%).
• Their turns run where you want (crewdesk-hub brain): on the brain on AMP, or on the server itself.

Ending access

crewdesk-hub user revoke --email sam@example.com

This revokes every token of theirs, ends their running turn at its next check, removes their AMP link and stored credentials, closes their invites and writes an audit row. Ask them to regenerate their Enterprise Action Token in AMP (the server's copy is already deleted).

After 30 days, crewdesk-hub user purge --email … deletes their chats, files, memories, pending approvals and usage detail (daily totals and the audit log stay); --force purges sooner, for a deletion request.

A revoked user can come back with a new invite, with their old data if it wasn't purged.