Published at October 26th, 2025 • Last updated 8 days ago

Unified User Synchronisation - Views

VIEW CREATE STATEMENTS

Download Postgres user view create statements

Download Oracle user view create statements

 

USER_DATA (Mandatory)

This view is used to list all the users (people who can log in and use Pure) you want to synchronise into Pure. This means that one row should exist in this view per user you want to have in Pure. For each user you have to specify a USER_ID in the PERSON_DATA table, which corresponds to ID in this table. This means that this ID has to be unique for each user and cannot change over time. It's strongly recommended not to use the same ID for user as for person. ID for user could for example be prefixed with "USER". The USER_ID will be used to create "personal users" - the least privileged users of Pure, who can create content, and push it to other, more powerful users. Additional privileges can be added to users within Pure.

The User synchronisation should be executed prior to the Person synchronisation.

 

Column name

Data type

Size

Mandatory

Note

Sync type.

For each field pick on of: 'Yes', 'No', 'Once'
ID String 1024 Yes This is unique ID of the User. Keep above description in mind when defining user ids.
 		  
FIRST_NAME String 1024 No The first name of the user.  
LAST_NAME String 1024 No The last name of the user.  
USER_NAME String 256 Yes

This represents one part of the security credentials for the user, and must be unique. Can be used to link to an SSO system.

We do not recommend re-using usernames after a user has been retired, as that will make attribution of historical changes in the audit log cumbersome.

  
EMAIL String
  		256 Yes The email address of the user  

SQL Validation

SQL validation for views 

 

Was this article helpful?

Related articles