Customizing Default Columns

Change the columns shown in the reviewer interface, and the order rows appear.

Overview

Columns in the review interface can be customized to rearrange, show, or hide certain attributes. Configuring default columns can improve overall readability, and offer reviewers valuable context for each row. Note that changes to columns made in the Veza UI will be saved to the browser. If a user has already customized a certification's columns, changes to the default settings will not apply.

circle-info

Column Pinning and Reordering: Reviewers can drag column headers to reorder them, or pin columns to keep them visible while scrolling. These customizations are saved to your browser and persist across sessions.

You can also change the default order in which rows appear. For example, you might want to show results in descending order by destination resource type. This can be useful to encourage reviewers to focus on particular rows earlier in the review.

A set of global default columns and sort method applies to all reviews. You can also configure custom column orders for all reviews created for a specific configuration.

There are two ways to set default columns:

  • From the reviewer interface (UI): Administrators can set default columns and grouping directly from the review UI. This is the quickest way to configure defaults for a specific configuration.

  • Using the API: Use API calls to set defaults globally or per configuration. This approach is ideal for automation or bulk changes.

Setting default columns from the UI

Administrators can configure default columns for all reviewers using a specific configuration directly from the reviewer interface:

  1. Open a review created from the target configuration in the reviewer interface.

  2. Arrange columns to your preferred layout (show, hide, and reorder columns as needed).

  3. Optionally, select a Group By option to set a default row grouping.

  4. Click Admin > Set Columns as Default.

The selected column layout and grouping option will be applied as the default for all future reviews created from this configuration. Existing reviews are not affected.

circle-info

The Set Columns as Default option saves both the column layout and any active row grouping selection. For more details on row grouping, see Row Grouping for Access Reviews.

Setting default columns using the API

Column customizations can also be configured using a private API call. This method is useful for setting global defaults, automating configuration, or making bulk changes across multiple configurations. By default, the customization applies to all reviews. Optionally, it will apply to all reviews created for a given workflow_id (corresponding to a review configuration in Veza).

The following example sets per-workflow default columns, including source tags, custom properties, summary entities, and reviewers:

Sort order

The default sort value is source.type asc for ascending order. You can default to descending order or sorting on another column by including an order_by value, for example:

Column syntax

Columns for entity attributes have the format:

  • source.attribute_name: Source entity attributes.

  • destination.attribute_name: Destination entity attributes.

  • waypoint.attribute_name: Attributes on the Relationship entity, if specified in the configuration.

  • path_summary.name: Shows Summary Entities from the configured scope.

  • idp.attribute_name: Attributes on the related IdP or HRIS user for a row, when the Enrich option is enabled for the configuration.

Columns can also show row metadata:

  • status

  • abstract_permissions

  • concrete_permissions

  • updated_at

  • notes

  • reviewers

  • decision

  • decision_by

  • decision_by_id

  • decision_by_name

  • decision_by_email

  • decision_at

  • marked_fixed_by_id

  • marked_fixed_by_name

  • marked_fixed_by_email

  • marked_fixed_at

  • signed_off_state

  • signed_off_by_id

  • signed_off_by_name

  • signed_off_by_email

  • signed_off_at

  • notification_status

  • automation_run_ids

  • no_decision_or_decision_by

  • is_signed_off

Last updated

Was this helpful?