Who should use Veldriq Field
Veldriq Field
Native Field is for assigned field technicians. It is not for platform administrators, customer portal users, or public-booking guests.
Screen path in the office (setup, not this app): Workforce → Technicians plus Settings → roles that grant field.workspace.view. On the phone: Welcome back → Today.
Eligibility (all required)
Section titled “Eligibility (all required)”| Layer | Meaning |
|---|---|
| User | Staff login (email/password). Not a portal identity. |
| Workspace membership | Active membership on that tenant |
| Permission | field.workspace.view on the role |
| Technician | Active technician profile linked to that user |
| Licence | Field activated on that deployment |
A workspace admin without an Active technician profile cannot use Field. Buying the app does not create assignments. Admin / super-admin inference does not substitute for the technician profile.
Loop (office then technician)
Section titled “Loop (office then technician)”- Office creates the User and an Active technician (Workforce → Technicians).
- Office grants
field.workspace.viewand keeps membership Active. - Platform Admin activates Field on License & Products.
- Technician signs in with the same work email and password.
- Office assigns an appointment to that technician. Field lists stay per assignee.
What works / does not work
Section titled “What works / does not work”| Actor | Can use Field | Cannot |
|---|---|---|
| Active technician + permission | Yes | Create work orders, dispatch others, invoice |
| CMS admin, no technician profile | No | “Just use my admin login” |
| Portal customer / magic link | No | This Welcome back screen |
| Public-booking guest | No | This app |
Office setup: Technicians · Users and roles · Field licence.
If the phone says No eligible Field workspace for this account: the User exists but Field eligibility is incomplete. Create the Active technician; do not issue a Profile API token.