Personas and account model
Quoalis provides five work perspectives: operator, owner, vendor, field and advisor. A person's available actions also depend on their role, account membership and permitted property or assignment scope.
Operator / property manager
Operators coordinate requests, property work, assignments, vendors and owner updates. Start with the current work queue, identify the responsible person and open the exact request before taking an action.
Owner
Owners review property status, decisions, evidence and reports within their permitted properties. Check the selected property and reporting period before reviewing costs or recording a decision. Missing or pending evidence should be resolved with the operating team.
Vendor
Vendors work within assigned packages and approved scope. Review the current offer, permitted access window, required proof and closeout instructions. Company dispatch and individual technician permissions can differ.
Field team
Field users carry out assigned visits and capture observations and evidence. Select the exact visit before entering work, and review its instructions and evidence requirements. Device-saved or queued work is distinct from server-confirmed submission.
Advisor
Advisors inspect authorized property information and reviewed reporting. The advisor perspective is read-only; owner decisions, dispatch and field completion belong to roles with those capabilities.
Account administration
Account administration is a permission-bearing role, rather than a sixth work persona. Authorized administrators manage invitations, membership, property access and account settings. An invitation alone does not grant every account or property.
Context and access
Keep account, property, assignment and reporting-period context in view. Switching accounts or work perspectives can change both visible records and available actions. Private owner information, operational notes and vendor instructions are shared according to their scope.
Private events are a workflow involving these roles, rather than a separate access persona. Guest request intake is separate from authenticated workspace access.
For a first task and recovery guidance, read First-task help. A public tour uses synthetic examples; a production workspace requires reviewed invitation and identity setup.