Setting it up

On the Payouts page under Payment requests, create a request and turn on Pay it down over time. You name the Total owing and the Smallest instalment you will accept. The payer gets a page that leads with what is still owed, shows how much has already been cleared, and lets them send whatever they can toward it. The same link keeps working for the next payment and the one after that.

What naming the total changes

• Nobody can pay more than is still owing. The page refuses an amount above the remaining balance rather than taking it and leaving you to hand the difference back.
• The last instalment is allowed below your minimum. The floor exists to stop token payments, not to strand somebody twelve dollars from square, so it drops with the remaining balance.
• The request closes itself when the balance reaches zero. The payer is told it has been paid in full rather than being invited to pay again.
• A refund puts the money back on the balance and reopens the request. The same link starts working again, because that instalment is genuinely owed once more.

What it is not

It is not a subscription and it schedules nothing. No date is set, no reminder is sent by the request itself, and no card is ever charged automatically. The payer decides when, and how much, every time. If you want to chase them on a rhythm, that is a cadence or a follow-up.

Paying down works with everything else on a request. It can be linked to a resident, so each instalment posts to their ledger and reduces what they owe, and it can offer your offline methods alongside. It cannot be a hold, because a hold reserves money instead of collecting it.

Archiving

Archive is on every conversation row in the Inbox, as the box icon that appears when you hover the row, and in the thread header at the top of an open conversation. Archiving removes the conversation from the Conversations list, from the inbox filters, and from the unread count on the sidebar.

It is the same archive the CRM uses. An archived conversation also leaves the CRM board and the leads lists, and shows up under the CRM's Archived tab. Nothing is deleted and the lead keeps its full history.

Finding it again

Archived is the third tab above the conversation list, beside Conversations and Spam. It lists what has been archived, most recently updated first, and the search and filters still apply to it.

Restore puts a conversation back. Use the box icon on an archived row, or the Restore button in the thread header, and it returns to the Conversations list immediately.

Two things to know

Archiving is a per-company action rather than a per-person one, so a conversation one teammate archives is archived for everybody.

Archiving is different from banning. Banning is a QuickCasa staff action for spam and bad actors that keeps the person out of the inbox permanently. Archiving is a normal tidy-up any employee can do and undo.

Where

Open a lead and find the Duplicates section on their profile, or use the Merge Duplicate quick action on a card in the CRM board's quick view.

How it works

The picker lists every other lead in the company, with likely duplicates (a matching email or phone number) at the top and labelled with why they matched. Search narrows the list by name, email, phone, flow or stage. Pick the other card, then choose which card stays. By default it is the one you opened the picker from. The merge cannot be undone.

What comes across

• Notes from both cards, in time order, plus a note recording the merge and who did it.
• Follow-ups, cadence enrolments, escalations, NPS surveys, quotes, bookings, signing requests, form submissions and activity history, all re-pointed to the surviving card.
• The conversation history from both cards, shown together on the profile.
• Tags, properties of interest, amenity wishes, assigned owners and contact opt-outs, combined.
• Contact details, budget, bedrooms and any other detail the surviving card did not have but the other one did.

The surviving card keeps its own stage, owner, score, flow and channel. The other card's stage and score do not override it. If the other card had a business goal further along, such as a completed booking, that progress is kept.

Afterwards

The merged-away card is removed from the CRM board, the leads list, the inbox and search. A new message from either identity, the original email or the later phone number, lands on the surviving card rather than recreating the duplicate.

Merging is a manual action only. QuickCasa never merges two cards on its own.

Installing it

Chrome or Edge on a computer: an install icon appears at the right-hand end of the address bar, and QuickCasa offers an install card in the bottom corner once you have been signed in for a moment. Dismiss the card and it stays away for a month. Android: the same card appears, and Chrome's own menu has Install app. iPhone and iPad: Safari never offers to install anything on its own, so QuickCasa shows the steps: Share, then Add to Home Screen. Safari on a Mac: File, then Add to Dock, on Safari 17 or later. Firefox does not install web apps on the desktop, so nothing is offered there.

