A workspace is your organization's own space on Hub Nexus. Its pages work like every other page — changes, review, every version kept — but only its members can read them. They stay off the public site: not in search, in any feed, on any topic page, or in the sitemap.
The screens below come from a demo workspace, Northwind Research, a coastal survey team. Maya is its owner; Sam is a member.
At a glance
- Private by construction. A workspace page is stored apart from public pages, and every request for it — its text, its history, its comments — is checked against membership on the server. To anyone outside, it does not exist.
- Four kinds of access. Owner, administrator, member and guest, from running the workspace to reading only.
- Every change reviewed. Changes are proposed, reviewed and approved — by each page's maintainers, or by a group you name. Every version is kept, with who changed what and why.
- Signed approvals for controlled documents: the approver says what the approval means and enters a code emailed at that moment (21 CFR Part 11).
- One page shared, safely: a read link that ends on its own, or one page shared with one person by name.
- Between private and public: publish a public version of a page, or copy a public page into your workspace and send your improvements back.
- Single sign-on, provisioning, an audit log: OpenID Connect or SAML 2.0, SCIM 2.0, and a log of every consequential act, kept for as long as the workspace exists.
- Deleting is real: deleting a workspace erases its pages, files and people.
Create a workspace
Press Create and choose Workspace.

Give it a name and, if you like, a line saying what it is for, and press Create workspace. You are its owner.

Inside a workspace
The workspace's page lists every page in it, newest first — drafts too, so colleagues find work in progress instead of starting it again. The box above the list filters it as you type, and the topic menu narrows it to one of the 24 topics. New page starts a page only members can read. Its members and groups are on the right; Workspace settings holds the rest.

Search says where it is looking
The search box at the top of every page names its place. Inside a workspace it starts in This workspace; one press switches it to All my workspaces or Public Hub Nexus. Results from different places are never mixed in one list, so a private title never sits beside public ones.

A home page
In Workspace settings › General, choose a Home page: a published page of the workspace that everyone here starts from — a welcome, and links to the pages that matter.
People and roles
Access is set per person, per workspace, and the server enforces it: the buttons on screen are a convenience, not the protection.
| What they can do | Guest | Member | Administrator | Owner |
|---|---|---|---|---|
| Read every page in the workspace | Yes | Yes | Yes | Yes |
| Comment, like and follow | Yes | Yes | Yes | Yes |
| Write pages and propose changes | No | Yes | Yes | Yes |
| Approve as one of a page's maintainers | No | Yes | Yes | Yes |
| Approve when in the group named to approve | Yes | Yes | Yes | Yes |
| Invite and remove people, change roles and settings | No | No | Yes | Yes |
| Hand the workspace over, or delete it | No | No | No | Yes |
Invite someone
In Workspace settings › Members and roles, type an address under Invite by email, choose a role and press Invite. They don't need an account first: they get an email and join when they accept, from Workspaces. An invitation stays open for 14 days.

- Member — reads and writes pages, and proposes changes.
- Guest — reads and comments; cannot write pages or propose changes. For an auditor, a consultant, or a new hire before their start date.
- Administrator — everything a member does, and runs the workspace: members, roles and settings.
Hand it over, leave, remove
The owner can Hand over the workspace to a member or an administrator — never a guest — and stays an administrator. Anyone but the owner can leave; administrators can Remove anyone but the owner. Access ends at once, old links and bookmarks included, and a change waiting on that person's vote passes to the reviewers who remain.
Writing and reviewing
A workspace page works like any page on Hub Nexus: write it in the editor — text, pictures, films, recordings, files — propose changes with New change, review them, publish them. Every version is kept.

Who approves
By default, each page's maintainers approve its changes. In Groups and approvers a workspace can name one group — Legal, Quality, Editors — to approve changes to every page instead. Its members need not write, and nobody approves their own change.

Signed approvals
Tick Approvals must be signed for controlled documents. Approving then needs an electronic signature: the approver says what the approval means — review, approval or responsibility — and enters a code emailed to them at that moment. The signature is kept with the change and never altered (21 CFR Part 11). Where the workspace has single sign-on, the approver can sign there instead.

Where a page lives
This page is in names a page's place — the public site or one of your workspaces — and says what each choice means before you make it. Moving a page into a workspace ends any links to its old public address.
Sharing one page outside
Send one page to a client, a candidate or a contractor without adding them to the workspace. A published workspace page shows every way out, each saying what it does.

A read link
Choose how long it lasts — 1, 7 or 30 days — and press Make a read link. A second step says plainly that the page is leaving the workspace, to anyone the link is forwarded to, and until when. Press Create the link.

While a link is live, every member sees it at the top of the page. Turn off ends it on the very next request.

