Default Column Setting Configured for Workflow Does Not Reflect in UI

Description:

Columns in the access review interface can be customized to rearrange, show, or hide certain attributes. This can be configured globally or per workflow.

An example API body JSON request may look something like below:

{
"value": {
"default_ordered_columns": [
"source.name",
"source.department",
"source.customprop_worker_status",
"source.tags",
"path_summary.name",
"concrete_permissions",
"destination.name",
"destination.customprop_display_name",
"reviewers"
]
},
"workflow_id": "002063d2-7898-4183-b5fb-1192758fdec7"
}

The expectation is that these columns will be loaded as default when the workflow is loaded for all users. 

Issue:

The problem is that columns settings are persisted via the browser's local storage.

Solution:

Columns are persisted via the local browser storage. The idea for this is that if a user would like to include or exclude additional columns to the view in their access review, they should be able to. Which means that the default column setting an admin has configured may not reflect in the UI. 

To resolve this, you will need to delete the browser local storage settings as seen in the screenshot below:

If there are multiple ones, you will need to delete all. After that, do a refresh and your default column settings for the workflow will show correctly.