Control who can do what
Decide what each role may do, for your whole organization
Fit the role defaults to how your teams actually work, without inventing new roles.
Change what Viewers, Operators and Editors can do in every domain from one Permissions page.
What this changes for your team.
Settings → Permissions shows each domain role against each action and lets an organization Owner or Admin change the defaults: take publishing away from Editors, let Operators maintain knowledge. Changes apply to everyone with that role, in every domain, within a few seconds, and each save is recorded in the audit log. Some cells stay fixed so a domain always remains manageable - Owners hold everything, every member can see the domain, and who approves is set by each domain's approval policy.
How it works in practice.
- 01
Open Settings → Permissions and read the grid; cells your organization changed are marked.
- 02
Tick or untick a permission for a role, within the rule that a role keeps everything the roles below it have.
- 03
Save, or Restore defaults to return to the standard matrix.
What you can plan around.
What to expect, including limits that matter to your team.
Only running, triggers, webhooks, authoring and knowledge can be changed, and only for Viewers, Operators and Editors.
A matrix where a lower role can do something a higher role cannot is refused before it is saved.
Managing members, connections and domain settings stays with domain Owners whatever the matrix says.
Bring one real process
See how Yekar.AI fits the way you work.
Start with a job your team already owns, plus the tools and decisions around it.
Get started