Enforced boundaries
Most software tells you what it does. These are the 198 buyer-visible refusal statements describing what this one will not do across 54 protected product areas.
How to read this page
The themes below are our grouping of the questions buyers, security reviewers and procurement teams actually ask. The refusals inside them are whatever exists: a theme with four entries has four, because we did not write a fifth to balance the column. The remaining 171 boundaries are narrower and live on their module pages.
20 modules are represented. Each entry links to the module page so the same refusal can be reviewed in its product context.
All 61 protected modulesDoes this software ever hold, move, or charge money?
5 enforced refusals in this theme.
The accounting and payments workbench prepares evidence, classifications, export mappings, and payment packets for human review. It does not move money, file taxes, submit 1099s, create live QuickBooks records, or expose internal vendor cost or coordination markup to owners.
Reviewed product boundaryConcierge intake records an owner-safe request for human review. Receipt is not acceptance, dispatch, scheduling, purchasing, or an emergency-response guarantee. Do not submit access or security credentials, payment details, private guest data, vendor wholesale pricing, or raw media identifiers. Quoalis does not store payment instruments or custody client funds here.
Reviewed product boundaryTime and cost entries are staff-reviewed operational records only. They do not run payroll, pay vendors, create invoices, charge cards, expose loaded labor rates to owners/vendors, publish raw GPS, or write accounting ledgers.
Reviewed product boundaryVendor administration stores business profile, service-fit, compliance metadata, and review posture only. It does not store raw W-9/TIN values, bank details, payment instructions, access/security codes, vendor markups, or evidence object keys.
Reviewed product boundaryCommercial authorization packets are start-of-service evidence only. They do not create billing-provider customers, invoices, subscriptions, payment methods, financial charges, email, access grants, imports, monitoring, or dispatch.
Reviewed product boundaryWill it send someone, or act, without a human deciding?
7 enforced refusals in this theme.
Reserve provides issue acknowledgement and property coordination, not emergency dispatch, alarm monitoring, physical security, guaranteed arrival, or guaranteed resolution.
Reviewed product boundaryMaintenance requests capture property care needs, triage decisions, owner-safe updates, and manual follow-up status. Quoalis does not guarantee emergency response through this portal, store access/security secrets in ordinary request data, expose vendor pricing or markups, process payments/client funds, or automatically dispatch vendors.
Reviewed product boundaryConcierge execution coordinates an explicitly scheduled property-team visit. It does not automatically dispatch staff or vendors, promise emergency response or arrival, expose access or security details, or send owner notifications without staff review. Owner views contain only reviewed closeout language and explicitly owner-visible ready evidence.
Reviewed product boundaryThe owner approval center centralizes review packets and decision posture. It does not auto-approve, bypass authority policies, send tenant-sensitive notices, execute payments, or dispatch vendors without a valid approval.
Reviewed product boundaryAction links open existing source workflows. They do not automatically dispatch, approve, pay, alter source records, or override required human review.
Reviewed product boundarySnow routes coordinate winter access work only. They do not optimize routes, auto-dispatch vendors, expose access/security details, show vendor pricing, promise emergency response, or guarantee arrival/resolution times.
Reviewed product boundaryReserve notification adapters are release-gate contracts only. This API does not send live email, SMS, WhatsApp, push, emergency, alarm, utility, or dispatch notifications.
Reviewed product boundaryIs anyone being watched, tracked, or recorded?
6 enforced refusals in this theme.
This is an assignment-only field route packet. It uses synthetic relative context and is not live tracking, route optimization, surveillance, or an emergency-dispatch tool.
Reviewed product boundaryThis staff-only preview assembles role-specific map status overlays from authorized records and property markers. A marker is a coarse canvas cell, either projected from the single coordinate a person recorded for the property or, when none is recorded, derived from the property identifier; every marker states which of the two it is. It is not live GPS, route optimization, occupant tracking, camera monitoring, alarm monitoring, emergency dispatch, provider writeback, or automated ticket prioritization.
Reviewed product boundaryIoT signals become reviewable ticket candidates only. This endpoint does not dispatch, notify emergency services, expose device coordinates, publish owner alerts, or create work without an operator review.
Reviewed product boundaryHome technology records show reliable status and planned care only. They exclude raw CCTV, continuous telemetry, access or alarm credentials, remote controls, network secrets, drone mitigation, and automated dispatch.
Reviewed product boundaryThe physical security registry tracks equipment, responsibility, privacy posture, service tier, and maintenance readiness. It does not promise emergency monitoring, police dispatch, live surveillance staffing, or access-code disclosure, and it stores no credential, stream URL, or provider secret.
Reviewed product boundaryPhone records are provider-neutral operational metadata only. Raw phone numbers, live carrier commands, recording files, transcripts, payment data, and secrets are excluded.
Reviewed product boundaryDoes it decide anything a lawyer or an appraiser should decide?
4 enforced refusals in this theme.
Compliance localization tracks jurisdiction, source, version, review, export, and delivery posture. It does not provide legal advice, jurisdiction-specific legal wording, court filing, eviction authority, or automated notice sending.
Reviewed product boundaryTenant lifecycle workflows organize reminders, checklists, evidence, and review packets. They do not provide legal advice, jurisdiction-specific notice automation, court filing, eviction authority, or payment collection, and they hold no tenant identity.
Reviewed product boundaryUnit tenancies record which unit is occupied, by what kind of arrangement, and over what window. They hold no tenant identity, contact details, payment data, lease documents, or screening results, and recording a tenancy neither creates nor terminates a legal agreement.
Reviewed product boundaryValuation-support language is a source-backed narrative only: it may describe history, readiness, amenities, and income-potential support, but it must not guarantee valuation, forecast income as certain, or replace a licensed appraisal.
Reviewed product boundaryCan anything in here open a door or sign someone in?
5 enforced refusals in this theme.
QR codes are context pointers only. They do not grant sign-in, MFA, property access, owner authority, vendor package scope, payments, access codes, or emergency dispatch.
Reviewed product boundarySix-digit email codes verify mailbox reachability only. They do not reset provider passwords inside Quoalis, replace MFA/passkey step-up, approve spending, grant property scope, or authorize account changes.
Reviewed product boundaryIntegration records are provider-neutral, account-scoped, and audit-ready. Credentials and private calendar URLs are accepted only through write-only setup, are never returned, and belong only in the server-side vault. Calendar reads store busy windows only. No scraping, payment movement, tax filing, private event detail, or unreviewed external write is performed by these endpoints.
Reviewed product boundaryVendor work packages are purpose-built, expiring assignments. Creating a package does not grant generic property access, confirm vendor availability, approve owner cost, or authorize work before explicit vendor acceptance, assignment, and operator dispatch.
Reviewed product boundaryAccess grant adapter packets are dry-run grant intents only. They do not create account, workspace, property, vendor, field, or owner-decision access rows.
Reviewed product boundaryWhat we left out
One governs Quoalis’s own marketing rather than the product — it decides whether we may make a customer-facing Reserve service claim at all — and reads as circular on a page of product refusals. The other is written in engineering register about drafts, assignment authorization and submission APIs, and answers a question no buyer asked. Both still render verbatim on their module pages, where the surrounding context makes them legible.
Nothing was dropped for being unflattering. If a refusal is missing from a theme, it is because the code does not make it.
How we evidence thisPilot access
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
We respond with the recommended demo route, who should attend, and what production access would require.