ReferenceDevRev object types
revu fields
Field reference for the `revu` target. Required fields must be mapped or have a supported creation fallback.
Field reference for the revu target. Required fields must be mapped or have a supported creation fallback.
Catalog generated July 13, 2026. Validate the mapping in your target organization. Can Load means external → DevRev; Can Extract means DevRev → external. See field rules for required values and references.
Resource Type: rev_user
Capabilities: Can App Fragment, Can Load
Fields
| Field | Type | Required | Description |
|---|---|---|---|
airsync_shared_with | permission (collection) | List of users and groups who have explicit access to the item and the corresponding roles. | |
associations | reference (collection) → [#record:account] | List of Accounts that the Rev user is associated with. | |
browser | text | Browser name and version of the user. | |
browser_language | text | Language of browser of the user. | |
created_by_id | reference → [#category:user] | User ID of the user that created the object. | |
description | rich_text | Description of the Rev user. | |
display_name | text | ✔︎ | The user's display name. The name is non-unique and mutable. |
email | text | Email address of the user. | |
external_refs | text (collection) | External refs are mutable unique identifiers for a contact record. If none are available, a good alternative is the email address(es)/phone number(s) which could uniquely identify the contact. If no identifier is specified, a system-generated identifier will be assigned to the contact. For organizations with multi-association contacts support enabled, this field accepts multiple identifiers, where each identifier must be unique across your DevOrg. For organizations without multi-association contacts support, this field accepts a single identifier, maintaining functionality consistent with the existing external_uid field. | |
external_uid | text | External ref is a mutable unique identifier for a user within the Rev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user. | |
full_name | text | Full name of the user. | |
item_url_field | text | Link to the item in the origin system. | |
modified_by_id | reference → [#category:user] | User ID of the user that last modified the object. | |
phone_numbers | text (collection) | Phone numbers of the user. | |
plug_availability | enum | Status of the user on the PLuG. | |
tags | reference (collection) → [#record:tag] | Tags associated with the object. |
Enum values
plug_availability
| Value | Name | Description |
|---|---|---|
offline | offline | - |
online | online | - |
Last updated on