Adopt a CDE approval preset

Open Set up CDE and step through the naming convention, suitability codes and the four functional roles - Author, Reviewer, Approver, Viewer.

Why: The wizard is resumable and saves as you go, so a half-finished setup never loses progress. Fixing who holds each role first is what makes the gate a step later mean something.

In the CDE page's Approval presets card, pick Issue for review, Comment and return, or Review and publish, and click Adopt. This clones the preset into a route that belongs to your project.

Why: The tenant-wide preset stays read-only and reusable by every other project; adopting makes your own copy the one you can actually change, without anyone else's flow moving under them.

In Approval routes, open your cloned route and adjust it: rename it, change an approver's role, add a second step, or set an SLA - then dry-run it before anyone routes real work through it.

Why: A preset is a starting point, not a straitjacket. The dry run proves your tailored route still terminates at approved before it gates a real container.

Back in the CDE page, check the go-live readiness scorecard. It only allows inviting the whole team once the workflow has actually been exercised, not just configured on paper.

Why: A CDE that looks configured but has never moved a container through its gates is a showroom, not a working environment. The gate is what stops a team finding that out the hard way.