Owner-safe projections
Owner views are designed to remove internal notes, vendor cost/markup posture, raw storage details, and sensitive security context before information becomes owner-facing.
Loading this page.
Trust center
Quoalis security and trust.
Private property operations need more than a login screen. Quoalis is designed around privacy boundaries, owner-safe views, assignment-scoped vendors, reviewed evidence, and human authority. This page answers the questions owners, operators, vendors, and procurement reviewers ask before rollout.
Trust at a glance
Four controls shape every workflow.
Assignment-scoped vendors
Vendor work is packaged around explicit assignments. The product story avoids broad vendor property access as the default operating model.
Provider-managed assurance
Quoalis delegates sign-in, MFA, recovery, and step-up access to the configured identity provider. The marketing site does not collect passwords.
Evidence with review
Media and closeout records are treated as operational evidence. Sensitive evidence should be scanned, reviewed, and intentionally published rather than casually attached.
Detailed security and procurement reviewAccess boundaries, evidence, recovery, claims, and operating limits
Procurement questions
The trust model should be easy to inspect before setup.
Who signs in?
Invited production users authenticate through the configured portal and identity provider.
What does MFA cover?
MFA, recovery, session posture, and step-up checks are managed through the identity provider and reviewed during setup.
Who can see owner data?
Owner-safe views are intentionally different from operator, vendor, field, and account-admin views.
Can public forms create accounts?
No. Public requests start a guided review; production access is invitation-only.
Where does sensitive data go?
Access codes, payment details, alarm context, raw credentials, and private guest data should not be entered into public forms.
What happens before rollout?
The team reviews roles, data boundaries, integrations, support path, and first workflow scope before production setup.
Data boundaries
Different people should not see the same raw record.
Owner
Sees: Decision context, approved evidence, next steps
Excludes: Internal notes, vendor markup, operational chatter
Manager
Sees: Work queue, triage, assignments, review state
Excludes: Credential secrets or bypasses around policy
Vendor
Sees: Scoped package, schedule, requirements, upload path
Excludes: Owner contact details or unrelated property history
Field team
Sees: Assigned tasks, checklists, bounded capture
Excludes: Broad account or portfolio administration
Account admin
Sees: Invites, roles, sessions, account posture
Excludes: Unreviewed production access grants from public requests
AudienceDesigned to seeDesigned to exclude
Owners
Reports, decisions, owner-safe timelines, reviewed evidence
Internal staff notes, vendor markup, raw security/access data
Vendors
Package scope, schedule, messages, assigned evidence upload
Owner contact details, unrelated property history, internal costs
Field teams
Assigned tasks, checklists, bounded evidence capture
Broad account administration, unassigned property records
Operators
Operational command center shaped by capability and context
Secrets, raw credentials, or bypasses around account authority
Visitor route map
Make the next path visible for every buyer.
Visitors can self-select by role, inspect proof, and move toward demo or access without hunting through the full navigation.
Operating principles
Trust is part of the workflow, not a footer link.
Owner-safe projections
Owner views are designed to remove internal notes, vendor cost/markup posture, raw storage details, and sensitive security context before information becomes owner-facing.
Assignment-scoped vendors
Vendor work is packaged around explicit assignments. The product story avoids broad vendor property access as the default operating model.
Provider-managed assurance
Quoalis delegates sign-in, MFA, recovery, and step-up access to the configured identity provider. The marketing site does not collect passwords.
Evidence with review
Media and closeout records are treated as operational evidence. Sensitive evidence should be scanned, reviewed, and intentionally published rather than casually attached.
Human-in-the-loop actions
The platform can structure recommendations and workflows, but sensitive actions still route through policy, owner authority, staff review, or step-up controls.
Guided rollout
New teams start with a reviewed workflow, support model, security posture, and data boundary map before broader availability claims.
Trust visuals
Security, vendor scope, and access review are visible product stories.
Account security posture
Provider-managed MFA, session review, invitations, and account context are treated as operating controls.
Package-scoped execution
Vendors and field teams get bounded work views instead of broad owner or property records.
Reviewed access setup
Intake, onboarding evidence, setup checks, and approval records come before production-scale claims.
Access support
MFA, invites, and role changes stay provider-led and reviewed.
Public pages can route the support question, but production identity changes stay inside the configured portal, identity provider, and account-review process.
Invite mismatch
Confirm the intended role, workspace, and identity provider before a new invitation is sent.
MFA recovery
Use the configured provider recovery path; public forms collect only high-level routing context.
Role change
Account support reviews authority, property scope, and audit context before access changes.
Vendor onboarding
Vendor users start from package scope and move to production access only after operator review.
Safe to say
- Designed around role-aware access and owner-safe projections.
- Supports provider-managed MFA and step-up posture through the portal architecture.
- Uses human-reviewed workflows for sensitive operational decisions.
- Treats vendor access as package/assignment scoped.
Do not claim yet
- Fully public self-serve SaaS availability.
- Autonomous emergency dispatch or guaranteed emergency response.
- Central alarm monitoring, payment custody, or insurance coverage.
- Compliance certification or breach-proof security.
Claims and proof
Claims should state what buyers can inspect and what remains protected.
Available to review
The platform supports multiple persona-specific interfaces.
Proof/source: Owner, operator, vendor, field, account-admin, and evaluator journeys are documented and represented in product boards.
Safe wording: Separate owner, operator, vendor, field, and account-admin front doors.
Avoid: Everyone sees the same dashboard.
Available to review
Vendors are assignment/package scoped.
Proof/source: Vendor and field work board, package-scoped demo path, and trust boundary language.
Safe wording: Vendors work from package-only views.
Avoid: Vendors get property access.
Guided setup
Account governance includes MFA posture and step-up assumptions.
Proof/source: Account security board and provider-managed assurance language.
Safe wording: Provider-managed MFA posture and step-up support.
Avoid: The app stores authenticator secrets.
Discovery
Voice-assisted owner intake is architected.
Proof/source: Owner voice architecture and use-case sequence docs.
Safe wording: Future voice-assisted drafting with owner confirmation and staff review.
Avoid: Live autonomous voice commands.
Excluded
Payments, emergency dispatch, central monitoring, and compliance guarantees are not offered.
Proof/source: Boundary matrix and what-we-do-not-do source language.
Safe wording: The platform structures escalation, evidence, and review workflows.
Avoid: The platform guarantees response, approval, or payment handling.
Buyer objections
Answer the hard questions without stretching the product posture.
Is this just property-management software?
No. The platform is designed for private-property operations where owners, operators, vendors, field teams, and account admins need different views of the same work.
Why not use email, spreadsheets, and shared folders?
Those tools are flexible, but they do not enforce owner-safe views, vendor boundaries, authority, evidence lifecycle, account context, audit, or workflow history.
Can vendors see private owner or property information?
The intended vendor model is package-scoped: scope, schedule, package messages, terms, and evidence requirements without owner contacts, security detail, internal markup, or unrelated records.
Does this automatically dispatch vendors?
No autonomous dispatch claim should be made. Vendor packages and readiness gates remain controlled, reviewed, and policy-bound.
Does this handle payments?
No. The platform can model closeout, charge candidates, owner decisions, and finance-adjacent evidence, but it does not hold funds or operate as a payment processor.
Can it guarantee event compliance?
No. Event/catering workflows can track readiness, required items, approvals, and documentation; they do not provide legal, permit, alcohol, food-service, insurance, or fire-code approval.
What the platform does not do
The boundary is part of the trust story.
Quoalis structures private-property operations. It does not replace the people, licenses, policies, emergency services, contracts, or professional judgment required to perform real-world work safely.
AreaCan help withDoes not do
Emergency response
Record requests, surface status, support escalation workflows, and preserve evidence.
Guarantee emergency response, dispatch first responders, or replace 911/emergency services.
Vendor coordination
Scope packages, collect quotes, manage package messages, track evidence and closeout.
Perform licensed trade work, automatically verify every license/insurance posture, or replace vendor contracts.
Payments and billing
Track closeout evidence, charge candidates, owner decisions, and finance-adjacent records.
Hold client funds, process payments, escrow money, or act as a payment processor.
Compliance
Track readiness items, required documentation, and review posture.
Provide legal advice, permit approval, food-service approval, insurance coverage, or guaranteed compliance.
Security and alarms
Coordinate home-technology/security-related work and record operational context.
Operate as a central alarm station or monitor emergency/security events as a regulated alarm service.
AI and voice
Assist drafting, summarization, intake, and future owner-confirmed requests.
Execute autonomous real-world actions or voice commands without confirmation and review gates.
Public access
Capture interest and reviewed access requests.
Instantly provision a production tenant from a public form.
Adoption posture
Start narrow. Prove value. Expand with evidence.
Trust claims should follow configured identity providers, support posture, backup/restore practice, and security review. The stronger buyer story is practical: show the workflow, explain the boundaries, and grant access only after reviewed scope.
Request access