Docs / Hosting OwnBase

Invites

When the workspace takes people with an invite only (--invite-only on a new workspace, or People with an invite in Workspace settings), everyone after the owner needs an invite code to create an account. Owners and administrators can make codes from Invite people. A member needs an administrator to select People → Allow inviting first; Stop inviting removes that permission. Apps cannot create invite codes. The dialog's codes last seven days. The same dialog lists codes: every code for an administrator, and only their own for a member, since a code is what lets a stranger in. Each shows how many times it has been used and whether it still works.

Revoke stops a code letting anyone else in, for one that has been shared further than meant. Its creator or an administrator can revoke it; a member who tries someone else's is told there is no such code, so trying codes cannot confirm which exist. A revoked code stays in the list, marked as revoked.

A code also stops working while its creator is deactivated or cannot invite. Restoring access and permission makes their unexpired, unused codes work again; revoke a code if it should stay dead. Members can still list and revoke their own codes after losing permission to create more. Codes are left out of the request log.

Schema v25 starts all members without an explicit invitation grant, including existing members during an upgrade. Their previously issued codes pause until an administrator allows them to invite. Owner/admin codes continue to work. Demoting an administrator removes the permission their role supplied; any explicit member grant they held before promotion remains until removed.

Otherwise anyone who can reach the server can create an account, and a code is not asked for.

This page is made from docs/DEPLOYMENT.md.