Getting started
Accounts and organizations
One account signs you in to every app. Everything you build belongs to an organization, and your role there decides what you can do.
Get an account
Accounts are created from invites. An owner or admin of an organization invites you by email; the invite link opens id.cactive.com.au, where you:
- Are new: enter your name and date of birth and choose Create a Passkey and Join: your device makes a passkey and the account is created with it, for the invited email address. Or choose Use a Password Instead and set a password (at least 12 characters).
- Already have an account: sign in first, with the email address the invite was sent to, then accept.
Your date of birth is private to your account and set once (support corrects it). It isn't on your profile, and apps never see it: they only learn whether you're old enough for something, such as Sexual Activity in Health (18 and over). Accounts made before sign-up asked for it are asked once, at https://id.cactive.com.au/date-of-birth, the first time an app needs it, and go straight back.
Invite links work for 7 days. New customer organizations are set up by the platform team, which invites the first owner.
Sign in
Sign in at https://id.cactive.com.au with a passkey (Sign In with a Passkey, or pick it from the email field's autofill) or with your email and password. While your account has only a password, signing in suggests adding a passkey or an authenticator app (Securing your account). Each app (Cloud, Git, Caity) sends you there when you need to sign in, asks which account to use when you're signed in already, and brings you back. See Sign-in and sessions.
Organizations
An organization owns Serverless App Services, repositories, storage, domains, agents, connectors and knowledge pages. You can belong to several; Cloud and the Git portal list what each one has, and the organization menu in Cloud switches between them.
Your account page at https://id.cactive.com.au lists your organizations. Open one to see its members, groups and (for owners and admins) its keys. Owners and admins administer it in Tenant.
Roles
Every member has one role per organization:
| Role | Can |
|---|---|
| Owner | Everything in the organization, including managing owners and the sign-in policy. |
| Admin | Everything an owner can, except managing owners and the sign-in policy. Invites and manages members, groups, roles and keys in Tenant, approves agents, manages connectors, reads the audit log. |
| Developer | Read everything (except the audit log and Tenant); create and change Serverless App Services, deployments, environment variables, domains, storage and repositories; write knowledge pages; queue agent jobs. |
| Viewer | Read everything (except the audit log and Tenant) and use Caity. |
Roles map to scopes, which the platform checks on every request. A group can give its members a higher role, and custom roles add specific scopes.
Groups
Groups (teams) gather members inside an organization. Owners and admins create and delete them in Tenant; a group's owners add and remove members. A group can give its members a role, custom roles, write access to Serverless App Services and repositories, and access to apps.