Appearance

Get started

Approvals for production

Make every production session pass a second person, and keep a record of the exceptions.

In Shellius, a server tagged prod always requires approval. No policy setting can switch that off: a policy's auto-approve flag is ignored for production.

A production request cannot be submitted without a reason. Interface preview with sample data.

1. Tag production honestly ​

Set the environment of every production server to prod. This one field is what triggers review.

2. Decide who approves ​

Approvers are set on policies and servers — see Access policies. Pick people who can judge the request, and more than one so that holidays do not block a deployment.

Approvers can shorten the duration they grant. Interface preview with sample data.

3. Decide whether anyone may bypass ​

Two things must both be true for someone to skip review:

  1. their role holds the access.prod_bypass permission, and
  2. the organisation switch prodBypassEnabled is on.

With the switch off, nobody skips review — not even a super admin. A bypass is never silent: the request is still created, a reason is still required, it is audited as access_request.prod_bypass, and the server's approvers are told afterwards.

A reasonable starting point

Leave the switch off. Turn it on only when you have an on-call rotation that genuinely needs it at 3 a.m., and review access_request.prod_bypass entries weekly.

4. Make approvals reach people ​

Approvers are notified in the portal and by email. Set up email delivery, or requests will wait unseen.

Next steps ​

Access requestsEvery state a request can be in.SettingsWhere the bypass switch lives.Audit logReview the exceptions.
Was this page helpful?No, tell us why