Set roles and permissions

Updated May 22, 2026

Someone on your team can see too much, or not enough, and you need to fix it. Yaplet answers that in two layers: two built-in roles that skip the switches entirely, and a set of individual switches for everybody else.

Open the permission editor

There is no Organization entry in the left menu, so it is easy to hunt for one and not find it. Click your avatar at the bottom-left of the dashboard and choose Manage team. Then click a member's row to expand it — their Permissions switches are the first thing inside. Your own access is not editable here, and the owner's row stays closed.

That menu entry only appears for people who hold the Organization permission. If you cannot see it, ask whoever set up the account.

The two built-in roles

Owner

The owner is the person who created the organization. There is exactly one. The owner has every right in the account, cannot be disabled, and cannot be removed — not even by an administrator.

Admin

An administrator skips the permission switches completely. Their row reads "Full access — owners and admins bypass permissions" instead of a list, and they see every brand's conversations in the inbox without being granted a single brand.

One exception: only the owner bypasses board access. An administrator still only sees the ticket boards they have been given. It is the one place where "admin" is not the same as "everything".

The role is printed on each member's row, but there is no control on the page for changing it. If you need another administrator, ask your workspace owner.

Everyone else gets switches

Every other member starts from nothing and gets exactly what you switch on. Each switch carries a one-line description of what it opens, so you do not have to guess. Above the list, Select All switches every available right on (click it again to clear them), and a counter such as 12 of 47 selected tells you how many you have turned on.

Turn a switch off and the matching screens disappear from that person's menu the next time their dashboard loads.

Being a member is not enough to work in the inbox. Replying, snoozing, transferring, asking for a rating, sending forms and workflows, banning a visitor, translating and drafting a reply with AI all need the Inbox switch, and the visitors list needs Audience. A member who is limited to some brands is also refused on the conversations of the other brands.

Parents and children

Some rights sit inside another one. Tickets has Board management and Forms beneath it; Newsletter has Campaigns, Email automations and Newsletter Autopilot. A child cannot be ticked until its parent is on, and turning the parent off clears every child under it in one go.

AI agent, Chat workflows and Voice & calls are three independent switches, so turning one off leaves the other two exactly as they were.

Ready-made presets

Rather than ticking twenty switches by hand, use Apply Preset. Three presets are built in:

  • Chat Agent — Audience, Inbox and its AI helpers, Settings, Message Templates and Time Management.
  • Newsletter Agent — Newsletter, Campaigns, Email automations and Newsletter Autopilot, each only if your organization has it.
  • Tickets Agent — Inbox, Settings, Message Templates, Time Management and Tickets.

A preset replaces the current selection rather than adding to it, so apply it first and adjust afterwards. You can also save your own with Create Preset in the same menu: give it a Preset Name and pick its rights. It appears under Your Presets, is available for every member of your organization, and can be deleted from the menu when you no longer need it.

Your organization's own rights are the ceiling

Nobody can be granted something the organization itself does not have. The editor simply does not list those switches — if your account has no Documentation module, there is no Documentation switch to turn on for anyone. Buying the matching module is what makes the switch appear.

A brand-new organization starts with these rights: Audience, Brands & chat widgets, Content sources, Yaplet assistant, Yaplet speaks first, Inbox, Knowledgebase, Newsletter, Campaigns, Organization, Overview, Settings, Api, Domain, Email, Message Templates and AI agent.

Pause or remove someone

At the bottom of an expanded member, under Actions, you get three buttons: Save, Disable and Remove. Save keeps every change you made in that member's card.

  • Disable keeps the account in your organization but stops the person signing in, and they can no longer open or change anything of your workspace from the dashboard, the Yaplet mobile app or a connected AI app. This takes effect at once (some actions can take up to half a minute to stop). It also cuts off every AI access that works as them at once — their Yaplet assistant, any AI app they connected to Yaplet, and any API key whose AI access they switched on. Everything works again when you re-enable them (the button then reads Enable). Use it for leave or a notice period.
  • Remove takes them out of the organization and deletes their access rows with them — permissions, brands, boards and shift types. Re-adding the same person later starts from nothing.

Neither works on the owner, and neither works on yourself.

What's next

To scope someone to particular brands, boards or shift types, see Restrict what a teammate can access. For a switch-by-switch list of what each right opens, see What each permission unlocks.

Did this article answer your question?