Once installed, the portal opens with no address bar, keeps a launcher icon, and appears in the task switcher as a separate app. Right-clicking or long-pressing the icon jumps straight to the Dashboard, the lead board or the Inbox. Installing changes nothing about your account or your data.

Device notifications

Open the bell in the top bar and there is an invitation to turn on device notifications for the browser you are in. After that, notifications arrive as ordinary notifications from your operating system, on the lock screen or in the notification centre, whether or not QuickCasa is open. It is per browser, so turning it on at your desk does not turn it on for your phone.

A notification about a lead carries two buttons: View opens the lead's profile and Reply opens straight to their conversation. Chrome, Edge and Firefox show them. Safari does not support notification buttons, but tapping the notification itself still opens it in the portal. Low-priority items such as a feature announcement stay on the bell only, and if you are installed, the app icon carries your unread count.

On an iPhone or iPad this only works once QuickCasa is on the home screen. Safari will not deliver notifications to a website in a tab.

Offline, and updates

With no connection, the installed app still opens, and a marker across the bottom says you are offline and nothing on screen is updating. When the connection returns, the marker disappears and live data resumes on its own. Updates download in the background. A message says a new version is ready, and ignoring it is fine, because the release is applied the next time you move between pages.

How an application behaves

• The applicant signs in first. Before it shows a single screen, the applicant signs in with their QuickPass account (email and password, Google, or an emailed sign-in link) or creates one on the spot. That account owns the application.
• Progress follows the account, not the browser. Every answer is saved as they go. Closing the tab, switching from phone to laptop, or coming back a week later puts them back on the exact screen they left.
• No starting over. Each applicant has exactly one application per form: not started, in progress, or submitted. Opening a submitted application shows when it was received and nothing else.
• Answers lock at checkpoints. The applicant can go back to fix a typo right up until they pass a checkpoint: reaching a checklist, finishing a checklist task, a payment that went through, or a verification that passed. Once past one, everything before it is committed.
• One screen at a time. An application ignores the scrollable display mode.

Applications are submitted without the bot challenge. The signed-in account is the proof of a real person.

Checklists

An application can contain a Checklist screen: a hub of tasks the applicant has to finish, in any order, before the form moves on. Before you sign, complete these: identity verification, upload your pay stubs, add two references. Each task is its own set of screens wired off the checklist. Finishing a task ticks it and locks it, an unfinished one can be left and picked up later, and Continue only becomes available when every task is done. Checklists are only offered on applications.

What your team sees

On the results page of an application, every row shows the applicant's name and email from their QuickPass account and a status: in progress with how far along they are, or submitted. Drafts are visible, so you can see who has started and stalled.

It uses QuickPay, so the money settles into your company's own Stripe account under the same rules as every other QuickPay payment: the same card and bank rails, the same card fee posture, the same statement, the same refunds. Card details are entered inside Stripe's own fields and never touch QuickCasa.

Setting it up

Add the Payment screen in the flow form editor and choose:

• Amount. A fixed figure, an amount the payer types, or an amount worked out earlier in the form and referenced as a variable. The two variable options ask for a smallest and largest amount, which is what the server enforces. A form that has to guarantee what it collects should use a fixed amount.
• Ways to pay. Card, bank account, or both.
• When to take the money. Charge it right away, or hold it on the card and decide later. A hold is card only, and Stripe releases an uncaptured hold after about a week, so take or release it from the Payouts page before then.
• Who covers the card fee. Follow the company setting, or override it for this screen.
• Category. Books the money under the same categories the resident ledger uses.
• Payment required. On, the form will not move past the screen until the payment is made. Off, the payer can carry on without paying.

What it writes back

