How to Share a Page With Everyone at Your Company

To share a page with everyone at your company, keep the page restricted and add the company's email domain to its access list, typed as acme.com. Anyone with an address at that domain can then open the page after confirming their email, and nobody else can, however far the link travels.

That is the short answer. The longer one is about what "everyone" means on the day you set it up, what the page records about who read it, and two ways this goes wrong that are worth knowing before you paste the link into the company chat.

The problem with sharing a page with everyone at your company

You built something the whole company should see: a dashboard, a policy page, the onboarding guide your AI wrote from the old wiki. Naming two hundred people one at a time is not an option. So the usual move is to make the page public and trust that nobody outside will find the link, or to put a password on it and send the password around.

Both lose the thing you wanted. A public link is open to the former employee who still has it and to anyone they forward it to. A password is one string that everyone shares, so you cannot take it away from one person, and you never learn who used it.

What you want is a rule instead of a list. Anyone who can prove they have an address at the company gets in. On SnapHost that rule is a domain entry on the page's access list.

How a domain entry works

A restricted page has a list of who can open it. The sharing docs describe the two kinds of entry: a person's email, like jane@acme.com, or a whole company at once by its domain, like acme.com. You add either from the page's Share dialog, or by asking your AI if it is connected.

When someone opens the link, they type their email and get a code. Once they have entered it, SnapHost takes the part of their address after the @ and compares it with each domain entry on the list. If it matches, the page loads. If it does not, and their exact address is not on the list either, they are turned away.

The comparison is exact. An entry for acme.com admits jane@acme.com. It does not admit jane@eu.acme.com or jane@acme.co.uk, because those are different domains. If your company uses more than one, add each as its own entry.

Three groups get in without any entry at all: the owner of the page, the active members of the workspace it lives in, and anyone you have named by their individual email. A domain entry adds to those, it does not replace them.

What it costs

Domain entries are a Pro feature. On the Free plan a page can be restricted to up to three named people, each by their own email, and SnapHost refuses a domain entry with a message saying so. Pro has no cap on the number of people a page can be private to, and that is also where domain entries live.

Pro is 19 euros a month for each member who can publish, and the people who open the pages cost nothing, however many there are. For a company-wide page that is the right shape: one or two people publish, everyone else reads. The current lines are on the pricing page.

One default is worth knowing. A new page on Pro is restricted from the start, so nobody outside your workspace can open it until you add an entry. A new page on Free is public unless you name people first. If you are on Free and want the page kept private, add the names before you copy the link.

Everyone at the company, or everyone in the workspace

There are two different "everyone" buttons, and they do different things.

A domain entry is about email addresses. It admits anyone who can confirm an address at the domain, whether or not they have ever heard of SnapHost. Readers do not need an account. They type an email, enter a code, and read.

The everyone in your workspace option in the Share dialog is about the people who are members of your SnapHost workspace. It gives the page to all of them in one line, including the viewers, which the workspace docs describe as the free role for people who open what is shared with them and change nothing. That is the right choice when the page is for your own team and your team already lives in the workspace.

For a company-wide page, the domain entry is usually the one you want. Most of the company is not in your SnapHost workspace and has no reason to be, and a company email address is all the domain entry asks of them.

What the page records

Every open of a restricted page is recorded with the time and the reader's email, since they confirmed it on the way in. Requests from people who were turned away are recorded too. So a domain entry does not mean you stop knowing who read the page. It means you stop having to list them in advance.

That record is where a domain entry earns its keep over a password. With a password, the page knows that someone who held the password opened it, and nothing more. With a domain entry, it knows that jane@acme.com opened it on Tuesday. The post on what an access log for a shared page tells you goes through each event and what to make of it.

One detail of how the identity is chosen. A reader may have confirmed more than one address with SnapHost over time. If one of them is on the list by name, that exact match is the one written to the log, ahead of any address that only matches by domain. So a person you named individually always shows up as that address.

Leaving, and other things that change

Someone leaves the company. Their company address stops working, so they cannot confirm it any more, and the next time they open the page they cannot get past the email step. You did not have to do anything. That is the main practical difference from a password, which keeps working in their head for as long as they remember it.

There is a window to be honest about. A reader who confirmed their email is remembered on that browser for fourteen days from their last visit, inside a ceiling of ninety days. Being remembered is not being permitted: the page checks the list on each open, and removing a domain entry refuses them on their next open. But a person whose mailbox was closed yesterday can still open the page on a browser that remembers them, until that window runs out. If that matters for a particular page, remove the entry, or take the page offline, rather than relying on the mailbox being gone.

The other direction is simpler. Someone joins the company, gets an address at the domain, and can open the page the same day, with no list for anyone to update.

Two traps

A public mail domain. A domain entry admits anyone with an address at that domain, and SnapHost does not refuse domains that belong to a mail provider. Add gmail.com because a contractor uses it and you have opened the page to everyone with a Gmail address. For a contractor, add their address by name instead. A domain entry is for a domain your company controls.

A password on top. On a restricted page, a view password is a second way in, not a second check. Anyone holding the password opens the page without being on the list, and an open made with the password alone is not written to the access log at all. If you added a domain entry to know who is reading, adding a password undoes that for anyone who has it. The argument is laid out in website allowlists vs passwords: pick one, and for a company page pick the domain.

People outside the domain

A company-wide page usually has a few readers who are not at the company: a board member with their own address, an agency, an auditor. Add each of them by email, on the same list as the domain. The two kinds of entry sit side by side and you remove either one on its own.

If someone you did not think of opens the link, they can ask for access from the page itself. The request shows up in Share, and approving it adds their address to the list. That is usually easier than guessing the full set of outsiders up front.

Setting it up

1. Publish the page in a Pro workspace. A new page there is restricted from the start.
2. Open Share and add the company domain, typed as the bare domain: acme.com, not an address at it. Add a second entry for each other domain the company uses.
3. Add any outside readers by their email.
4. Do not add a password.
5. Send the link wherever the company will see it. Anyone who opens it confirms their email once and reads.

If your AI is connected to SnapHost, the whole thing is one sentence: publish this and share it with everyone at acme.com. The same controls, including taking the page offline and bringing it back, are in the sharing docs linked above. For the wider question of where an internal page should live and who should own it, how to host internal web tools covers the part that comes before sharing.