Set up Nova for your team
Rather not read it all? Ask Nova this. It walks you through each step.
Nova with your rules: what it may do, who approves, and an audit trail of every change.
Who does what: Alice (platform engineer, org owner) sets the rules and approves.
You need Nova access, and your apps deployed through AstroPulse.
1. Alice connects Nova to the platform
In Nova > Skills > Discover, Alice connects AstroPulse (Skills).
2. Alice sets what Nova may do, and who approves
In Nova > Settings > Guardrails, open a category to move it. Under Who approves, set Who may approve a change to Owners and admins only, and pick whether to Approve from Slack. Every category and its default: Guardrails and Approvals.
3. Alice tells Nova how the team works
In Nova > Settings > Instructions, write where services live, who to page and what never to touch, then select Save instructions (what instructions do). On the Enterprise plan, also connect your runbooks, docs and postmortems with the Operational Memory skill, so Nova cites them (Operational Memory).
4. A change waits for an approver
When Nova proposes a change, such as the fix for the pods-probe-web crash loop, it waits on an approval card. Only owners and admins can select Let Nova fix it (deadlines and where to answer).
5. Alice reads the audit trail
Guardrails > Activity lists every decision with who made it (Every decision is recorded). To halt every change at once, see Emergency stop.
Result: Nova reads on its own, asks before every change, only owners and admins approve, and every decision is on the record.