The screen records the status (paid, processing, held or skipped), the amount, the method and the payment id, so a later branch can route on whether somebody paid, an end screen can print the amount, and the submission itself shows what was collected.

Each form payment raises a payment request behind the scenes, so it appears on the Payouts page under Payment requests, labelled with the form it came from, and on the company payments statement. Refunds work from there too.

Two things to know

Your company has to have finished QuickPay onboarding. Until it has, the screen tells the payer that payments are not set up rather than asking for a card. And a bank payment takes a few business days to clear while a hold takes nothing at all, so neither is worded as a completed payment on the form.

Sending it

Open the document's Fill page, enter the values that are yours, then choose Send for signature instead of Fill Document. You give the signer's name and email, choose which image field receives the drawn signature, tick any other fields you are leaving to them, and add an optional note for the email.

Your fields are checked before anything goes out, so a lease with a blank rent cannot be sent. The request then appears on the document's Signatures page with its status: sent, opened, signed, declined, cancelled or expired. Links stop working after 30 days, and an open request can be cancelled from that page.

What the signer sees

The email names your company and the document. The link opens a page that shows the whole document first, then asks for their fields, a drawn signature (finger, stylus or mouse), their typed full name, and a tick beside the consent wording. Nothing is sent until they press Sign. They can decline instead, with an optional reason, and you are emailed either way.

What you both get

The document is rendered with your values, theirs and their signature, and a signature certificate is appended as the last page. It records who sent it, who signed, when the link was sent, opened and signed, the network address and browser used, the consent wording agreed to, and a SHA-256 fingerprint of the signed pages. Both parties are emailed a link to the signed file along with the fingerprint of the whole file, so anybody holding a copy can confirm it has not changed.

The signed file is recorded in the document's History, and if the request was sent from a lead, the signing is written to that lead's activity.

QuickCasa is not a law firm and this is not legal advice, but the signature captures intent, consent, attribution and integrity, which is the same class of signature the large e-signature products provide.

Asking one person

Open a lead and find the Verifications section. Request asks that person directly: pick which of your forms does the asking, the lead's email is filled in for you, and you can add a short note. They get an email naming your company and linking straight to the form. The link works for 14 days, and the section shows where the request got to: waiting on them, in progress, being reviewed, verified, not verified, expired or cancelled. Cancel request withdraws an unanswered ask.

Asking everyone who applies

Add a Verify screen to a flow form and anyone filling it in is asked to prove something before they carry on. It can prove government ID, income or available funds, can be required or optional, and can offer the renter a free QuickPass to keep the result on. Only forms with a live Verify screen are offered when you request from a lead page.

Before any check runs, QuickCasa looks for one the person has already passed and is still current: identity for a year, income for 90 days, available funds for 30 days. If there is one, the step is satisfied on the spot and nobody is put through it again. Only the outcome is stored. Document numbers, dates of birth and bank balances never reach you.

Making a stage require it

Under Company Info, then CRM, any custom stage can carry Required Verifications: identity, income, available funds, credit check or background check. Choose what happens when something is missing: ask the person for a reason and record it on the lead, or refuse the move until everything is verified. Automatic moves never get past either.

Once any stage is gated, the Verifications section opens with a checklist: one row per kind, where this lead stands on it, and which stages still need it. Credit and background checks are run by the renter from their own QuickPass and are read here, not requested. On the board, a refused move snaps the card back and explains what is missing; on the softer gate it takes a reason and offers Move anyway.

Add default stages now includes Application Submitted, Application Approved and Application Denied. Application Approved ships asking for a verified identity with the softer gate, so you see the idea working the first time.

All of it lives under Company Info, then CRM, on the stage itself.

Rules

Each stage carries its own list of rules. A rule is one sentence: when this happens, do this. The When is either the moment a lead arrives in the stage (whoever moved it: a person, the AI, a flow or another rule) or once a lead has sat in the stage for a number of days you set, checked once a day.

The Do this options are:

