Users

The Create and Edit APIs are defined to be as consistent as possible. Both Create and Edit accept the same JSON, which has several shapes depending on which data you are creating/editing. For more information on Veeva SiteVault User Administration, see Veeva SiteVault Help.

Guidelines

Section link for Guidelines

• A Person record is referencing person__sys.
• A User record is referencing user__sys.
• A “user” object (create) or a “username” referencing an existing user (edit) must be specified. All other API references are consistent.
• Only a single user per API call is supported.
• APIs build on each other and appear in a nested format.
• If a site, organization, or study is specified, you must complete all the site, organization, or study parameters. For example, if you edit a user with an existing add-on permission and do not include it in your call, the user will no longer have that add-on permission.
• You must be in the organization context to add study assignments for other sites within the organization.
• It is possible to make an existing Person/User active if Vault finds an existing Person/User who is currently inactive.
• A person is made inactive in an organization when all access within that organization has been removed.