GlideSystem.getUserID() — ServiceNow API

gs.getUserID()→ string

beginnerTested on Xanadu

What It Does

The getUserID() method returns the sys_id of the user who triggered the current server-side script execution. ServiceNow maintains user context throughout the request lifecycle, allowing scripts to identify which user initiated the action even when processing occurs in background threads or workflow activities.

Internally, ServiceNow stores the user context in the session object and maintains it across all server-side script executions within that request. The method retrieves the sys_id field from the sys_user record of the authenticated user, not their username or display name.

The method returns a 32-character hexadecimal string when a user context exists. During system operations like scheduled jobs, data imports, or certain workflow activities, no user context exists and the method returns an empty string. Web service calls maintain user context if properly authenticated, but system-generated events may not.

User impersonation affects the return value. When an administrator impersonates another user, getUserID() returns the impersonated user's sys_id, not the administrator's. This behavior ensures security rules and user-scoped queries work correctly during impersonation sessions.

The method works identically to gs.getUser().getID() but with better performance since it doesn't instantiate a GlideUser object. Use gs.getUserName() to get the username instead of the sys_id.

When to Use This

Use getUserID() whenever you need to scope database queries to the current user, enforce security rules, or track user-specific actions. This includes filtering records by assigned_to, requested_by, or any reference field that should match the current user's sys_id.

Use gs.getUser() instead when you need additional user properties like roles, groups, or preferences. Use gs.getUserName() when you need the username for display or logging purposes. Avoid using this method in client-side scripts where g_user.userID is the correct approach.

Return Value

Returns a 32-character string containing the hexadecimal sys_id of the current user (e.g., "5137153cc611227c000bbd1bd8cd2005"). The return value is always a string type, never null or undefined. When no user context exists, such as during system operations or scheduled jobs, the method returns an empty string ("").

💡

Always check for empty string before using the return value in queries. Use if (gs.getUserID()) to verify user context exists.

Free Newsletter

Enjoying this? Get one deep-dive per week.

Join 1,000+ ServiceNow pros — scripts, GlideRecord patterns, Flow Designer techniques, and career moves. Free.

Platform Behavior & Side Effects

No database queries are executed - the user ID is cached in memory for the request duration
No Business Rules, ACLs, or notifications are triggered by calling this method
Performance is excellent - sub-millisecond execution time
Returns the same value throughout a single request lifecycle, even across multiple script executions
User context persists through workflow activities and async script execution within the same request
Returns impersonated user's ID during admin impersonation sessions, not the admin's ID
Behaves identically in before/after Business Rules, Script Includes, and UI Actions

Chrome Extension

Sourdough: ServiceNow Monitoring and Analytics

A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.

Instance HealthGraphs & ChartsAPI HealthDeveloper ToolsQuick SearchInstance Switcher

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview

Tasks

CMDB

API

Metrics

Monitor

Internals

Instance:sourdoughdev·Version:Yokohama

Instance StateONLINE

System StatusFully Operational

Session Timeout90 minutes

Logged-In Sessions2 (20 active)

Build Nameyokohama-12-18-2024_p1

IP Address10.159.128.43

Instance HealthHealth Score: 90%

🔥 5dSourdough (Chrome Plugin)Dark Mode

Code Examples

Basic usage — Query user's incidentsbasic

// Business Rule: Limit incident visibility to assigned user
var userID = gs.getUserID();

if (userID) {
    var gr = new GlideRecord('incident');
    gr.addQuery('assigned_to', userID);
    gr.query();
    
    gs.info('Found ' + gr.getRowCount() + ' incidents assigned to current user');
    
    while (gr.next()) {
        gs.info('Incident: ' + gr.number + ' - ' + gr.short_description);
    }
} else {
    gs.warn('No user context available - running as system');
}

Shows the standard pattern for user-scoped queries with proper empty string checking. The user context check prevents errors during system operations.

Intermediate — Audit trail with user trackingintermediate

// Script Include: Create audit record with current user context
function createAuditTrail(action, recordSysId, details) {
    var userID = gs.getUserID();
    var userName = gs.getUserName() || 'system';
    
    var audit = new GlideRecord('sys_audit');
    audit.initialize();
    audit.tablename = 'incident';
    audit.record_sys_id = recordSysId;
    audit.field_name = 'state';
    audit.new_value = action;
    audit.user = userID || 'system'; // Handle system operations
    audit.user_name = userName;
    audit.reason = details;
    
    var auditSysId = audit.insert();
    return auditSysId;
}

Demonstrates handling both user and system contexts when creating audit records. The fallback to 'system' ensures the audit trail works even without user context.

Advanced — Security validation patternadvanced

// Business Rule: Enforce record ownership security
function validateRecordAccess(tableName, recordSysId) {
    var currentUser = gs.getUserID();
    
    // System operations bypass security checks
    if (!currentUser) {
        return true;
    }
    
    // Check if user owns or is assigned to the record
    var record = new GlideRecord(tableName);
    if (record.get(recordSysId)) {
        var hasAccess = (record.sys_created_by == currentUser) ||
                       (record.assigned_to == currentUser) ||
                       (record.requested_by == currentUser);
        
        if (!hasAccess && gs.hasRole('admin')) {
            hasAccess = true; // Admins can access all records
        }
        
        return hasAccess;
    }
    
    return false;
}

Shows a comprehensive security pattern that handles user ownership validation, system context, and role-based overrides. This prevents unauthorized access to records.

Gotchas

Returns empty string (not null) during system operations like scheduled jobs, making string comparison checks essential before using the value in queries.

During admin impersonation, returns the impersonated user's sys_id rather than the administrator's, which can confuse debugging sessions.

Web service calls may or may not have user context depending on authentication method - REST calls with proper auth maintain context, while some integrations run as system.

The return value persists throughout the entire request lifecycle, so user context switches mid-request won't affect already-executing scripts.

Workflow activities maintain user context from the triggering action, but some system-generated workflow events may run without user context and return empty string.

Test Your Knowledge

Quick 3-question quiz — see how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue