Accounts that activate when you use them¶

When a large organization joins the platform, every site, store, branch or warehouse becomes its own account. Setting all of them up front would take hours and most of them are not needed on day one, so the platform creates them pending and finishes setting each one up the first time somebody actually uses it.

Nothing is missing or broken while an account is pending. It is a normal step.

What the statuses mean¶

Status	Shown as	What it means for you
Pending	`PLACEHOLDER`	The account exists and is in your organization structure, but nobody has been given access to it yet. It cannot be used yet.
Activating	`MATERIALIZING`	Somebody just granted the first access. This lasts seconds — refresh and it will be active.
Active	`ACTIVE`	Ready to use. People can sign in to it, and it can be managed like any other account.
Closed	`CLOSED`	Retired. Its history is kept for auditing; it can no longer be used.

The middle column is the exact value the platform reports, which is what you type when filtering a list.

How a pending account becomes active¶

Give someone access to it. The first time you assign a person — through an Identity Center permission set — to a pending account, the platform finishes setting it up and the account becomes Active. That is the whole trigger: staff the location, and the location comes to life.

Adding a machine credential is a separate step. If that account also needs a service user (an application or robot signing in with an access key rather than a person), creating the first one sets up an extra piece the account did not need before. Most accounts never need this, and never get it. See Service users.

The two are independent. An account staffed only with people is fully active and will never need the machine part.

Where to check an account’s status¶

In the application your organization was onboarded through. If a partner application set up your organization, its own site list is the place that shows which locations are live and which are still pending.

With the FGAI CLI, if you use it:

fgai org account-lifecycle --org <your organization>
fgai org account-lifecycle --org <your organization> --status PLACEHOLDER

Organization at https://console.flexgalaxy.ai/organization shows your organization’s structure — its organizational units and the accounts in them — so you can confirm a location exists and where it sits.

Retiring a location¶

A location that has been used is closed, not deleted. Closing keeps its history for auditing.
A location that was created but never used can be removed outright, because nothing was ever set up for it.

If a removal is refused, the account has already been used at least once — close it instead.

“Opening the app took me to a setup page”¶

Applications can declare a separate first-run page. When you open one, the platform checks the account you are entering: if it is still pending, you are sent to that setup page instead of the normal home page. Once the account is active, the same link takes you straight into the application.

If a colleague went straight in and you did not, their account was already active and yours was not — not a permissions problem.

If the application says the account is closed, it cannot be opened at all. Ask your administrator to use a different account.

Still stuck?¶

“I was given access but the account is still pending.” Give it a few seconds and re-check. If it stays pending for more than a minute, contact FlexGalaxy support — the setup step needs to be re-run for you.

“I can see the location but cannot select it.” It is pending. Someone needs to be assigned to it first; see Where to manage each identity.