• Assign an owner, alongside anyone already there.
• Add a tag.
• Notify the team, as a dashboard notification and an email to the teammates you pick.
• Add a note to the lead.
• Create a follow-up by email or SMS, a set number of days out.
• Start a follow-up cadence.
• Send an NPS survey.
• Move the lead to another stage.
• Archive the lead.

A rule can be switched off without deleting it, and every batch of rules writes one line to the lead's activity saying what ran and what was skipped.

What a rule will not do

Rules are built so they cannot loop. A rule that moves a lead does not run the destination's rules, so one arrival causes at most one further move. A rule never blocks the move that triggered it: if it points at a cadence you deleted, the move still happens and the rule is skipped with the reason recorded. A dwell rule fires once per visit, and the clock only starts for leads that move from now on, so nothing fires against leads that have been sitting still since before this shipped.

Exit requirements

Separately, a stage can insist a lead has something before it may leave: a note, an assigned owner, or a completed booking. Set it under Before A Lead Can Leave, then choose what happens when something is missing: ask the person for a reason and record it on the lead, or refuse the move until it is done.

One more change: a card dragged on the CRM board now fires everything a move made any other way fires, including cadence triggers, NPS triggers, flow events and the stage's own rules.

Where it lives

Open a flow, go to the Access Points tab, and open an email or SMS access point. The First-Touch Plan section lists the plans attached to that intake, lets you attach an existing one or detach it, and can create one from a template without opening the cadence builder:

• Text if no reply in 1 hour. If the lead gave a phone number, wait an hour after the first email reply and text them if they have not written back.
• Text right away. If the lead gave a phone number, text them straight after the first email reply so they know it is on its way.

A plan created here is an ordinary cadence. Open it in the cadence editor to change the wording, the timing or who it applies to. Detaching a plan from its last intake pauses it rather than leaving it to run for every new lead.

Building your own

Cadences have a new New Lead trigger, which fires when a lead is created from any intake: an email, a text, the web widget or a listing site. On its own it fires for every new lead in the company, so scope it with the guardrails: which flows or buildings, which intake channel, which specific intake address or number, and which Casa.

Two smaller additions make short plans possible. A wait step can now be measured in minutes, and a follow-up step can send an exact text you wrote, with variables filled in, instead of asking the AI to write one.

Texting a lead who only emailed

A cadence can now reach a lead on a channel they have not used yet. The text goes out from the Associated SMS Number set on the email access point, or from the flow's own SMS intake, so the reply lands back in the same conversation. The lead needs a phone number on file. Leads from listing sites such as RentFaster, Zumper, PadMapper and Rentals.ca have the number they typed into the listing form stamped onto their record at intake, so a later text from that number is recognised as the same person.

What the tab covers

The Addons tab offers the accessibility widget, the translation plugin, the QuickPass SDK and the QuickPass save buttons. Turning the save buttons on turns the SDK on with them, because the buttons do nothing without it. The translation plugin asks which of your translation profiles the site should use, so there is no key to copy across.

Widget addons work differently

Nudge, WebVision and web analytics sit in their own section further down, called Widget addons. They have no tag at all. Every site published from QuickCasa already carries the web widget script and those three ride along with it, so what decides whether they run is a setting on the widget rather than anything on the page. Never paste a tag for one of them onto a QuickCasa site: a second copy runs a second time, and two Nudge clients show every nudge twice.

Flipping one of these saves straight away rather than waiting for the page's Save button, because it is changing the widget rather than the website.

When there is nothing to flip

The tab tells you why:

• The site has no address yet. Give it a slug or a domain and publish it first.
• No widget covers this site. Nothing claims the site's addresses, so the web widget itself is not running here either. Add one of the listed addresses to a widget's sources under Web Widgets and all of it starts working.
• The widget or its flow is switched off. The switches still save, but nothing runs until the widget is back on.
• The widget is not active by default. It only appears on the pages its activation rules name, so these stay off everywhere else on the site.

Things to know

Custom head code still works if you prefer it, and sites hosted elsewhere still paste the tag anywhere in the page head, the same as an analytics tag. The tab keeps the tags in step with the site instead of leaving them to drift.

Where to find it

Open the Inbox. The picker sits above the tabs and starts on All inboxes. Choose an option to narrow down, and choose All inboxes to widen back out.

What it helps with

If you run separate addresses or numbers for different buildings, campaigns or brands, you can read one stream on its own rather than picking it out of everything at once. Each option shows how much traffic that inbox has had, so you can see which addresses are busy. An address whose only mail so far was held still appears in the list, so you can inspect it.

Things to know

Conversations that started before this picker existed may not yet know which inbox they arrived on. They still appear under All inboxes, and QuickCasa can fill the missing inbox in for past conversations on request.

Where to find it

Open the Inbox and choose the Spam tab at the top of the conversation list. The tab shows a count when something has been held. Selecting a held email opens it on the right, the same as reading a conversation.

Why an email was held

Each held email says which check stopped it and why:

• Spam. The classifier read the message as spam rather than a lead enquiry.
• Suspicious sender. The sending address looked throwaway or generated, so the message was checked more closely and did not pass.
• Marketing. It read as promotional mail from a third party, such as a newsletter.
• Empty message. Once the signature and the quoted reply thread were stripped out, there was no message left to answer.
• Nowhere to route it. The address it was sent to is not attached to a lead flow yet. Wiring that address up to a lead flow and then releasing the email will bring it through.

Releasing a real enquiry

If a held email should have come through, open it and choose Not spam. It is sent back through the normal intake pipeline as though it had arrived a moment ago: the lead is created, the AI replies if it is set up to, and the conversation appears in your Inbox. The checks that held it are skipped on the way through, so it will not be caught a second time. A released email is marked Released in the list and cannot be released again.

Reading held mail safely

Held email is shown in an isolated preview that cannot run scripts, load remote content, or navigate anywhere. Opening something in the spam folder to see what it was is safe, including mail that turns out to be a phishing attempt. Very large emails are stored up to a size limit, and when one is cut short the reader says so.

Things to know

Held emails are kept for 90 days and then removed. Releasing one creates a normal lead, which is kept under your usual lead retention rather than that 90 day window. The spam folder shows only your own company's email, under the same lead permissions as the rest of the Inbox, so an employee restricted to certain lead flows sees only held email for those flows.

Where to find it

NPS Tracking sits in the Clients Portal under Marketing. It has three screens: a campaigns list showing each campaign and its current score, a campaign editor, and a results screen.

Building a campaign

A campaign points at one flow form, which is the survey people fill in. Pick a form you already have, or start from one of the built in templates: Classic NPS, NPS plus Comment, or Detailed NPS.

The score calculator turns an answer into a number, and a campaign will not save without one. Tick the fields that should count towards the score and give each a percentage weight, totalling 100. Dropdown and choice fields map each option to a score from 0 to 10, and number and rating fields scale into the same range.

When surveys go out

Turn on the manual trigger and the campaign appears in the NPS Surveys section of any lead's profile, where an agent picks it and sends. Automatic triggers send on their own at four moments:

• Lead reaches a stage you choose on the CRM board.
• Lead qualified, when someone passes a qualification goal.
• Tour or appointment completed, so you ask about a viewing they attended.
• Lead archived, when their journey is closed out.

An automatic trigger can hold the survey back by up to ninety days, so a tour survey can go out three days later and a move in survey two weeks later. Everything is checked at the moment the survey goes out rather than when the trigger fired, so somebody who opts out during the wait is not surveyed.

Each campaign has a send limit for how often the same person can be surveyed, defaulting to one per month.

Acting on the answers

Promoters, passives and detractors can each get their own follow-up action: notify the assigned agent with a note, create a follow-up, or send a thank you message. For anything more specific, a data integration flow can react to the NPS: Response Recorded event, which carries the score, the category and every answer the person gave.

Reading the results

The results screen shows the score with its promoter, passive and detractor split, how many surveys were sent and answered, the response rate, a trend over time, and a breakdown by property, source, agent and stage.

Things to know

NPS Tracking is a module, so it needs to be enabled for your company before it appears. Surveys go out one person at a time, and there is no bulk send. People who have opted out of NPS messages are never surveyed.

Listing maps and published website prices follow it, and each is formatted the way that market writes it. A company operating in Vietnamese dong sees 10.000.000 with the dong sign on it rather than a figure that reads as ten million dollars.

What it does not change

The setting changes how a price is written, never its value. The stored number is untouched, so choosing a different currency does not convert anything and does not reprice a single unit. It is a display setting.

Canadian dollars stay the default when nothing is set, so a company that never opens the setting sees exactly what it saw before.

Overriding it on one map

A single listing map can price in something other than the company setting, beside the price filters in the editor's Listings section. That is there for when one embed serves a different market than the rest of the business.

How it works

Build a switchboard with an email intake type and start it from the Form Submission trigger. Pick the form it watches, either a flow form or a custom form. Every submission of that form starts the flow, and the answers arrive as variables you can branch on.

A Switch node reads whichever answer decides the destination, usually the property or community the person picked. Each branch then ends in a Route to Lead Flow node, which names the lead flow that should own the submission and the email intake source on it. A Script node in between is the usual place to tidy an answer up first, so that Sofia Yorkville, sofia and Sofia London all land on the same branch.

What the receiving flow sees

The submission is handed over as the same submission notification the form would have sent anyway, so the lead flow treats it exactly as it treats a form wired straight to it. The person becomes a real lead on the right flow, Casa answers them, that flow's cadences pick them up, and their reply threads back to the same place. Nothing downstream needs to know a switchboard was involved.

Worth knowing

• Route to Lead Flow can also send to an address you type in, for when the destination has to be built out of the submission itself.
• A submission that cannot be routed, because the destination lead flow was archived or its email intake method was switched off, is recorded in the execution history rather than dropped without a trace.
• A switchboard that starts only from a form submission is not given an intake address of its own, because it never reads one.

Switchboard sits under Developer in the menu. As with any flow, it only runs once you toggle it Active.

You will find it under Marketing, then Maps. Create a map, pick Listing, and it gets a public URL and an iframe snippet like any other map, so it can sit on any website, including one QuickCasa did not build.

Where the listings come from

By default the map pulls your own QuickCasa inventory. Filters narrow it to specific communities or buildings, an availability setting, a bedroom range and a price range. If you keep your listings in another system, the map can take them from the host page instead.

Before you publish, Check matching listings tells you how many listings the current filters match, how many were skipped for missing coordinates, and how many pins would have nothing to click.

What a visitor gets

• The price shown on the pin, or plain dots instead.
• Nearby pins grouped into numbered clusters, with a click to zoom in on them.
• A search box that filters both the list and the pins.
• A list that follows the map as they pan, waits for a Search this area button, or always shows everything.

Making it look like yours

Every part of the layout carries a stable CSS class, and the colours are published as CSS variables. The editor has a custom CSS field with a reference table of every class and variable, plus an example you can copy.

Two things worth knowing

A listing with no coordinates cannot be pinned, so it is left off the map. The editor tells you how many that is before you embed anything.

The Performance section shows the last 30 days: how often the map loaded, how many listings were opened, the share of loads that opened one, and which listings were opened most.

Two ways to do it

• Paste clipboard image asks the browser for whatever is on your clipboard. The first time, the browser asks whether to allow it.
• Ctrl+V works too once you have clicked the drop area, and needs no permission at all, because pressing the keys is the permission.

Both are offered because they fail differently. The button works when you have not clicked anything yet; the keys work when the browser will not hand a page the clipboard on request.

What to expect

A pasted image is named for the time it was pasted, so two screenshots added to the same record can be told apart. Everything a dropped file has to pass, a pasted one passes too: the file type, the size limit and how many files are allowed. A type that is not on the list is refused by name, so pasting something unusual tells you what it was rather than only that it was wrong.

The button is left out entirely where the browser will not let a page read the clipboard, rather than sitting there failing.

It helps most where the image never existed as a file on your machine: a screenshot of a listing, a crop of a larger photo, a picture taken off a message. Saving it to the desktop, finding it again in a file picker and deleting it afterwards was three steps to get one image in.

Symbols across a space

A room can be tiled with a symbol saying what the space is: trees across green space, cars across parking, water across a pool. The Fill pattern setting on any selected room offers Trees, Cars, Water, Paving, Play equipment, Dots and Hatching, plus None.

It starts on Automatic, which means whatever that kind of space normally uses, so green space, parking, a pool, a playground and a walkway come with a symbol and everything else starts plain. Automatic is not the same as None: a room left on it picks up the right symbol if its type is changed later, and plans drawn before patterns existed pick theirs up without being touched.

The last option is Custom icon, which opens the same icon picker the website builder uses and tiles the room with whatever you choose. Pick a dog for a dog run, a bicycle for bike storage, a wheelchair for accessible parking. Renters see the same icon on the published page. A point of interest can take an icon the same way, so the marker says what to look at rather than only that there is something to look at.

Turning the numbers off

By default every room prints two lines under its name, its size and its area. Sizes and Areas in the toolbar switch them for the whole plan, and they are saved with the drawing because they change what a renter sees rather than being a preference about looking at it.

A single room can disagree. The Size line and Area line dropdowns give each block three choices: follow the plan, always show, or always hide. That covers the case where a site plan wants no dimensions anywhere except on the property boundary.

Where the label sits

Every room label can be moved to any edge or corner, turned a quarter turn either way, resized and recoloured. Turning a label is what makes a narrow room readable, since the text can run along the room instead of across it. The name, the dimensions and the area move, turn and scale as one block, so the three lines never come apart from each other.

On an L shaped or U shaped room the positions are worked out against the largest open rectangle that fits inside the room rather than the box drawn around it, because the middle of the box around a U is in the gap between its arms, which is usually another room.

Portals

A Portal is a way through to another level of the same plan. Drop one at the top of a stair, at the lift doors, or at the hatch to a roof deck, and pick the level it leads to under Leads to. On the published page a renter taps it and arrives on that level.

It is the only thing on a plan that is a control rather than a description, so it is drawn to look like one: a pill carrying the name of where it goes, with a stair symbol and an arrowhead. The pill gets smaller as the plan is zoomed out, down to about half size, and past a point it drops the name and keeps the symbol. It stays easy to tap at any size without covering half a building.

Three things worth knowing:

• Portals are one way. A stair usually wants two, one upstairs pointing down and one downstairs pointing up. Placing one does not create the other.
• The name is what the pill says. A new portal takes the name of the level you point it at, so it reads "Second Floor" with no typing. Rename it and your name is kept, including if you later change where it leads.
• A portal with no destination is never published, nor is one whose level has since been deleted. A control a renter presses with nothing happening reads as a broken page, so it is left off the plan entirely rather than shown doing nothing.

Copy to level

With anything selected, Copy to level puts a copy of it on any other level of the drawing, and takes you there with the copy selected so you can carry on working on it.

The copy lands at exactly the same place, which is the point of it. Trace the building footprint on the grounds level, copy it up to the floor, and you have the real outline of the building to draw rooms inside instead of guessing at it. The same goes for a stairwell or a lift shaft that runs through every storey, or a guide line you want the floor above to line up with.

The copy is its own thing from the moment it is made, so editing it does not change the original and editing the original does not change it.