For Companies
Every SiteYour People Published
Someone in the team asked Plexon to put a page on the internet under your company name. Here is the list of every one of those, the address each answers on, whether it is actually working, and the switch that decides who is allowed to publish in the first place.
Related features
One List of Everything Published
Every site your people published from Plexon is in one inventory, with who owns it, the address it answers on, and what state it is in. A site the owner took offline says so and keeps its address. A site that failed carries the reason it failed, rather than sitting there looking fine.
- Owner, address, and state on every row
- The certificate state and whether the domain actually verified
- The last error, kept on the row instead of thrown away
- Offline is a state, not a deletion: the address is held and the next publish clears it
Your Domain, Set Up Once
Sites publish under your company domain. The setup itself stays with Plexon, on purpose: those settings decide where your company publishes and who pays for the zone. What you get is the read of them, the records they depend on, and a Re-check button for the moment after someone installs the app on your side and wants to know whether it took.
- The configuration is readable, with the records it depends on listed
- Re-check asks the provider now and records the answer
- Hosting and your counts load separately, so a company that never set hosting up still sees its people
- Ask Plexon to change the configuration itself
Publishing Is a Right You Grant
Nobody publishes to your domain because they felt like it. A company admin grants the right, and taking it back is the same switch in the other direction. That is the control most teams actually want before they let an assistant put anything on the internet under their name.
- The grant sits on a group, so one change covers everyone in it
- Takedown is a separate switch from the grant
- It can also be set on one person, whichever fits how your company is organised
- Changes take effect on the next call, not the next sign-in
Taking One Down
Remove a site and the publishing stops. A company can remove one, or several at once, and can delete the repository behind it in the same step or leave the repository where it is. Withdrawing somebody's right to publish is the other half of this, and it is a switch of its own.
- Remove one site, or select several and remove them together
- Deleting the repository along with the site is a choice on the same action, not automatic
- A removed row stays in the company inventory rather than vanishing from the record
- The person's own view excludes what was detached, so nothing looks half-deleted to them
What the Inventory Gives You
Nothing Published in the Dark
Every site your people put up is on one list, with its owner, its address and whether it is actually working.
On Your Domain
Sites answer under your company domain, with the certificate state and the domain verification shown on the row.
Publishing Is Granted
A company admin hands out the right to publish, on a group or on one person. No grant, no publishing.
Takedown When You Need It
Remove one site or several, and choose whether the repository behind it goes too. Withdrawing the right to publish is a separate switch.
Connects to
Nothing here works alone. See the whole map for how the pieces fit together.
What feeds it
Company Admin Panel requires this.
A group can publish a site only once a company admin grants it that right.
Publish Sites renders into this.
A site published from the app appears in the company inventory with its address and its state.