Roles and permissions
Access in Uniweb is controlled by roles. Websites and folders have separate permissions, which is what lets someone contribute content without having the keys to a whole site. This page explains both.
Who can do what on a website
When you share a website, you choose one of three roles for each person. A fourth state — Full control — is a checkbox you can add on top of the Editor role.
| Role | What they can do |
|---|---|
| Reader | See the site. No changes of any kind. |
| Contributor | Add, organise and remove Records — the content the site reads from — without being able to edit the site's pages. |
| Editor | Everything a Contributor can, plus editing the site's pages. |
| Editor with Full control | Everything an editor can do, and more — see below. |
⭐ Contributor is the useful one, and the one people miss. It is exactly the pairing a contributor needs: they keep the content flowing without being able to change how the site is built.
The owner is not in this list because the owner is not something you assign. The owner has complete access, and the app shows their row as fixed: "Full control — can't be changed here."
Full control
Full control is a checkbox on a person's row, and it appears only when their role is Editor. Before switching it on, the app asks, and its warning is worth reading rather than summarising:
…will be able to do anything you can with this site — including publishing it, spending on its subscription, sharing it with other people, deleting it, and exporting or deleting the form submissions visitors have sent. It costs nothing extra, and you can withdraw it at any time.
⚠️ Treat that list as examples, not as the boundary. Full control means what its name says; the things listed are the consequences you cannot predict or undo, not the complete set of what it permits. You can withdraw it at any time by clearing the checkbox — that takes effect at once, with no question asked.
⛔ Only Full control (or the owner) can manage people. Inviting someone — even as a Reader — changing a role, removing a collaborator and seeing who has access all need it; an Editor without it cannot do any of them. For a site in an organization, the organization's administrators can too.
💰 It costs nothing extra. Editors and full-control editors are charged the same; only editors need a paid seat at all. Readers and Contributors are free.
The app never uses the word Admin for a website — that word belongs to organizations, and to sharing content that is not a website (see below).
Content access and page access are separate
A site's Records and its pages are governed separately, which is what makes lightweight collaboration possible:
- a Contributor can add, organise and remove the site's Records while its pages stay untouched;
- an Editor can do both.
That separation is the whole point of the Contributor role: content keeps flowing without handing over how the site is built. See Folders.
Library items on a site
An item's own menu, once you open it, has no access controls (the Hub's list of a content type does have Share in each row's ⋮ menu). An item in a site's folder is on that site unless its Draft mode is on — see Creating library assets.
⚠️ A site's Records are shared through the site's roles, not separately (and Contributor is offered only on a site that has a Records folder): a Contributor or an Editor can change them, and a Reader can see the site. A site's own Records folder has no sharing button of its own — use the site's Settings → Collaboration tab.
A folder that isn't part of a site — you can't create one in the app today — is shared on its own, from its Access button (or Share in its ⋮ menu), with different words for the same three levels: Viewer (can view), Editor (can edit) and Admin (can manage). Sharing a folder is free at every level.
Where to go next
- Collaborators and seats — how inviting people works.
- Working together — editing the same site at once.
- Folders