---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/de-DE/platform-administration

 Release :

    - brazil

ft:locale :

    - de-DE

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# User record

# The User record {#ariaid-title1}

Freigeben Version: Brazil  
Aktualisiert 10. September 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer  
Learn about user records and their use within the ServiceNow AI Platform.

## User account records {#user__section_ifn_gpz_5sb}

User records establish a relationship between an individual and your ServiceNow instance. User records consist of a user name, a password, and information relating to the individual, such as contact information, location, and job title.
Abbildung : 1. User record

User records are stored in the Users \[sys_user\] table.  
Hinweis:  
ServiceNow occasionally adds service accounts to the sys_user table to facilitate some platform features and functionality. For more information, see [KB1648003: (OOTB) Out of the box local user accounts in sys_user](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648003).

## Related records {#user__section_u5p_gsg_vsb}

User records are associated with records on several other tables to control permissions,
preferences, and other features.

Roles
:   Roles control access to features and capabilities in applications and modules. For more information on roles, see [Managing roles](https://www.servicenow.com/docs/nM1GQxjDbGjNFnpF7_H2GA "Administrators can create and configure roles that grant specific permissions, which govern what users and groups with that role can do.").  
    Hinweis:  
    When possible, simplify user administration by assigning roles to groups. Create groups that contain all the roles necessary for specific personas, and then assign users to those groups.

Groups
:   A group is a set of users who share a common purpose. Users assigned to groups are automatically assigned to all roles associated with that group. For more details, see [Creating groups](https://www.servicenow.com/docs/s8hmsnGxczJVC2vXuNAuyw "Admins can add users to one or more groups.") and [Managing roles](https://www.servicenow.com/docs/nM1GQxjDbGjNFnpF7_H2GA "Administrators can create and configure roles that grant specific permissions, which govern what users and groups with that role can do.").

Delegates
:   In addition to role and group assignments, users can be assigned as delegates, giving them permission to act with the same permissions as a delegator user. See [Delegating roles](https://www.servicenow.com/docs/zDZEzyq3ejY1beLUjiSwJQ "Administrators can grant users the ability to assign roles within groups. However, these users can only assign roles that they already have.") for more information on delegation.

Skills
:   Use skill management to associate users with their areas of training and expertise. For more information on skill management, see [Skill Management](https://www.servicenow.com/docs/access?context=skills-management&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US).

Subscriptions
:   Administrators use subscriptions to control which users have access to purchased
    subscriptions on their instances. Details on subscription management can be found at [Subscription Management](https://www.servicenow.com/docs/twE09d3KN1FW8cP3O5cFpA "Subscription Management enables you to proactively manage your subscriptions and monitor subscription usage on your instances.").

User
preferences
:   User accounts are also connected with user preferences. Users can save personalized
    preferences to configure many UI features, as well as preferences regarding the notifications
    they receive. Details on administering user preferences are found at [User preferences](https://www.servicenow.com/docs/access?context=c_UserPreferences&version=brazil&pubname=brazil-platform-user-interface&ft:locale=en-US).

## Date and time formatting {#user__section_nvm_d4q_23c}

For releases before Brazil, you can set your preferred date and time formatting through the User record. If you don't specify a preference in these fields, the system applies default formatting.

Before the Brazil release, the Date format field appears in the User record by default and can be modified without specific permissions. However, the Time format field must be added to the User record by revealing
additional form fields. For instructions on showing or hiding form fields, see [Configuring the form layout](https://www.servicenow.com/docs/ep~rnmhW2LWs6GKANT_HHQ#configure-form-layout "Administrators or users with the personalize_form role can configure the form and related list layout."). If you can't modify form fields, contact your organization's user administrator to update your time format preferences.

The Date and time format field in User MenuPreferencesLanguage \& Region extends the options you select in the Date format and Time format fields of your User record. For more information, see [Configure Next Experience language and region preferences](https://www.servicenow.com/docs/access?context=next-experience-language-preferences&version=brazil&pubname=brazil-platform-user-interface&ft:locale=en-US). Time zone settings automatically sync between the User record and your preferences.

## System and guest users {#user__system-guest-users}

Some automated processes use the system or guest user to apply and track changes to records. As a result, some records may show that they were last updated by system or guest.

For example, when a user logs in for the first time in a day, some fields on that user's record are updated by the system user. These fields can include Last login and Last login time. If a user has
a failed login attempt or is locked out, some fields on that user's record are updated by the guest user, such as Failed Login Attempts or Locked Out.

If a record was last updated by the system or by guest users, you can identify the updated fields by enabling auditing for the table. View the audit history to see the changes. For more information, see [Configuring auditing for a table](https://www.servicenow.com/docs/access?context=t_EnableAuditingForATable&version=brazil&pubname=brazil-platform-security&ft:locale=en-US) and [Knowing about History sets](https://www.servicenow.com/docs/access?context=c_HistorySets&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

