Roles and permissions
How Basker decides what each user can see and change — the built-in roles and how content is shared
Each staff member on your site has one or more roles that decide what they can do — which content they can view, create, edit, publish, or delete, and whether they can change site settings or manage other people.
There's also the Site Owner, a separate per-site designation for the person with overall responsibility for the site. The owner isn't one of the roles you assign to staff.
How roles work
A role is a named set of permissions. Permissions are grouped by what they apply to:
- Content — each content type (pages, posts, events, people, venues, media, and the rest) has its own permissions for View, Create and edit, Publish, and Delete. You can grant any combination, so a role can let someone edit pages but not publish them, or manage posts without touching events.
- Settings — separate permissions for general settings, security, domains, languages, apps, themes, transferring ownership, and managing roles and staff.
Because permissions are granular, a role can be as broad or as narrow as you need.
Built-in roles
Full access
Grants every permission on the site — view, create, edit, publish, and delete across all content, plus all settings and staff management. Use this for senior editors, operations leads, and anyone who needs unrestricted access.
View only
A read-only baseline: the person can sign in and see content but can't create, edit, publish, or change settings. Use this for stakeholders who need visibility without editing rights.
Custom roles
Beyond the built-in roles, you can create your own. A custom role has a name, an optional description and icon, and any combination of the permissions above. Build one for any pattern your team needs — for example, a content lead who can edit and publish everything but can't change settings or manage staff, or an editorial contributor scoped to posts only.
Every site starts with a set of ready-made roles to choose from; the exact roles available depend on the templates provisioned for your account. Create, rename, and adjust roles from the Roles section of Users & Permissions, then assign them when you invite or edit staff.
A staff member can hold more than one role; their effective access is the combination of everything their roles grant.
Sharing content across your sites
If your organisation runs multiple Basker sites — or works with partner organisations that do — content can be shared between them. A shared record can be edited from either site, controlled by the role the person holds on the site they're working from.
Sharing is set per record. Open a record's sharing options and pick the sites to share it with. Roles include separate permissions for working with shared content, so you can let someone view or edit shared records without giving them the same rights over the site's own content.