# One rule, set by the person who published it

A bucket policy is a ticket. A project-wide lock is an admin setting. A dashboard needs a door of its own.

Source: https://publidock.com/blog/one-rule-per-site

Published: 2026-09-11
Topic: Sharing

Access control on a bucket is a ticket. Access control on a production project is an admin setting. Neither matches a dashboard that finance should see and sales should not.

## Four doors

Every Publidock site carries one rule, set by the person who published it and changeable at any time:

- Anyone with the link — open on the internet, never indexed.
- Anyone at the company domain — signed in with the identity provider they already use.
- Named people — a list of addresses, inside the company or outside it.
- A password that expires — for clients and contractors. The link stops working on its own.

IT does not edit a policy. Nobody guesses. Viewers of a shared site never become members.

## The price of that door

Company-domain and named-people sharing sit on Team, because access control is the thing companies buy. Free stays public-links-only. [The ladder](/#sharing) is the product, not an add-on around a deploy.

If the rule is wrong, change it. The file stays at the same address.

## Related

- [Sharing & access](https://publidock.com/product/sharing/index.md)