Sign up now for Client Certification Foundation Course - June cohort!
Pure's logos
Pure Help Center for Pure Administrators

If you are a researcher, or other non-admin at your institution, click here.

  • Home
  • Announcements
  • Release Notes
  • Technical user guides
  • Training
  • Events
  • Support
  • Contact Us
  • Home
  • Knowledge base articles
  • Pure Core

How Can We Help?

Search Results

Filter By Category

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact us

System UsersSystem Users

In Pure there are some system users which are needed to make Pure run.

 

List of system users:

  • root
  • sync_user
  • atira
  • ddp
  • recordlog
  • webservice
  • anonymous

These users are essential for keeping central parts of Pure running and are defined as:

  • root - used for running various jobs in Pure. If the user is deleted, these jobs cannot run.
  • sync_user - used for running various jobs in Pure. If the user is deleted, these jobs cannot run.
  • atira - used for Elsevier staff ADFS login (note that you can identify whom from ELS has logged in, even though it is this atira user we use for ADFS login). We use ADFS (Elsevier federated login method type) for accessing your Pure and we have automatic locking: Any individual access will be automatically withdrawn upon employment termination.
  • ddp - if you have this user, it is only used by the pure portal ddp-service, and only if you have set up basic authentication on your web service. For fetching portal content and updates the ddp service (pure portal) needs access to your web service, if basic authentication is enabled, a ddp user has been set up to allow access by the pure portal (this would either be you or something that has been set up by the Implementation manager while setting up the connection to pure portal). If this user is in use, and you delete/lock it, the pure portal will not be able to fetch updates to the portal from WS.
  • recordlog: this user was created in 5.31 and is to support the New Pure Portal and the roll-out of it.
  • webservice: this user is used by the web service.
  • anonymous: this user plays a central role in Pure as it ensures, for example:
    • the surveillance mechanism can test essential functionalities in Pure, i.e., can Pure access the database
    • the web service can be accessed by non admin accounts - an account is still required.
    • if running the Pure portal that data can flow across the two systems

These users cannot be:

  • Deleted - the root user is needed for accessing Pure
  • Marked as Locked - the root user is needed for accessing Pure
  • Marked for Externally Authenticated- this is to prevent someone accessing a system user, especially the root user, by creating a SSO user that can take over the system user.
  • Change password - the root user is needed for accessing Pure

 

Published at April 08, 2025

Download
Related Articles
  • Supported platforms
  • How Can Cover Sheet Show Cyrillic or Chinese Characters
  • How Do Internal Person Names Appear on Research Outputs
  • Removing Research Outputs From the Filter "Claimed/Disclaimed Research Outputs"
  • Terms of Agreement Configuration
Keywords
  • 5.19.0
  • users
  • system users
  • ddp
  • sync_user
  • root
  • atira user
  • recordlog
  • anonymous

Was this article helpful?

Yes
No
Give feedback about this article

    About Pure

  • Announcements

    Additional Support

  • Events
  • Client Community
  • Training

    Need Help?

  • Contact Us
  • Submit a Support Case
  • My Cases
  • Linkedin
  • Twitter
  • Facebook
  • Youtube
Elsevier logo Relx logo

Copyright © 2025 Elsevier, except certain content provided by third parties.

  • Terms & Conditions Terms & Conditions
  • Privacy policyPrivacy policy
  • AccesibilityAccesibility
  • Cookie SettingsCookie Settings
  • Log in to Pure Help CenterLog in to Helpjuice Center

Knowledge Base Software powered by Helpjuice

Expand