| Someone with the link | |
|---|---|
| Reads the page's current published version | Yes |
| Sees its history, changes, comments or maintainers | No |
| Opens any other page of the workspace | No |
| Finds it through a search engine | No — a shared page is never indexed |
| Keeps reading after it ends or is turned off | No |
Drafts cannot be shared: a link always shows a published version.
One person, by name
When someone outside needs to take part, not only read, share the page with them by email — Can read, Can comment or Can propose changes — for 7, 30 or 90 days.

A second step says what they will be able to do, on this page only, and until when.

They sign in with that address and see this one page. Whatever their access, a person outside never approves changes, never shares in what the page earns, and cannot pass the page on. Their proposed changes go to the page's maintainers like anyone's. Every member sees who outside has the page, and Remove ends their access at once.
Between private and public
Publish a public version
Publish a public version puts the page's current text on the public site, as a page of its own. Later, Update the public version brings it up to date, and See the public version opens it as the world sees it. Drafts, earlier versions, votes, comments and who wrote what stay in the workspace; the public page says only that it is A published snapshot.
Adopt a public page
On any public page, Take a copy into your workspace and press Adopt. Your workspace gets its own copy to keep current; the page you copied is untouched and never learns about it. When your team has improved it, Send improvements back opens an ordinary change on the original, reviewed by its maintainers like any other.

Privacy, enforced
Someone outside the workspace is never told that a private page exists. Its address answers Page not found, as a page never written does, and the workspace's own address says it does not exist or they are not a member of it.

| Where a workspace page never appears | Why |
|---|---|
| Search on the public site | It is never written into the public index, so nothing has to be filtered out |
| The home page, topics, feeds, Read next | They show only public pages |
| The sitemap and link previews | Search engines and social networks are never given its address or title |
| Other workspaces | Titles are unique within a workspace, so two companies can each have an "Onboarding" page |
Running it
Everything that runs the workspace is on one page for administrators, Workspace settings: General, Members and roles, Groups and approvers, Verified domains, Single sign-on, SCIM provisioning, Signed approvals, Recognition budget, Audit log, and Delete.
Verified domains and single sign-on
Prove your organization owns its email domain with one DNS record. Then connect your identity provider — Okta, Microsoft Entra ID, Google Workspace, ADFS or any other that speaks OpenID Connect or SAML 2.0. Someone at your domain who is not yet a member joins when they first sign in. Once a sign-in has worked, single sign-on can be required for your domain.


SCIM provisioning
Your identity provider adds and removes people as they join and leave your organization. Addresses at a verified domain become members directly; anyone else is invited. Roles are set here, never by the provider.

Recognition budget
Fund it and set a monthly amount: it pays the members who write and improve the workspace's pages, by the same shares that split a page's earnings — two for each published page they wrote, one for each they contributed to. Money added is credited after Stripe's fee and Hub Nexus's 10% (Fees and payouts).

Audit log
Who did what, and when, newest first: membership, roles, settings, every review step, read links, shares and payments. Nothing is taken out of it while the workspace exists, and the whole log downloads as CSV.

Delete the workspace
Only the owner can delete a workspace, by typing its name and entering a code emailed at that moment. It erases every page with every version, comment and share, the files, the members, groups and settings. The audit log is kept for 12 months, then erased too. A page published outward stays public: it is a page of its own.

Workspace or public
| Workspace page | Public page | |
|---|---|---|
| Who can read it | Members of the workspace | Anyone |
| Who can change it | Members, through review | Anyone signed in, through review |
| Every version kept | Yes | Yes |
| Articles, films, recordings, files | Yes | Yes |
| Found by public search and feeds | No — search it with This workspace | Yes |
| Shared with one person outside | A read link, or by name — both end on their own | Already public |
| Publish a public version | Yes | Already public |
| Copy into a workspace | — | Yes, with a way back |
| Readers support it with money | No | Yes |
Questions
Do the people we invite need an account first? No. Invite them by email. They sign in with that address — a six-digit code, no password — and the invitation is waiting.
Can anyone outside see our pages? No. A workspace page is absent from public search, feeds, topics and the sitemap, and its address answers "Page not found" to anyone who is not a member.
What happens when someone leaves the company? Remove them, or let your identity provider do it. Their access ends at once, including links and bookmarks they kept.
Can a guest change anything? No. A guest reads and comments, and is never offered a way to write or propose a change. An administrator can make them a member at any time.
What if a read link is forwarded? Anyone who has it can read that one page until it ends — which is why making one asks twice. Every member sees that a link is live, and any member can turn it off.
Are there folders? No. A home page, search inside the workspace and the 24 topics find your pages without a tree that goes stale.
Does publishing a public version expose our history? No. The public page gets the current text only.
Where is our data kept? In Amazon Web Services' US West (Oregon) region. More on Security.
Can we get everything out? Yes. On request, an export of every page, version, change, comment and signature, with the files, the members and the audit log.
Talk to us
For a pilot with your team, enterprise terms, or a partnership, write to support@hubnx.com. We reply personally.
Get each new page of
Hub Nexus
Following means one email when a page is added, nothing when a page changes.
Comments






