Concept and mechanism
A ServiceNow instance brings together data, applications, and configuration for a specific environment. The same application can exist in development, testing, and production with different versions or data. Before investigating behavior, record the instance, user, interface, and application scope. Unified Navigation provides access to modules, workspaces, favorites, and history. Its navigation filter finds destinations; a list uses conditions on records. Confusing these produces incorrect diagnoses: finding the incident module does not mean the incidents for an application have been filtered. Visible menus depend on access and configuration, so two users can legitimately have different experiences.
Guided application
In a fictional APS handover, Lisbon reports that a task disappeared while Paris can still find it. First confirm that both users are looking at the same instance, table, and record identity. Then compare filters and effective identity. A favorite stores a useful destination but does not grant access to its contents. The selected development scope is also not a boundary that automatically isolates all data. Keep context explicit in investigation notes: test environment, table, identifier, time, and observed result. This discipline reduces unnecessary permission requests and changes in the wrong environment. This course develops knowledge and decisions; official certification depends on the provider’s process.
A test favorite can look identical to its production destination.
Common pitfalls
Navigation filter treated as data filter; menu treated as authorization; name treated as identity.
Related topics: Configuration, access, and interfaces · Records, collaboration, and analytics · Knowledge and catalog
Confirm environment, identity, and filter before concluding that data is missing.
Reference: Next Experience Unified Navigation · CSA blueprint January 2026