DemandFlow Support Centre

PORTALUSER: Portal User

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The PORTALUSER entity represents external user accounts for customer-facing portals. Stored as standard objects in the tenant's DynamoDB table, separate from internal DemandFlow users. Each portal user is scoped to a specific PORTALCONFIG record via comboKey.

PORTALUSER: Portal User

The PORTALUSER entity represents external user accounts for customer-facing portals. Stored as standard objects in the tenant's DynamoDB table, separate from internal DemandFlow users. Each portal user is scoped to a specific PORTALCONFIG record via comboKey.

Default definition. This article describes the default PORTALUSER definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches PORTALUSER.

Entity properties

PropertyValue
Entity codePORTALUSER
Display namePortal User
PluralPortal Users
Level60100

Use cases

Portal users authenticate via separate portal auth Lambdas (portalAuthLogin, portalAuthRegister) which manage passwordHash, passwordSalt, resetToken, and resetTokenExpiry fields directly on the object. These fields are NOT in the definition and should never be exposed in the UI. The comboKey format is SUB:{sId}|PORTAL:{portalConfigId}|ENT: to scope users per portal.

Fields

General

FieldTypeRequiredNotes
nametextYesFull Name.
emailtextYesUsed as the login identifier for the portal.
statusenumStatus. Valid ids: 1 (Active), 2 (Suspended), 3 (Pending Verification).
portalConfigIdtextThe PORTALCONFIG record this user belongs to. Read-only.
emailVerifiedbooleanEmail Verified.
lastLogindatetimeLast Login. Read-only.

Additional panels

  • Activity timeline panel attached.

Relationships

  • No declared relationships in the default definition.

Creating a Portal User via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "PORTALUSER",
  "level":    60100,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "email": "example@example.com",
  "status": "1",
  "emailVerified": true
}

Listing PORTALUSER records

# All portal users in your tenant
GET /v1/entities/PORTALUSER/SUB

See also

portaluserportal userportal usersportaluser

Was this article helpful?

← Back to Knowledge Base