Skip to main content
An access policy decides what access a whole group of people gets, so a mistake in it reaches everyone it covers. Approvals add a sign-off before that access goes live. With approvals on, an approver signs off at two moments:
  • Before a new policy is published for the first time. The approver reviews the whole policy.
  • Before a change to a published policy goes live. The approver reviews the apps and permissions that changed.
Approvals bring the people who know the access best, like policy owners and app owners, into the decision, and Lumos records who approved each version. Approvals are off by default. When you turn them on, they apply to every access policy in your organization. Use approvals when:
  • You need sign-off before access is granted or changed. A department lead or app owner confirms a new policy, or a change to a live one, before anyone gains or loses access.
  • You run approvals outside Lumos today. Lumos replaces the Jira ticket or spreadsheet you use to approve a policy before you set it up by hand.
  • You need audit evidence. Lumos records who approved each published version of a policy and when.

How approval works

  1. An Admin or policy owner builds a new policy as a draft, or creates a draft of a published policy to change it. When the draft is ready, they submit it for approval.
  2. Lumos notifies the policy’s approvers.
  3. Approvers, and anyone the policy is shared with, leave comments on the draft to ask questions or request changes. For a new policy, they review the whole policy. For a change, they can compare the draft to the published version.
  4. A policy owner or Admin works through the comments and updates the draft. If they change the apps or permissions, they submit the draft again.
  5. When the draft is final, an approver approves it.
  6. An Admin publishes the approved draft. A new policy is published for the first time, or the approved draft replaces the published version.
While a change is in review, the published policy keeps working as it is, so nothing changes for the people it covers until the approved draft is published. The sections below follow these steps in order.

Turn on approvals

Only Org Admins can change approval settings.
  1. Go to Access Policies and click Settings in the top right.
    The Settings button next to Create Policy
  2. In the Access Policy Settings drawer, turn on Approval Required.
    The Approval section of Access Policy Settings
  3. Add at least one approver. See Assign approvers.
  4. Click Save. Lumos shows Approval settings saved.
Approvals also apply to drafts that already exist when you turn them on, including new policies that haven’t been published yet. Each of those drafts has to be submitted and approved before an Admin can publish it, even if it only changes conditions or the name.

Assign approvers

  1. In the Access Policy Settings drawer, click Add approvers next to Approvers. If approvers are already set, click them to edit the list.
  2. In the Approvers dialog, click Add and choose who can approve. You can combine any of these:
    The approver picker with Policy Owners, Permission Owners, App Admins and groups
  3. Click Confirm, then click Save.
Org Admins can approve any draft, even if you don’t add them as approvers. Lumos only notifies the Org Admins you add here, so add anyone you expect to sign off. Policy owners are approvers only if you add Policy Owners. If you want owners to sign off on their own policies, as the rollout guide recommends, add them here.

What needs approval

A new policy always needs approval before it’s published for the first time, because everything in it is new access. After that, only changes to the access a policy grants need approval. If a draft only has changes that don’t need approval, an Admin can publish it without submitting it. This only applies to a published policy. A new policy always needs approval before its first publish, and so does any draft that already existed when approvals were turned on.

Submit a draft for approval

Admins and policy owners can submit a draft for approval. How you get to the draft depends on whether the policy is new or already published.

Submit a new policy

  1. Go to Access Policies and click Create Policy.
  2. Set up the policy: its conditions, the apps and permissions it grants, and its business justification.
  3. Click Save. Lumos saves the policy as a draft and opens the Drafts tab.
  4. Open the draft, then click Submit for Approval.
Approvers review the whole policy, since there’s no published version to compare it to.

Submit a change to a published policy

  1. Open the published policy and click Create Draft. If the policy already has a draft, open it from the Drafts tab instead.
  2. Make your changes under Grant Apps & Permissions.
  3. Click Save, then click Submit for Approval.
The published version keeps running as it is until an Admin publishes the approved draft.
A draft with the Draft badge and the Submit for Approval button
Until an approver approves the draft, Publish Policy… is disabled. Its tooltip reads These changes need approval before they can be published. Submit them for approval first. before you submit, and These changes need approval before they can be published. Waiting for an approver. while the draft is pending. If Submit for Approval is disabled, hover over it to see why:

Approval status

