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
  • Training
  • Technical user guides
  • Integrations
  • Synchronizations
  • Database View Synchronization

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

Unified User Synchronisation - ViewsUnified 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 

 

Published at December 04, 2023

Download
Table of Contents
  1. VIEW CREATE STATEMENTS
  2. USER_DATA (Mandatory)
  3. SQL Validation
Related Articles
  • SQL validation for views
  • Configurable Person Synchronisation
  • Configurable Person Synchronisation
Keywords
  • unified views
  • user sync

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