Skip to content

Organisations and access ​

An organisation is an independent workspace for a team. It owns its apps, deployment channels, signing configuration, releases and test devices. All organisations can use the same hosted OTA server.

Two portals, one account ​

PortalWho uses itWhat it manages
/super-adminPlatform super adminsOrganisations, organisation managers and other super admins
/adminOrganisation administrators and membersApps, Staging/Production, publishing, monitoring, rollback and app access

Use the same email and password in both portals if you hold both roles. Sign in separately. Each portal has its own cookie and server-side session, and signing out of one does not sign out of the other. Changing your password or MFA settings revokes both sessions.

Super-admin status does not automatically make you an organisation member. Assign yourself membership if you also need to manage that organisation's apps. Platform administrators can grant themselves that membership; these changes are audited. This is a shared platform with access controls, not infrastructure isolated from its server operators.

Create an organisation ​

  1. Sign in at /super-admin.
  2. Select Manage organisations → Create organisation.
  3. Enter the organisation name and its administrator's email.
  4. An existing account gets access immediately. For a new person, copy the private invitation link and send it to them.

The new administrator signs in at /admin, selects their organisation and creates an application for each native platform. Every new application gets its own Staging and Production deployments. Follow its setup guide to connect the mobile project.

Add another super admin ​

At /super-admin, open Super admins → Add super admin. Enter the person's email, confirm your password and provide an authenticator or recovery code if MFA is enabled.

An existing account receives platform access immediately. A new person receives a one-use invitation link to create their account. They can then sign in at /super-admin, create organisations and appoint administrators. Grant this role only to people who should control the platform.

Removing super-admin access takes effect on the next request, including in an already-open session. It does not remove separate organisation memberships. The last super admin cannot be removed.

Organisation roles and app access ​

Role or app accessPermissions
Organisation administratorManage the organisation's team and all existing and future apps, signing settings, channels and releases
Organisation memberView the organisation's team and all its existing and future apps and deployments; cannot change the organisation or team
ViewerDefault access to each organisation app's releases, monitoring, activity, native registrations and test-device list
PublisherView and publish, promote, edit, pause and roll back updates for a particular app

Organisation administrators use Organisation team to add people, change roles and remove organisation membership. Adding a member gives them Viewer access to every app and deployment in that organisation automatically, including apps created later. There is no separate app assignment step. Apps in other organisations remain inaccessible unless the person also belongs to those organisations.

To allow publishing, open an application's App access screen, find the member, select Publisher, then choose Save access. This grants publishing rights for that app only. For example, someone can be a Publisher for your iOS app and a Viewer for your Android app. Organisation settings, team membership, app access, application creation and deployment configuration remain administrator controls. Members see the team overview without pending invitation links or organisation management activity.

Viewers cannot publish from the dashboard or terminal, change releases, register native builds, approve or remove test devices, change signing settings, or create publishing credentials for that app. They can still manage their own account security. These restrictions are enforced by the server, including for requests sent outside the dashboard.

You can belong to several organisations. Use the organisation selector before choosing an app. Apps may have identical names in different organisations; their identities and keys remain separate.

The organisation-level Savings screen is visible to every member, including before apps are created. It automatically compares recorded monthly usage with published Revopush pricing in USD. There is no cost-entry form; administrators and members both see a read-only estimate. Super-admin status alone does not bypass organisation membership.

Use App access to change a member between Viewer and Publisher. Choosing Viewer and saving, or selecting Remove Publisher access, removes their publishing rights and revokes their scoped publishing credentials for that app. The person remains a Viewer through their organisation membership; the app and its deployments stay visible. The next request from an existing session uses the new permissions; a publication that has not yet committed must pass the permission check again. Re-granting Publisher does not revive revoked tokens.

To remove read access, remove the person from Organisation team. This removes access to every app and deployment in that organisation and revokes their publishing tokens for those apps. Re-adding them restores default Viewer access but does not revive old Publisher grants or tokens. Other organisations are unaffected. Demoting an administrator to Member removes administrator privileges while retaining default Viewer access to all organisation apps and any explicit Publisher grants. The last organisation administrator cannot be removed or demoted.

If an organisation has no apps yet, members see an empty state explaining that an administrator must create the first app. Members cannot create apps or deployments. Their account security settings and read-only team overview remain available.

Terminal publishing ​

Copy the setup command from the correct app's dashboard. It includes the organisation identifier automatically. Terminal sign-in uses your organisation-dashboard account and supports MFA. Every publish checks your current organisation and app permissions. Signing in alone does not grant publishing rights: you need Publisher access to that app or the organisation administrator role.

The project configuration saves the immutable app ID and organisation ID. Signing keys remain scoped by server and app ID in private storage outside your project. Renaming an organisation does not change its ID, app IDs, deployment keys or signing keys.

An old configuration without an app ID can still use an unambiguous app name. If a name resolves to multiple organisations, the server returns an error instead of guessing. Recover or update the configuration with the current dashboard setup command. Explicit store version targeting and automatic public-store lookup behave as described in Store version detection.

A scoped OTA_TOKEN can publish only to its authorised app/deployment. It cannot create organisations, manage members or enter /super-admin.

Invitations ​

Invitations expire after 48 hours and work once. Reissuing an invitation invalidates the old link. Administrators can revoke pending invitations. This deployment generates copyable links; it does not send invitation emails.

The recipient chooses their own password. If the account already exists by the time the invitation is accepted, the recipient must sign in with that account. An invitation cannot reset an existing password or be accepted by another email address.

Invitation tokens are stored as hashes. The link token is a URL fragment, which is not sent in HTTP access logs or referrer headers. Share it privately. Invitations from an administrator who no longer has the required management access cannot be accepted.

Existing installations and migration ​

The organisation upgrade creates one organisation per existing app owner. That owner becomes its administrator. Existing collaborators retain their publishing access only to the apps they already had, now labelled Publisher in the dashboard. Organisation members automatically receive Viewer access to the organisation's other apps and deployments. The API continues to use Collaborator for the publishing permission; Viewer is the inherited read-only permission. App IDs, signing keys, deployment keys, releases and native configurations are preserved; this change does not require a new mobile build.

Existing accounts without apps remain accounts and can be added to an organisation. There is no public registration and no automatic first-user super-admin privilege.

The server operator grants the initial super admin explicitly:

sh
npm run console:operator -- set-super-admin you@example.com

Run this inside the configured API environment, after creating the dashboard account. Once bootstrapped, use the super-admin portal to manage additional platform administrators.

The database schema remains version 3. Default Viewer access is derived from organisation membership, separately from explicit publishing grants. Older Viewer assignment records remain compatible but are no longer needed to make an organisation's apps visible. Reverting to a preceding version-3 server can reduce read visibility to the app assignments that version understands; it does not grant publishing rights. Existing Publisher and administrator access continues to work. The deployment pipeline checks that the previous image can open the upgraded database before switching traffic.

Take a consistent SQLite backup before upgrading. Images from before the organisation upgrade deliberately refuse schema version 3. To revert to one of those older images, stop the server and restore the pre-upgrade database into a new path, then run the old image against that restored database. Updates written after the backup must be reconciled before rolling back. This is separate from rolling back a mobile OTA release, which still works from the dashboard.

Signed React Native updates. Self-hosted on your infrastructure.