Compute
Set up a Compute organization
Choose the legal account, name an administrator, and set one policy before anyone submits work. Add the optional enterprise resources later, and read back every change.
Before you start
Decide three things before you touch the portal: which legal entity holds the account, who administers it, and which workflow the team runs first.
You also need authority to accept commercial terms for that entity. If you do not hold it, name the person who does before you begin.
Choose the legal account
The organization resource carries the legal name, the billing contact and the commercial terms. Get it right at creation, because invoices and receipts inherit it.
Describe the organization resource, plan the values you want, apply, then read the applied resource back. If the read-back does not match the entity on your contract, fix it before inviting anyone.
Name the administrator
Name at least one administrator who is not you. A single administrator is a single point of failure for key rotation and member removal.
Administration and work submission stay separate. An administrator credential manages members, identities and destinations. A work key submits jobs and does nothing else.
Invitations are not reversible by a configuration rollback. Withdrawing an invitation is its own action, taken forward.
Set one policy before work starts
Set the organization spend ceiling and the approval rule that admission checks against. Do this before the first member joins, so nobody can run work against an unset limit.
Choose one default data policy for the organization. Members can narrow it per workflow later, but they can never widen it.
Stage the optional enterprise resources
Everything below is optional. Add each one when a workflow or an audit actually requires it.
- Directory sync and role mappings, once you want membership managed outside the portal.
- Schedules and event triggers, once a workflow needs to run without a person present.
- Cost allocation and finance mappings, once you need spend split by project or cost center.
- Reusable workflow profiles, once two teams need the same defaults.
Staging them is not deferral for its own sake. Each resource you register is a resource you must review, rotate and revoke later.
Read back every applied resource
An apply is not finished when it returns. It is finished when the resource reads back.
Each resource returns its own state. VERIFIED means the applied value was read back and matched. APPLIED_UNVERIFIED means the write happened but the read-back has not confirmed it yet, so wait and read again.
The change as a whole returns COMPLETE only when every resource verified. PARTIAL_WITH_NEXT_ACTION means some resources verified and the rest name what to do.
When a resource refuses
Read the reason and the next action together. REFUSED needs a different input. CONFLICT means the resource changed since your plan, so inspect and replan.
Verified resources stay verified when a later one refuses. Resume from where the change stopped rather than starting the whole setup again.