--- sourceDocument: Brazil ServiceNow AI Platform user interface sourceDocumentLink: https://www.servicenow.com/docs/r/platform-user-interface Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform user interface ft:clusterId : - platux bundleId : - platux workflow : - Platform --- # View management # View management {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of View management Views in ServiceNow define which elements appear when users open forms or lists, typically displaying a subset of fields from the underlying table. Users can switch between different views to see various layouts or data presentations, such as the Incident form shown in different views like Self-Service or Metrics. This helps tailor the user experience for different roles or use cases. Show full answer Show less ## Key Features * **View Permissions:** Administrators and users with the `personalize` role can create, modify, and delete views and view rules. Users with `admin` or `viewchanger` roles can switch between views. * **Base System Views:** Several default views come pre-installed, such as Default and Advanced views, which must not be deleted. * **Switching Views:** Users can switch list views via the list context menu and form views via the form header menu. Switching views saves the form and triggers related client scripts, but cannot be done on unsaved new forms. * **User Preferences:** When a user selects a view, it is saved as a user preference to persist the view across sessions. This preference overrides URL parameters specifying views, unless explicitly overridden by setting the `sysparmviewforced` parameter to true. * **Create and Delete Views:** Administrators can easily create or delete views from lists or forms, enabling customization of data presentation. * **View Rules:** Administrators can define rules to control when specific views are displayed based on conditions such as field values or user roles, overriding user preferences as needed. * **Navigation Handler:** A scripted view rule that runs whenever form data is requested for a specified table, allowing dynamic control over view selection. ## Practical Benefits for ServiceNow Customers With view management, you can customize the appearance of forms and lists to match business needs, improve user experience, and enforce role-based access to specific views. This enhances usability, ensures relevant data visibility, and supports consistent workflows. Administrators have full control to tailor views and automate which views users see based on context or roles, helping streamline interaction with records across your ServiceNow instance. A view defines the elements that appear when a user opens a form or a list, and you can switch the view from the default for lists and forms. When the system displays a form or list it usually displays only a subset of the fields belonging to the underlying table. For example, this is the Incident form in the Self-Service View: Figure 1. Self service view This is the Incident form in the Metrics View: Figure 2. Metrics view Administrators and users with the personalize role have permission to perform the key tasks related to views: * create views for any list and form * determine which view is visible by default * delete views they have created * create and modify view rules determining which views are available depending on the values of the fields of the underlying table * create rules that determine which views pertain to specific user roles {#view-management-overview__ul_dp4_z1x_j1b} Users with the admin or view_changer roles can change views. ## Views included with the base system {#view-management-overview__section_vgq_xzw_j1b} Several views are included with the base system, including the Default view and Advanced view. Warning: Do not delete any of the base system views. ## Switching views {#view-management-overview__section_lvj_rkm_n1b} To switch between list views, click the list context menu at the top left corner of the list, and then select Views\[Desired View\]. Figure 3. List view list To switch between the list view in list v3, click the context menu, then select Change view\[Desired View\]. To switch between form views, click the context menu at the left side of the form header, and then select Views\[Desired View\]: Figure 4. Form view list Switching views submits the form, which saves all changes and triggers any onSubmit client scripts that apply. You cannot switch form views on a new form that has not been saved yet. When a user switches views, the selected view is saved as a user preference so the user sees the same view by default when the form opens. When a user has a view saved as a user preference and then opens a URL to a record that specifies another view, the form displays in the view saved in the user preference, not the URL. For example, if a user selects the Mobile view on an Incident record and then tries to open the following link, which specifies the visual task board view, the form still opens in the Mobile view: https://{instance}/nav_to.do?uri=incident.do?sys_id={sys_ID}sysparm_view=vtb The sysparm_view parameter specifies the view to be used for a list or a form, and can be overwritten by a user's stored preference for a view. You can override this behavior by setting the sysparm_view_forced parameter to true. * **[Create and delete views](https://www.servicenow.com/docs/ntV4WuxEgo9y6bA3OPXbZg)** Administrators can create views and delete any views they have created. You can create or delete views from either the list view or the form view. * **[Create a view rule](https://www.servicenow.com/docs/S6iYysQZxCmAgo6Dng4CMQ)** When a user switches views, the selected view is saved as a user preference so the user sees the same view by default when the form opens. With a view rule, you can override this functionality to force a specified view to be used. * **[Control when the system displays a view](https://www.servicenow.com/docs/z9mLaIB9Thl9EikIvqJbvQ#control-views)** Administrators can create rules that determine the conditions for when the system should display a form or list in a specified view. Administrators can also restrict views by user role. * **[Navigation handler](https://www.servicenow.com/docs/EKx16foY68vwjrX1tqt0iw)** A navigation handler is a scripted view rule and runs each time data from the specified table is requested in the form view. *[\>]: and then