What you will take away from this lesson
ACME’s site now has three environments serving two releases, and every address of all three asks for a sign-in. This lesson decides who opens each one: the web team in dev, a supplier and the store operations team on stage, and, once ACME’s domain is on it in lesson 1004, the public on prod.
On Plexara, who opens an environment is decided per environment, and whether an address answers anyone is decided per address. Those two decisions are why the same site is a workshop, a client review room, an intranet and a public website at once, with no copies to keep in step.
Learning Objectives
- 01Say what a private address is, and what makes an address public.
- 02Share an environment with a person, with a persona, and with everyone internal.
- 03Explain why a persona share follows the persona without anyone updating it.
- 04Describe what happens when someone opens a private environment for the first time.
- 05Say who can make a domain public, what the portal asks first, and what stays private.
- 06Read who may do what on a site, by role.
Where this lesson sits
Lesson 1002 gave acme-stores a stage and a prod and moved releases into them. Nobody outside the web team can open any of them yet.
1000 Series: Sites
- 1001Your first siteWhat a site is, the working copy called dev, the first release, the address it answers at, and who may create one.
- 1002Dev, promote, roll backEnvironments people use, promotion of the exact release that was reviewed, approval, rollback, and the history of every move.
- 1003Private environments, public domainsAccess per environment: people, personas, everyone internal, the sign-in every pages address asks for, and the rules for making a domain public.
- 1004Your own domainThe main address, an address for every environment, adding a domain in the portal, making it public, and the names a site cannot take.
- 1005Layouts and recordsLayouts, includes and records: the agent maintains data and the platform generates pages, paged lists and category indexes.
- 1006Editing a live siteReading and patching site files in place, dry runs and diffs, overlays for new files, and one promotion for several edits.
- 1007Capstone: moving an existing site onto PlexaraA crawl that keeps every address, redirects as rules, forms replaced by Plexara forms, and the whole series end to end.
The 1000 series builds on the forms and endpoints of the 700 series and the sharing model of the 800 series: a site is where the pages people open live, with the same people, personas and approvals deciding who reaches them.
Access belongs to the environment
Most web hosting gives a site one audience: it is on the internet or it is not. Anything else, a preview for a client, a version for staff, is a second site somewhere else with its own way of keeping people out.
On Plexara each environment decides who may open it, independently of the others. This is where ACME’s site is going by the end of the lesson.
acme-stores: one site, three audiences
| Environment | Access | Who opens it | What it is for |
|---|---|---|---|
| dev | Private, always | The owner, the people who manage the site, administrators, and the web-team persona | The working copy. The agent’s changes land here and are reviewed here. |
| stage | Private | Everyone internal, plus the supplier-blue-harbor persona | Review by the people the site is about: store operations and one supplier, before anything is public. |
| prod | Public at ACME’s own domain, requires approval | Anyone at stores.example.com; at its pages addresses, the people who manage the site | The store finder and supplier page the world uses, once lesson 1004 puts the domain on it. |
The three environments serve releases of the same site. Nothing was duplicated to give the supplier a preview or the public a website, and nothing has to be kept in step between them.
Private addresses and public domains
Every address on your deployment’s pages address is private: the platform checks who is asking before it serves a single byte. A domain you add is private too, until the owner or an administrator sets it public, and then it serves anyone at that one name.
A private address and a public domain, side by side
| Private address | Public domain | |
|---|---|---|
| Who opens it | Administrators, the owner, the people who manage the site, and whoever it is shared with | Anyone |
| Sign-in | Your organization’s, checked on every request and every path | None. A site that wants one of its own builds it. |
| What a refusal shows | Nothing of the site: no page, no file, no file name | Does not apply |
| Browser caching | The browser checks back on every request, so removing someone takes effect on their next click | As published |
| Search engines | Every answer asks not to be indexed | Indexed as any public site is |
| Who is signed in | The site’s own script can ask who the visitor is | Nobody is signed in, and the site is told so |
| Which addresses | The main address, every <site>--<environment> address, and every domain until it is set public | A domain the owner or an administrator set public, and only that one name |
dev is always private and can never have a domain, so it can never be public. Every other environment asks for a sign-in at its pages addresses whatever its domains are set to. A domain set public opens that one name and nothing else.
What a visitor to a private environment experiences
A contact at Blue Harbor Wholesale opens the stage address from an email. They have never used the portal and do not need to know it exists.
Opening a private environment
- 1
The address is checked before anything is served
Every request to a private environment, on its own address or on a domain, is checked first. A visitor with no sign-in is sent to your organization’s sign-in.
- 2
The visitor comes back to the page they asked for
After signing in they land on the same address and path. Someone already signed in to the portal passes through without a click.
- 3
The site’s address keeps its own sign-in
The handover uses a code that works once, for one minute, for that site, that address and that browser. The address then keeps a sign-in of its own for an hour. It never receives the portal’s session, so a page’s script cannot act as you in the portal.
- 4
Access is read again on every request
Whether this person may open this environment is decided each time, from the current shares and the current persona. Removing a share closes the site on that person’s next request.
API keys are not accepted on a site’s address. A private environment is for people in a browser, and a system that needs data calls an endpoint (700 series).
What it takes to answer anyone
Store operations and the supplier read stage and were satisfied. prod already serves release 2. What remains is the one change on a site that cannot be taken back quietly: opening it to the world. Lesson 1004 takes that step.
Five rules govern it, and each one exists because a public address is a commitment to people the organization cannot see.
The rules for making a domain public
- 01
Public is a setting of a domain, never of an environment
Every address on your deployment’s pages address asks for a sign-in, whatever happens to the environment’s domains. Opening a site to anyone takes two deliberate steps: adding a domain, and setting that one domain public.
- 02
Only the owner or an administrator makes a domain public
An agent can do it only when it is working for one of them, and it is then their decision on the record. On an environment that requires approval, the owner’s request waits in Approvals and the domain stays private until it is approved.
- 03
The portal names the domain before it opens it
Make public asks for the domain’s name to be typed, names that one domain, and says the pages addresses keep asking for a sign-in. Nobody opens an address to the world without having read it.
- 04
An approval covers the access it was asked for
A domain made private and then public again asks again. Approval is for this change, not a standing permission.
- 05
Anyone who manages the site can make a domain private
Closing a door needs less standing than opening one. Private takes effect on the next request.
Inside a private environment
The platform’s decision ends at the door: this person may open this environment, or may not. A site that wants to show different people different things does that itself, and the platform gives it the one fact it needs.
A private site can ask who is signed in
// In a page served from a private environment
const who = await fetch('/_viewer').then((r) => r.json())
// { "email": "[email protected]",
// "user_id": "...",
// "persona": "supplier-blue-harbor",
// "name": "Dana Okafor" }
if (who.persona === 'supplier-blue-harbor') {
showSupplierPriceSheetLink()
}The platform decides who may open the environment. Anything finer is the site’s own business, and the site has what it needs to do it: a private environment answers /_viewer with the signed-in person. When the environment is part of an application, the application’s endpoints answer on the same address and run as that person, so a rule the page shows is a rule the server enforces. At a public domain /_viewer answers that nobody is signed in, and the endpoints run as nobody.
Who may do what
Lesson 1001 introduced the owner and the people who manage a site. With sharing and public domains in place, the full table is short enough to read at a glance.
Who may do what on a site
| Shared with | Can manage | Owner | Administrator | |
|---|---|---|---|---|
| Open a private environment | The ones shared | Every one | Every one | Every one |
| Publish and edit dev, promote, roll back, add domains and environments | No | Yes | Yes | Yes |
| Share an environment, make a domain private, set approval | No | Yes | Yes | Yes |
| Make a domain public, move the main address | No | No | Yes | Yes |
| Add or remove the people who manage, change the owner | No | No | Yes | Yes |
| Delete the site, take approval off an environment | No | No | No | Yes |
The rows climb in consequence, and so do the columns. Putting approval on an environment is something anyone who manages the site can do; taking it off is an administrator’s, because removing a control should never be easier than adding one.
One site, many rooms
What comes next
prod serves release 2 to the people who manage the site, at addresses that ask for a sign-in. Lesson 1004 puts ACME’s own domain on it and makes that domain public. The external persona used here is built in lesson 805.
Key terms
Five terms cover who can open a site and who decides.
Key Terms
- Private address
- Asks for your organization’s sign-in and opens for administrators, the owner, the people who manage the site, and whoever the environment is shared with. Every address on the pages address is private.
- Public domain
- A domain set public by the owner or an administrator. It opens its environment for anyone, with no sign-in, at that one name.
- Share
- View access to named private environments for a person or a persona. Naming no environments opens every private one.
- Everyone internal
- A setting on one private environment that opens it to everyone signed in whose persona is not external.
- Can manage
- Site-wide standing to publish and edit dev, promote, roll back, add domains and share. For internal people only.

