Sharing and access
Shared as widely, or as narrowly, as you meant.
A plan can be open to anybody with the link, gated behind a name and an email address, locked with a passcode, or not reachable at all. Every one of those is enforced on the server.
The three visibility settings
One setting on the plan, checked on every request.
| Setting | Who can open it | What a wrong guess gets | What is given away before entry |
|---|---|---|---|
| Public | Anybody with the link, optionally after an unlock form | Nothing to guess | The plan, or its name and your branding when a form is in the way |
| Private | Anybody with the link and the passcode | A wrong code, and a limit on how often it can be tried | Your branding and the fact that a plan exists. Not its name |
| Draft | Nobody | The same answer as a plan that never existed | Nothing |
Passcodes
A passcode is a short code you set on the plan, or generate. Generated codes leave out the characters people misread when a code is being read down a phone, so there is no distinguishing a capital O from a zero or a lowercase L from a one.
A passcode protected plan gives up almost nothing before the code is right. The reader gets your branding and a box, and that is all: no plan name, no room count, no floor area, not even the total on a listing of the property. The name of a suite can itself be the sensitive part, and a lock screen that announces what it is guarding is not much of a lock.
Guesses are rate limited, and the limit is counted before the code is checked. Guessing wrong therefore costs exactly what guessing right costs, so a script cannot work its way through the possibilities.
Changing the passcode retires access for everybody who unlocked the plan with the old one. There is no list to clear out and no sweep to wait for: the old code stops working the moment the new one is saved.
The unlock form
A public plan can ask for a name and an email address before it opens, and a phone number as well where you want one. You write the sentence that appears above the form, so it can explain why you are asking.
What somebody types becomes a lead in QuickCasa, attached to the property the plan belongs to, and from there it is an ordinary lead: assignable, workable, and eligible for the automatic follow up you already run. A floorplan behind a form is a listing page that generates leads instead of a file that generates nothing.
This is a softer gate than a passcode on purpose. The name of the plan is shown before the form, because the plan being named is the reason anybody would fill the form in.
Who has opened a plan
Getting past a gate creates an access grant, which is what the reader holds for the next thirty days so they are not asked again on every visit. The portal lists them, newest first.
A form unlock carries the name and email address that were given. A passcode unlock does not, because nobody was asked, so it is a count rather than a name. Both are worth having: one tells you who is interested, the other tells you how much interest there is.
Comments
A plan can take comments, pinned to whichever room the reader had open when they wrote one.
Nothing publishes itself
Every comment arrives for review. There is no path by which something a stranger typed appears to other readers without somebody at your company approving it.
Team only, or public
Approved comments can either be shown to other readers or kept for your team alone. Team only turns the box into a private channel from a renter to you.
The form says which it is
Where comments are never published, the box says so before somebody writes one. Telling a renter their comment is awaiting review, on a plan where it will never be shown, would be a lie by omission.
Attached to a room
A comment picks up the space the reader has open, so a question about the second bedroom arrives labelled as being about the second bedroom.
Whether readers may pass it on
The share button is yours to allow
When it is on, a reader gets a panel of social destinations, a copy button and a QR code. When it is off, the panel is not there.
It is a convenience, not a control
Turning the share button off does not stop anybody sending the link, because the link is in their address bar either way. Nothing in the product implies otherwise. If a plan must not travel, that is what a passcode is for.
A QR code for the room you are standing in
The code is drawn in the reader's browser the instant the panel opens, so holding a phone up at a showing works at the speed the moment requires.
What is never in the page at all
Gates decide whether a reader gets a plan. A separate check decides what is inside the plan they get, and it runs every time regardless of how they arrived.
Private notes, private attachments, the instructions your AI assistant reads, and the internal links between a drawn room and the inventory record behind it are all removed on the server. The plan is rebuilt field by field rather than copied and trimmed, which means a new internal field added in the portal next year is absent from the public payload by default. Somebody has to decide to publish it.
The practical consequence is that there is nothing to find by reading the page source, opening developer tools, or asking the browser what it downloaded. It was never sent.
Put a plan in front of your next renter.
Floorplans are part of QuickCasa, so the drawing, the listing and the lead it brings in all live in one place. Book a demo and we will show you what it looks like with your own properties.