AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  1. Home
  2. Managing users
  3. User internals and API

User internals and API


Was this page helpful?

Send us feedback Go back to top

Related pages

  • User management
  • Handling custom administration authentication
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

Database tables

The following database tables store user data:

Database table

Description

CMS_User

Stores records representing users.

CMS_UserSettings

Stores the advanced settings of user accounts.

CMS_UserSite

Stores relationships between users and sites. Each entry indicates that a specific user account is available on a given site.

CMS_UserCulture

Stores relationships between users and cultures. Each entry indicates that a user may edit the content of documents belonging to a specified culture/language (if the given user has the Editor privilege level).

CMS_UserMacroIdentity

Security signature used when signing macro expressions. Signatures prevent macros from accessing or displaying data for which the author is not authorized. See Working with macro signatures.

The following database tables store the data of user roles, permissions and memberships:

Database table

Description

CMS_Role

Stores records representing roles.

CMS_UserRole

Stores relationships between users and roles. Each entry indicates that a specific role is assigned to a given user. Also stores the expiration date for roles that are assigned for a limited time period.

CMS_Membership

Stores records representing memberships.

CMS_MembershipUser

Stores relationships between users and memberships. Each entry indicates that a user belongs to a specific membership. Also stores the expiration date for roles that are assigned for a limited time period.

CMS_MembershipRole

Stores relationships between roles and memberships. Each entry indicates that a membership includes a specific role.

CMS_Permission

Stores the system's permissions.

CMS_RolePermission

Stores relationships between roles and permissions. Each entry indicates that a role has a specific permission.

CMS_RoleUIElement

Stores UI personalization settings for roles.

CMS_RoleApplication

Stores the default application content of the system dashboard for individual roles (the system uses UI elements to represent applications).

Users can individually adjust their own dashboard and override these default settings.

CMS_ACLItem

Stores page-level permissions, and their relationships with users or roles.

CMS_ACL

Stores relationships between ACL items and individual pages (tree nodes).