Why a new workspace starts pending

On this page

Why this happens
Who is affected
What is blocked while pending
What to do while you wait
If your account is not approved

You complete the setup wizard, your organisation and entity are created successfully, and then you land on a screen saying your account is awaiting approval. This is intended behaviour, not a failure.

Why this happens#

Governax receives read access into an organisation's identity provider, source control and cloud accounts. Reviewing who is standing up a workspace before that access can be configured is a deliberate control on the Governax side.

Every account carries an approval status of approved, pending or rejected. It defaults to approved and cannot be set from anything you submit. Creating your first organisation is what flips it to pending.

Who is affected#

Who the approval gate applies to
Situation	Result
You create your first organisation	Account goes to pending
You already have an approved account and create a second organisation	Stays approved, no new review
You accept an invitation to an existing organisation	Stays approved, never sees this screen
You are a Governax platform administrator	Bypasses the gate entirely

The practical consequence: only the person who first stands up a workspace waits. Everyone they invite afterwards walks straight in.

What is blocked while pending#

The gate returns HTTP 403 with the error code PENDING_APPROVAL on the surfaces that matter:

Reading or updating the organisation, and listing its members
The entire ledger surface, including the live feed and verification
The entire integrations surface, so no connector can be attached

Entity routes are deliberately left open, because creating the first entity is the last step of the wizard and it happens after the flip. If that were blocked too, onboarding could never finish. In practice you will not notice, because the application redirects you to the pending screen before rendering any of the product.

What to do while you wait#

The pending screen re-checks your status when it loads and whenever you press "Check again". Approval takes effect immediately: your status is read fresh from the database on each request, so there is no need to sign out and back in, and no cache to wait out.

There is nothing to configure or resubmit on your side. If the wait is longer than you expect, contact support with the organisation name you registered.

If your account is not approved#

A rejected account sees a different message and loses the "Check again" button, because re-checking will not change anything. The remaining actions are contacting support and signing out. Rejection does not delete the organisation or anything in it.

For the other states that can block access, including organisation suspension and account-level bans, see When access is blocked.