Identities
An Identity is an account that can authenticate with the platform - either a human user logging into a portal, or a service account used by automated processes. Each identity has exactly one Role that determines its system-level access. Identities are managed by users with the Security Administrator role.
The Identities screen
Section titled “The Identities screen”Navigate to Security - Identities to see all identities in the current application:
| Column | Description |
|---|---|
| User ID | The identity’s login identifier (typically an email address for user accounts) |
| Role | The role assigned to this identity |
| Identity Type | User Account or Service Account |
| First Name | First name (user accounts only) |
| Last Name | Last name (user accounts only) |
| Is Active | Whether the identity can currently log in |
| Use 2FA | Whether two-factor authentication is enabled |
Use + Add Identity to create a new identity. Selecting rows and clicking Delete deactivates the selected identities (sets Is Active to false) rather than permanently removing them.
Identity types
Section titled “Identity types”User Account - a human user who logs in with a username and password. Has personal profile fields (First Name, Last Name, phone number, profile image) and can use two-factor authentication.
Service Account - a non-human account used for automated processes, integrations, or background tasks. Has no personal profile fields and no password-based login. The Run As User setting on Scheduled Triggers typically references a service account.
Creating and editing an identity
Section titled “Creating and editing an identity”Clicking + Add Identity or an existing identity row opens the identity panel. Fields vary by Identity Type:
Fields for both types:
| Field | Description |
|---|---|
| Identity ID | The login identifier - typically an email address for user accounts, or a descriptive name for service accounts. Click Change ID to update it on an existing identity. |
| Identity Role | The Role assigned to this identity |
| Identity Type | User Account or Service Account |
Additional fields for User Accounts:
| Field | Description |
|---|---|
| First Name | User’s first name |
| Last Name | User’s last name |
| Use 2FA | Enable two-factor authentication for this account |
| Mobile Phone Number | Used for 2FA delivery |
| Profile Image | Avatar shown in the platform UI |
Bottom actions on an existing identity:
- Change Password (user accounts only) - set a new password for the account
- Deactivate Account - disables login without deleting the identity
- Save - save changes
The system_user account
Section titled “The system_user account”system_user is a built-in service account present in every application. It is used for internal system maintenance and is the default Run As User for scheduled automation. It cannot be modified or deleted. It can also be used as the execution identity for your own Scheduled Triggers when you want automation to run with administrator-level access without tying it to a specific person.
Where identities go from here
Section titled “Where identities go from here”Identities appear as User dimension options in security rules on navigation items, Database Workflows, Server Functions, and other resources that support per-user access control.