Onboarding Hub
On the [Settings > Onboarding Hub] page, you can get a new workspace ready in one continuous flow — connect a cloud account, confirm resources are being collected, and map those resources onto applications.
Onboarding Progress
The card at the top counts how many of the three steps are done — 1 of 3 Steps Completed — above a progress bar. The three steps do not have to be done in one sitting — the hub remembers what is finished and picks up where you left off.
| Step | Purpose |
|---|---|
| 1. Connect Account | Link a cloud provider account to CloudOps |
| 2. Verify Collection | Confirm resources are actually arriving from the connected accounts |
| 3. Map Application | Classify the collected resources into applications |
Progress Tracker
Each step shows its own state and a one-line summary of what it means right now.
| State | Meaning |
|---|---|
| Completed | The step is done. The summary tells you what to review — for example Cloud account connected successfully. Check the details of your connected accounts. |
| Incomplete | The step still needs attention |
Click any row (or its > chevron) to jump straight into that step, whether or not it is complete.
Recommended Action
The panel on the right names the single next thing worth doing and gives you a button for it — for example Step 2. Verify Collection with a [Verify Collection →] button.
Step 1 — Connect Account
Register the cloud account CloudOps will read from. For what has to be prepared on the provider side first — IAM policies, roles, service accounts — see the Cloud Account Integrations guides.
Step 2 — Verify Collection
Check that resources are genuinely being collected from the account you just connected. This is the step that catches a credential that authenticated but lacks read permission — the account looks connected, yet nothing arrives.
Collection Status and Last Collected carry no meaning — leaving them in would make a healthy setup read as a row of failures.Step 3 — Map Application
Collected resources start out unclassified. Mapping puts them under applications so that cost, findings, and tickets can be attributed to something meaningful.
There are three ways to do it, and they combine:
Create an application
Add the application the resources belong to, so there is something to map onto.
Create a mapping rule
A rule classifies resources automatically by their attributes, and keeps classifying the ones collected later. This is what you want for anything that will keep growing.
Assign manually
Pick resources and attach them to an application directly. Useful for one-offs and for whatever the rules did not catch.
After onboarding
Once all three steps are complete, the hub stays available as a status view — a quick way to confirm collection is still healthy after adding another account later.