When navigating the ServiceNow UI, it's important to understand the difference between configuration, and personalization. These are defined terms within ServiceNow. As a general rule, in UI16 and later, configuration results in changes for everyone, whereas personalization results in changes just for you.
Most configuration modifies global system settings,configuration records, and properties (properties can be found in the sys_properties table), whereas most personalization results in modified or generated preferences (user preferences can be found in the sys_user_preference table). You can create Global default preferences by creating a preference record in the sys_user_preference table that isn't assigned to any particular user, but these default preferences can be overridden on a user-by-user basis, if users modify their preferences manually. It would be possible to create a data policy or business rule (discussed in a later chapter) to prevent users from customizing certain preferences, but this may lead to a bad user experience.
Some examples of personalization are:
Changing the columns that are displayed when viewing a given list, using Personalize List Columns from the hamburger menu at the top-left of lists:
- Or by clicking the gear menu at the top-left of the list view in Geneva and earlier
Adjusting your theme, list/form view preferences, or anything else from the System Settings gear menu at the top-right of the ServiceNow frame, in the banner.
Adding or removing fields on a form using the Personalize Form button (which looks like three stacked slider-toggles) at the top-right of a form.
Some examples of configuration on the other hand, are:
Changing the columns that are displayed when viewing a given list, using List Layout from the hamburger menu at the top-left of the list view (or by right-clicking the List header, and navigating to Configure |List Layout).
Modifying the system themes from the System UI |Themes module in the Application Navigator.
Adding/removing fields or moving fields around on a form, using the FormDesigner (Configure |FormDesign), or from Configure |FormLayout.
Take care not to make configuration changes when you mean to make personalization changes. Having the admin role can be a burden in this way. Some even avoid this by having entirely separate admin-only accounts that they must log into separately, so they can't make configuration changes by accident.