Search Views allow you to save specific configurations for how asset or collection data is displayed in your domain. This includes settings like visible columns, sizing and presentation of columns,and the overall layout of information. With Search Views, you can tailor the display to suit different workflows, roles, or departments — and easily switch between them when needed.
What Are Search Views?
Search Views are saved layouts or “views” of how information is displayed when searching or browsing assets or folders. These views capture:
- Selected columns and fields
- Sorting and filtering preferences
- Layout arrangements
Once configured, a Search View can be saved and reused, saving time and ensuring consistency across teams. Users can switch between multiple Search Views depending on their current task or role.
Creating or Updating a Search View
You can either create a new Search View or update an existing one. To do this:
- On the Search page, configure the display (choose your columns, arrangement, sizing, etc.)
- Select the Edit View menu option
- Click Search Views
- Choose to Create new View or Update Existing View
- Name the view (if new), and confirm your selection
Editing or Deleting a Search View
You can edit or delete an existing Search View. To do this:
- On the Search page, select the Edit View menu option
- On the view of your choice, select the edit icon
- Make any applicable changes or select the delete icon
- Confirm your choices
Assigning Search Views
Search Views can be assigned at different levels:
- User-level: A view specific to an individual user.
- Group/Team-level: Set as the default for users with specific Groups as their primary Groups (legacy) or users with specific Teams as their primary Teams.
- System-level: Available as a default for everyone in the system.
This flexibility ensures that the right people always have the right views, without needing to reconfigure their interface every time.
Please note, individual users can override the Search Views set on the domain or Group/Team level within their own settings.
Use Cases
- Marketing team needs to see campaign assets with fields like “Region”, “Channel”, and “Status”.
- IT team views collections with metadata like “Last Modified”, “Owner”, and “Permissions”.
- Executives have a simplified view with only essential KPIs and project statuses.