Background
Reviewers in an access review don’t always know what data matters most to a decision. When the table shows some column by default and hides some others, the noise can hide the appropriate signals of which entitlement is risky, who last logged in, what the AI Insights say. The result is slower reviews and less confident decisions. As an admin, you have the context reviewers don’t. With admin-configured table views, you can curate the columns reviewers see by default for each app, so every reviewer in your organization starts from the same focused, decision-ready view. Configuring views for reviewers lets you:- Cut down on noise. Hide columns that aren’t relevant to the decision (e.g., system identifiers, fields used elsewhere in Lumos but not in reviews).
- Surface what matters. Lead with the columns reviewers actually rely on, such as AI Review Insights, Last Login, or Manager.
- Standardize the reviewer experience. Every reviewer working on a given app sees the same default columns in the same order, across every campaign.
- Stay flexible. Reviewers can still tailor their own view if they want to, and reset back to your default at any time.
Who can configure views
The people who can configure views are:- People who have the Manage permission for Access Reviews through a custom role
- Campaign owners can configure views for any access review app within campaigns they own
- App Review Admins can configure views for the access review apps they own
How to configure a view
1. Open the access review and select the app
From Access Reviews, open the campaign and select the app whose view you want to configure.2. Open the Columns menu
In the top right of the entitlements table, click Columns. You’ll see the full list of available columns with toggles for visibility, and handles to drag and reorder them.
3. Show, hide, and reorder columns
Show/Hide columns to show data that’s most relevant to the Review decision and hide everything else.
4. Click Save for Everyone
Hit Save for Everyone to persist this configuration as the default view for every reviewer working on this app. If you make changes but don’t click Save, nothing is pushed to other reviewers, just to your local view.
5. Use Reset to undo local changes
If you’ve been experimenting and want to return to the currently saved default, click Reset.What gets saved (and what doesn’t)
- Saved on click: column visibility and column order.
- Not saved: filters and sorts. Filters and sorts stay local to whoever applied them.
Where the saved view applies
Admin-configured views are persisted per app, not per campaign. That means:- The saved view applies to every review of that app, across past, current, and future campaigns.
- The saved view applies across all stages of the review (Assigning Reviewers, Reviewing, etc.) and all tabs within a stage (Needs Assignments, Assigned, All).
- When a review transitions to the next stage, that stage uses the column configuration from the previous stage as its starting point.
How reviewers experience the view
Reviewers open the app and see the default view you configured. They can still:- Show or hide columns locally for their own session.
- Reorder columns locally for their own session.
- Apply filters and sorts as they work.
- Click Reset at any time to return to the admin-configured default.