System properties control platform-wide behavior like session timeouts, UI settings, and feature toggles. This guide shows you how to find, modify, and create these configuration settings safely.
What system properties replace
Before system properties, platform configuration meant editing configuration files and restarting services — standard for on-premise software but impossible in a cloud environment. System properties let ServiceNow administrators change platform behavior through the web interface without touching files or bouncing services. Platform admins use these to control everything from login session duration to whether certain features appear in the UI. The settings affect everyone on the instance, so changes need to be made thoughtfully.
How system properties work
System properties are name-value pairs stored in the sys_properties table, where the name is a dot-separated identifier like 'glide.ui.security.ignore_csrf' and the value is a string, boolean, or integer. The Type field matters — if you set a boolean property to 'yes' instead of 'true', ServiceNow interprets it as a string and the feature won't work. Most properties take effect immediately when saved, but some require a cache flush or user logout. You'll either modify existing properties that shipped with ServiceNow or create new ones for custom applications.
Managing properties at scale
Once you're comfortable with individual properties, you'll want to document which ones you've modified from defaults — this matters for upgrades and troubleshooting. Consider creating a custom table or spreadsheet that tracks your changes with business justification and rollback values. For custom applications, prefix your property names with your company identifier to avoid conflicts with future ServiceNow properties. Advanced administrators set up update sets to promote property changes across instances consistently.
Before you start
- •admin role
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to System Properties
Go to System Definition > System Properties, or use the faster approach: type 'sys_properties.list' in the Application Navigator filter and press Enter. The list view shows all properties with their current values, types, and descriptions.
Find your target property
Use the Name column filter to search for the property you want to modify — property names are dot-separated like 'session.timeout' or 'glide.ui.list.max_count'. If creating a new property, skip to step 4. Click the property name to open the record.
Search for partial names — filtering on 'session' will find all session-related properties.
Update the existing property value
Check the Type field first — this determines how ServiceNow interprets your value. For boolean types, use 'true' or 'false' (not 'yes'/'no'). For integer types, enter numbers without quotes. For string types, enter the text value. Change the Value field and click Update to save.
The Description field often contains valid values or ranges — read it before making changes.
Create a new system property
From the System Properties list, click New. Set the Name using dot notation like 'mycompany.feature.enabled'. Choose the correct Type (string, boolean, integer, or true/false) based on how your code will read the value. Enter the Value following the type requirements from step 3.
Prefix custom property names with your company identifier to avoid conflicts with future ServiceNow properties.
Set additional property details
Fill the Description field with the property's purpose and valid values — this helps other administrators later. Leave Suffix and Private unchecked unless you have specific requirements. Set Write roles only if you want to restrict who can modify this property. Click Submit to create the property.
Verify the change took effect
Most properties apply immediately, but some require cache clearing or user logout. Test the functionality the property controls to confirm your change worked. If it didn't take effect, double-check the Type field matches your value format.
Properties affecting UI behavior often require refreshing the page or clearing browser cache.
Best practices
Always check the Type field before changing a value — setting a boolean property to 'yes' instead of 'true' breaks the functionality silently.
Document any properties you change from default values, including the original value and business justification — you'll need this during upgrades.
Test property changes in a development instance first, especially for authentication or security-related settings that could lock you out.
Prefix custom property names with your organization identifier to avoid naming conflicts with future ServiceNow releases.
Never delete system properties that shipped with ServiceNow — set them back to default values instead.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue