Alpha Public & Private Projects
Control whether house links can be shared with anyone or only opened by invited buyers through the buyer portal
Public & Private Projects
Every house in a project has a house link: the buyer-facing viewer URL you copy from the sidebar, put in a mail, or turn into a QR code. A project's visibility decides who may open those links.
This is different from the project team, which controls who inside your organisation sees the project in the Projects overview. Visibility is about people outside your organisation.
The two modes
| Public (default) | Private | |
|---|---|---|
| Who can open a house link | Anyone who has the link | Staff, and the invited buyer of that house |
| Woningzoeker / project pages | Reachable by anyone | Staff only |
| Buyer route in | The link itself | The buyer portal |
| What others see | The house | A 404 |
Public is how projects have always worked and stays the default, so nothing changes for existing projects. Use it while a project is on sale and links are meant to spread.
Private closes the links off. Use it for projects that are sold out, under NDA, or still in preparation, anywhere a leaked link should not expose the plan.
Making a project private
- Open the project and go to the Project tab.
- In the Visibility card, choose Make private.
Only project owners (and tenant administrators) can change this.
Going private takes effect immediately, including for links you already shared. Anyone who is not staff or the invited buyer of that house gets a 404 on their next request, even mid-session. Invite the buyers before you flip the switch if they are already using their links.
A private project deliberately returns "not found" rather than "forbidden": the link must not confirm that the project or the house exists.
Inviting a buyer
On a private project a buyer reaches their home through the buyer portal, not through the raw link. Both steps (recording who buys the house, and mailing them their way in) live in one place.
For the whole journey end to end, including the configurator route and what to check once the buyer is signed in, see Getting buyers into the portal.
- Go to the Sales tab and pick Houses.
- Select the house. The panel on the right shows a Buyer card.
- Fill in the buyer's email (name and phone are optional) and choose:
- Save & invite: records the buyer and mails them a one-click link to their house.
- Save only: records the buyer without sending anything, for when you want to mail later.
- For a buyer already on the house, the same card offers Send portal invite to (re)send, and Edit or Remove to correct who is on the home.
Each invite mails a fresh sign-in link, so re-sending is how you help a buyer who lost the mail.
If the email already belongs to an Alpha user, no second account is made: the house simply appears in the portal they already sign into, and the notification says so.
A CRM client with the same email address is linked automatically, so the house, the client record and their dossier stay one story.
Once signed in, the buyer also finds their home on the portal dashboard, under Mijn woning, so they never need to keep the mail.
Buyers recorded by assigning a request
Assigning a submitted configuration to a house (Assign on a request) also records that request's client as the buyer of the house, unless a buyer was already entered by hand. So a house sold through the configurator needs no separate buyer entry, just the invite, if the project is private.
Seeing who has a buyer
The Houses table has a Buyer column, a filter for Assigned / No buyer, and a
x/y with buyer counter. That counter also sits in the bar at the top of the Sales tab, next to
the project's Public/Private badge, so you can see at a glance how much of the project has a person
attached.
When an invite cannot be sent
The invite reports rather than fails silently when:
- there is no email address on the buyer yet,
- the tenant has the buyer portal switched off (
configuratorSettings.buyerPortalEnabled), or - the email belongs to an account Alpha must not auto-provision: a staff account, or a signup that was never verified. Use the buyer's own address instead.
In each case the buyer is still recorded on the house; only the mail is skipped.
What a buyer can and cannot reach
An invited buyer can open their own house and its neighbours (needed to render the street). They cannot open another buyer's house, the woningzoeker, or the project-wide 3D pages; those stay staff-only on a private project.
Revit and render workers
The Revit add-in and the render workers call the same endpoints with an API key, so exports and render jobs keep working on a private project. Nothing needs reconfiguring.
Going back to public
Choose Make public in the same card. Every house link starts working for everyone again immediately. Invites already sent stay valid; they simply are no longer required.