Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform administration
Table of Contents
Choose your release version
    Home Orlando Now Platform Administration Now Platform administration User administration Manage user sessions

    Manage user sessions

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Manage user sessions

    The Now Platform provides the ability to view and terminate individual user sessions, lock out users from the system, and make users inactive.

    • Terminating a specific user session effectively logs that user out of the next transaction, which is usually the next browser click. Use the terminate sessions feature when you want to perform system maintenance.
    • Locking a user out of the system means the user can no longer log in or generate any actions from any email messages that the user sends to the instance. Locking out users also terminates their user sessions.
    • Making a user inactive means that the user does not show up in any fields that reference active users on the User table.

    Modify session timeout

    The base system uses the default Apache session timeout of 30 minutes.

    Before you begin

    Role required: admin

    About this task

    After 30 minutes of inactivity in the application, the platform logs the user out automatically, unless the Remember Me check box in the login screen is selected. Making the interval longer can lead to the unnecessary maintenance of inactive sessions in memory. Adjust this timeout setting to no more than a few hours, although up to 24 hours is workable.
    Note: Regardless of how many windows a user has open in a browser, it is considered to be one session. However, if a user has two separate browsers open (such as Internet Explorer and Firefox), it is considered to be two separate sessions.

    Procedure

    1. Clear the Remember Me check box in the login screen.
    2. In the Navigator pane, enter sys_properties.list.
    3. In System Properties, search for glide.ui.session_timeout.
    4. If glide.ui.session_timeout does not exist, click New to add a new property using the following values:
      • Name: glide.ui.session_timeout
      • Description: Type a brief description. In this case, enter something like Override the default session timeout (30). This value is in minutes.
      • Type: Select the appropriate data type. In this case, select Integer.
      • Value: Change the default value from 30 minutes to a value of your choice.
      Note: The session timeout can also be set through installation exit customizations.

    What to do next

    • Ajax calls to the server keep the session alive (such as Labels and Refreshing homepages).
    • Polling keeps the session alive when the chat desktop is open (requires the Chat plugin).
    • Administrators can add the following properties to the System Properties table.
      • glide.security.csrf.handle.ajax.timeout: Handles errors for timed out Ajax requests when set to true.
      • glide.security.auto.resubmit.ajax: Automatically resubmits timed-out Ajax requests when set to true and the Remember Me check box is selected or automatically set. A popup appears to users asking them to continue.
      • glide.ui.auto_req.extend.session: When set to true, the system automatically extends a user's session by the value the user selects for the homepage refresh time. If there is no homepage refresh time, the standard timeout value applies. Tablet and mobile devices do not support this property. When set to false, user sessions time out when the Remember me check box is clear. The timeout is based on whether there is a homepage refresh time. When there is no homepage refresh time, the standard timeout value applies. When there is a homepage refresh time, the user session times out after the timeout value plus one interval of the homepage refresh time. For example, if a user selects to refresh interval of five minutes, then user sessions expires after the timeout value plus five minutes.
        Note: Users who select the Remember me check box are unaffected by session timeout properties.
    • Administrators can also add the following properties to configure an alternate session timeout value for guest sessions. You can do this to conserve system resources:
      • glide.session.unauthorized.timeout.enabled: If set to true, enables an alternate session timeout for unauthenticated, guest sessions. Guest sessions are created for HTTP requests to the instance that do not contain authentication information. By default this property is set to true.
      • glide.unauthorized.session_timeout: The session timeout value in minutes that controls the lifespan of an unauthenticated (unauthenticated) guest session. Set the property to a value greater than 0 and less than the value in the glide.ui.session_timeout property.
    Related tasks
    • Add a new property

    Lock out a user

    Lock out a user when you do not want the user to access the instance.

    Before you begin

    Role required: user_admin or admin

    Procedure

    1. Navigate to User Administration > Users and select the user from the list.
    2. Select the Locked Out check box, and update the record.

    Mark a user inactive

    You can mark a user inactive so the user does not show up in any fields that reference active users on the User table.

    About this task

    Note: By default, when you mark a user inactive, you lock out that user. The Lock Out Inactive Users business rule governs this behavior.

    Procedure

    1. Navigate to User Administration > Users and select the user from the list.
    2. Clear the Active check box, and update the record.

    Terminate a specific user session

    You can terminate a user session, for example, if you are going to perform system maintenance and users are still logged in.

    1. Navigate to User Administration > Logged in users.
      You can only see users who are logged into the same application node as you. If the Active field on a user record value is false, the user is logged in but not currently running a transaction. Most users appear as inactive at any given time.
    2. Select the session you want to end.
    3. Click Lock Out Session.
      The session is terminated, and the user is redirected to the login page at the next attempted transaction. The user is not locked out. Multiple user sessions may be associated with one user. Terminating a user session only affects the specific session.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Manage user sessions

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Manage user sessions

      The Now Platform provides the ability to view and terminate individual user sessions, lock out users from the system, and make users inactive.

      • Terminating a specific user session effectively logs that user out of the next transaction, which is usually the next browser click. Use the terminate sessions feature when you want to perform system maintenance.
      • Locking a user out of the system means the user can no longer log in or generate any actions from any email messages that the user sends to the instance. Locking out users also terminates their user sessions.
      • Making a user inactive means that the user does not show up in any fields that reference active users on the User table.

      Modify session timeout

      The base system uses the default Apache session timeout of 30 minutes.

      Before you begin

      Role required: admin

      About this task

      After 30 minutes of inactivity in the application, the platform logs the user out automatically, unless the Remember Me check box in the login screen is selected. Making the interval longer can lead to the unnecessary maintenance of inactive sessions in memory. Adjust this timeout setting to no more than a few hours, although up to 24 hours is workable.
      Note: Regardless of how many windows a user has open in a browser, it is considered to be one session. However, if a user has two separate browsers open (such as Internet Explorer and Firefox), it is considered to be two separate sessions.

      Procedure

      1. Clear the Remember Me check box in the login screen.
      2. In the Navigator pane, enter sys_properties.list.
      3. In System Properties, search for glide.ui.session_timeout.
      4. If glide.ui.session_timeout does not exist, click New to add a new property using the following values:
        • Name: glide.ui.session_timeout
        • Description: Type a brief description. In this case, enter something like Override the default session timeout (30). This value is in minutes.
        • Type: Select the appropriate data type. In this case, select Integer.
        • Value: Change the default value from 30 minutes to a value of your choice.
        Note: The session timeout can also be set through installation exit customizations.

      What to do next

      • Ajax calls to the server keep the session alive (such as Labels and Refreshing homepages).
      • Polling keeps the session alive when the chat desktop is open (requires the Chat plugin).
      • Administrators can add the following properties to the System Properties table.
        • glide.security.csrf.handle.ajax.timeout: Handles errors for timed out Ajax requests when set to true.
        • glide.security.auto.resubmit.ajax: Automatically resubmits timed-out Ajax requests when set to true and the Remember Me check box is selected or automatically set. A popup appears to users asking them to continue.
        • glide.ui.auto_req.extend.session: When set to true, the system automatically extends a user's session by the value the user selects for the homepage refresh time. If there is no homepage refresh time, the standard timeout value applies. Tablet and mobile devices do not support this property. When set to false, user sessions time out when the Remember me check box is clear. The timeout is based on whether there is a homepage refresh time. When there is no homepage refresh time, the standard timeout value applies. When there is a homepage refresh time, the user session times out after the timeout value plus one interval of the homepage refresh time. For example, if a user selects to refresh interval of five minutes, then user sessions expires after the timeout value plus five minutes.
          Note: Users who select the Remember me check box are unaffected by session timeout properties.
      • Administrators can also add the following properties to configure an alternate session timeout value for guest sessions. You can do this to conserve system resources:
        • glide.session.unauthorized.timeout.enabled: If set to true, enables an alternate session timeout for unauthenticated, guest sessions. Guest sessions are created for HTTP requests to the instance that do not contain authentication information. By default this property is set to true.
        • glide.unauthorized.session_timeout: The session timeout value in minutes that controls the lifespan of an unauthenticated (unauthenticated) guest session. Set the property to a value greater than 0 and less than the value in the glide.ui.session_timeout property.
      Related tasks
      • Add a new property

      Lock out a user

      Lock out a user when you do not want the user to access the instance.

      Before you begin

      Role required: user_admin or admin

      Procedure

      1. Navigate to User Administration > Users and select the user from the list.
      2. Select the Locked Out check box, and update the record.

      Mark a user inactive

      You can mark a user inactive so the user does not show up in any fields that reference active users on the User table.

      About this task

      Note: By default, when you mark a user inactive, you lock out that user. The Lock Out Inactive Users business rule governs this behavior.

      Procedure

      1. Navigate to User Administration > Users and select the user from the list.
      2. Clear the Active check box, and update the record.

      Terminate a specific user session

      You can terminate a user session, for example, if you are going to perform system maintenance and users are still logged in.

      1. Navigate to User Administration > Logged in users.
        You can only see users who are logged into the same application node as you. If the Active field on a user record value is false, the user is logged in but not currently running a transaction. Most users appear as inactive at any given time.
      2. Select the session you want to end.
      3. Click Lock Out Session.
        The session is terminated, and the user is redirected to the login page at the next attempted transaction. The user is not locked out. Multiple user sessions may be associated with one user. Terminating a user session only affects the specific session.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login