Give a whole company access by email domain Pro

A client area normally lists the people who can reach it. If the people are "everyone at one company", naming them individually means editing the category every time someone joins or leaves.

Instead, add an entry that starts with @:

@acme.example

Anyone signed in with an email address at that domain can reach the category and its documents. You can mix the two freely:

@acme.example, jrivera, contractor@other.example

That reads: everyone at acme.example, plus the user jrivera, plus that one contractor.

Named people and domains are an OR

Adding a domain rule never revokes anyone. <!– claim-ok: verified by the integration suite — "a named user still gets in once a domain rule is added" –>If a category lists both named users and a domain, a person gets in by matching either. That is deliberate — the common case is "the whole client company, plus two people on our side".

Why it is a rule, not a shortcut

FileDeck stores the domain as a rule and checks it on every request. It does not expand the domain into a list of user accounts when you save.

That is the entire point: someone who creates an account at that domain next month gets in without anyone touching the category. Expanding it on save would have frozen the list at the moment you typed it.

What it depends on

Access is decided by the email address on the user’s account, so it is only as trustworthy as your signup process. If people can register with any address and change it freely without verification, a domain rule is not a strong control — someone can simply set their address to anything@acme.example.

Use it where accounts are created or verified by you. Where they are not, name people individually, or use role restrictions.

Site administrators are never blocked, as with every other restriction. <!– claim-ok: verified by the integration suite — "a site manager still sees a domain-gated document" –>

Notifications

People admitted by a domain rule are emailed when a document is published into the area, the same as named users. Very large domains are skipped rather than partially mailed — a partial send reads as "everyone was told" and is worse than no send. Developers can adjust the threshold with the filedeck_domain_notify_cap filter.