How Can We Help?
System UsersSystem Users
Pure has a number of system users. These users are essential for keeping central parts of Pure running and are defined in the table below.
| User | Description |
|---|---|
| root | Used for running various jobs in Pure. |
| sync_user | Used for running various jobs in Pure. |
| 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 lock it or change password for it, the Pure Portal will not be able to fetch updates to the portal from web service. |
| recordlog | This user was created in 5.32.0 and is used 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:
|
These users cannot be
- Deleted
- Marked for Externally Authenticated
- Marked as Locked (not applicable to all)
- Change password (not applicable to all)
Published at October 22, 2025