First-Administrator Setup, Sign-Up Rules and App Connections for the Iternal Platform, in Development

A new deployment gets its first administrator through an explicit setup step, so ownership starts with a named person. A signed-in person generates the code and the deployment operator redeems it; the code is short-lived, single-use and tied to that person and deployment. People who sign in with a company account can then add a first local password, which needs a verified email address and ends their active sessions so they sign in again. In development; applies to new deployments.

Deployment owners list the company email domains and individual addresses allowed to sign up for themselves, or leave registration open. The rule applies from the start of sign-up through to completion and to new accounts; existing accounts and sessions are unaffected. People an organization invites or an operator enrolls are admitted separately. In development; set by the deployment owner in the deployment's configuration.

Each connection is independent, belongs to one organization and workspace, and can be renamed, reduced in permissions or disconnected. People approve the subset of permissions an app asks for, and disconnecting ends a connection for good. Permissions cover read and use access to Chat, and an administrator registers each app first. In development; limited to new deployments.