All updates

Editor role and access requests

Give teammates the Editor role to run jobs, companies, candidates, the blog and the inbox without touching settings or billing. Editors can request more access in one click.

Abi Tyas TunggalAJack WalshJ
By Abi Tyas Tunggal and Jack Walsh on

Most people who help run a job board need jobs, companies and candidates, not billing or domains. Your team now has three clear roles: Owner, Admin and Editor.

  • Owner: everything, including deleting the board and transferring ownership
  • Admin: everything except those two actions
  • Editor: the board's day-to-day content: jobs (including publishing), companies and their teams, employers and access requests, job seekers, the blog and the inbox

Editors can view, but not change, job alerts, the job form, collections and email templates. Settings, the website builder, domains, sign-in methods, integrations, API keys, the audit log, team management and billing are hidden from their navigation. Cavuno checks these permissions on every action, not only in the menu.

Teammates who had the Member role are now Editors, and can do more than before. Change anyone's role in Settings → Members.

Request access

When an Editor opens a page their role does not include, they see Request access (or Request edit access on a view-only page). The Owner and every Admin get a notification and an email with a Make (name) an Admin button, so granting access takes one click.

Read Team roles and permissions.

Design your own coming-soon page

Paid boards built with the AI website builder can now design the page visitors see while the board is password protected. Ask the builder for a page at /coming-soon-gate, publish, and Cavuno shows your design with the password entry added. Boards without one get a coming-soon page styled with your board's colors, fonts and logo instead of a plain password form.

Read Design your own coming-soon page.

Other improvements

  • Search matches inside words: category, skill and place typeahead now matches text anywhere in a name, so "script" finds "JavaScript" and accents do not matter. See the taxonomy reference
  • List top-level categories: the SDK and Operator API can list only top-level categories, and each category now carries its parentId. See Top-level categories
  • Builder access for coding agents: Operator API keys can hold Builder: read, Builder: manage and Builder: publish permissions, so a local coding agent can work on your board's site through the Cavuno CLI or MCP. See Builder access
  • Search Cavuno's docs from MCP: the Cavuno MCP server has a new search_docs tool, so your AI assistant can look up how Cavuno works while it helps you. See Docs search