Users and roles

Workspace members live under Organization / Members (and Settings access). Platform Admin is a different surface for the installation owner (license, tenants, first workspace). A technician is an extra profile on a user — not a substitute for a role.

Three layers (do not mix them)

Layer	Meaning	Where
Marketplace licence	You bought Veldriq on CodeCanyon	License activation
Plan / capability	What this workspace may use (portal, inventory, forms, …)	Plans and capabilities
Permission	What this user role may click	Settings → Roles

Missing a module is often a capability off, not a forgotten permission. Access denied can also be an inactive technician or missing field.workspace.view.

Typical roles

• Admin — configuration, members, settings (workspace.update).
• Dispatcher — work_orders.* + dispatch.assign (and override if they may Assign anyway).
• Technician — field.workspace.view only for Field; they do not get office Complete.

Steps

1. Create the User (email, name, role).
2. If they will use native Field: Workforce → Technicians → Active profile linked to that user.
3. Confirm the role includes the permissions they need. Field still needs the four eligibility items on Field eligibility.

Platform vs workspace

Platform administrators are not automatically Field technicians. Creating a workspace user does not create a technician profile. Workspace members cannot open License & Products or Mail / SMTP unless they are also platform administrators.

Related: Technicians · Settings.