How a draft moves from Draft to Pending Approval, Approved and Published
The badge on the policy page shows where a draft is in approval:
The Draft · Approved badge tooltip showing who approved and when
To see every draft in one status, go to Access Policies and open the Drafts tab. Click Show Filters, then select Draft, Pending Approval or Approved under Status. The Status filter is only available while approvals are on.
The Drafts tab filtered by Status

Notifications

Lumos sends approval notifications by email, Slack or Microsoft Teams, depending on your organization’s settings under Settings → Notifications. Lumos doesn’t notify you about your own request, even if you are one of its approvers.

Who needs to approve

One approval from any approver is enough, even if a draft has several approvers. Lumos works out who the approvers are when a draft is submitted. If you change the approval settings, the change applies the next time a draft is submitted. You can approve your own draft if you are one of its approvers.
Because one approval is enough, approvers should approve only when the draft is final. Once a draft is approved, an Admin can publish it.

Review and approve a draft

When a draft is pending approval, its approvers can open it and see the whole policy: its conditions, business justification, apps and permissions, and comments. Approvers can’t edit or publish the draft unless they’re also policy owners or Admins. What approvers look at depends on the draft:
  • A new policy: there’s no published version yet, so approvers review the whole policy. The badges next to each app and permission show how widely it’s used and assigned.
  • A change to a published policy: approvers can turn on Compare to published to see only the apps and permissions that changed.

Approve

A draft with the Pending Approval banner and the Approve button
Click Approve in the Pending Approval banner. Approve only appears while the draft is waiting for approval. If another approver approves first, the banner reads This draft was already approved.

Leave comments

Use the comment section on the policy page to ask a question or request a change. Approvers can’t reject a draft. To ask for changes, they comment, and a policy owner or Admin updates the draft. See Sharing Access Policies.

Compare to the published version

A new policy has no published version, so Compare to published doesn’t appear.
On a draft of a published policy, turn on Compare to published above the app list to see what changed. Added apps and permissions are highlighted in green, and removed ones are shown in red with a strikethrough.
The compare view with added and removed apps and permissions
A draft of a published policy opens in this view automatically when it’s waiting on approval or has saved changes to its apps or permissions. If you have unsaved edits, Lumos asks you to save them before it shows the comparison.
The prompt to save unsaved changes before comparing

Make updates and resubmit

If anyone changes the apps or permissions after a draft is submitted, the draft goes back to Draft and needs to be submitted and approved again. This applies to new policies and to changes to published policies, whether the draft was waiting on approval or already approved.
The banner asking the editor to resubmit for approval
For the policy owner’s side of this process, see Review an Access Policy as the Policy Owner. For people you share a policy with to get their input, see Review an Access Policy as a Policy Reviewer.

After approval

When an approver approves a draft:
  1. The badge changes to Draft · Approved, and Publish Policy… is enabled.
    An approved draft with Publish Policy enabled
  2. Lumos notifies the person who submitted the draft.
  3. An Admin clicks Publish Policy…. A new policy is published for the first time, or the approved draft replaces the published version.
Publishing a new policy doesn’t start granting its access. To do that, make the policy active. See Making your Policies Active / Inactive. Approvers lose their approver access when the draft is published. They keep any access they had before, for example as an owner or through a share. If someone deletes or discards the draft, Lumos cancels the request, and approvers lose their access to review it.

Activity log

The activity log records:
  • Each publish that needed approval, including who approved the published version and when, in the Approved By field.
  • Each change to approval settings, including turning approvals on or off and changes to approvers.

Turn off approvals

  1. Go to Access Policies and click Settings.
  2. Turn off Approval Required and click Save.
  3. In the Turn off approvals? dialog, click Turn off.
Drafts no longer need approval, including drafts that are waiting for approval. Admins can publish them right away. Approvers lose the access they had to review those drafts.

Frequently asked questions

Can I require approval for some policies and not others? No. Approval settings apply to every access policy in your organization. How many approvals does a draft need? One. Any one approver can approve it. Who can publish an approved draft? Admins. Does a change affect anyone while it’s in review? No. The published policy keeps granting the same access until an Admin publishes the approved draft. Do new policies need approval if approvals were turned on after I started building them? Yes. Any draft that hasn’t been published yet needs approval before its first publish, no matter when you started it.