Guided Setup
Nishad
Step 1 of 4
Why we ask this

Cortex needs to know who's actually running this install so approvals, activity, and the audit log all point to a real person โ€” never a shared account.

Who is the operator of this install?

Pre-filled from the bootstrap identity domain set when this install was stood up.

You can change any of this later in Settings โ€” this walkthrough just sets a sensible starting point, one decision at a time.

What's on this screen

Built from: your answers to four setup questions, each pre-filled with a sensible default pulled from this install's license and bootstrap identity.

On screenWhere it comes fromWhat it means to you
Progress dots (Step X of 4)which of the four setup questions you're onshows how much is left before setup finishes
"Why we ask this" boxa plain-English reason written for that questiontells you why Cortex needs the answer before you give it
Operator name/email (step 1)pre-filled from the identity used to license this installsets who approvals and the audit log point to
First company (step 2)defaulted to the company that owns this installdecides which company's work this install starts managing
Default approver toggle (step 3)your choice of who approves gates until you change itsets who has to sign off design/plan/test gates out of the box
Default model & deployment envelope (step 4)your choice, matched to this install's licensed deployment modesets what every agent runs on until you customize per-role
Back / Next / Finish setup buttonsyour navigation through the four questionslets you review or correct an earlier answer before committing