Organizations

Manage your team members, control feature access with permissions, grant per-brand access, configure board visibility, set pay rates, assign shift types, and maintain your organization's blocked words list.

You need the Organization permission to access this page. Anyone with it can manage teammates — including enabling, disabling, and removing them — but owners can't be disabled or removed. Renaming the team and sending invitations stay owner-only.

Switching & Renaming Teams

At the top of the page, you can:

  • Switch between organizations you belong to using the team dropdown
  • Rename your organization by editing the team name field (owner only)

Which organization you are working in is stored on your account rather than in the browser, so switching here changes it in every window and tab you have signed into.

Team Members

All members of your organization are listed as expandable cards. Each card shows:

  • Avatar with an online/offline status indicator
  • Username and email
  • Role — either Owner or Member
  • A (You) label next to your own entry
  • A short access summary — for example "8 permissions · 2 brands", or "Full access — owners and admins bypass permissions" on an owner or admin row

Click on a member to expand their card and access all management options.

Inviting New Members

Click the Invite button

Click the Invite member button at the top of the members section.

Enter their email

Type the email address of the person you want to invite.

Set access & permissions

The Access & permissions step opens with a chat-agent permission set already ticked and every brand switched on. Untick the brands this person should not see before you send. The same "N permissions · M brands" summary sits beside the step so you can see what you are about to grant.

They accept

The invited person receives an email with a link to join your organization. Invitations expire after 7 days. Exactly the permissions and brands you chose are applied the moment the invitation is accepted — and only those the organization still holds at that moment.

The free plan includes a single seat — the owner. Adding or inviting more members requires extra seats, purchased as volume-tier add-ons. When you've used every seat, the invite action prompts you to upgrade before a new invitation can be sent.

You can also view, edit, and cancel pending invitations from the invitations list — including adjusting a pending member's preset permissions and brand access before they accept. Each pending invitation shows the same access summary as a member row.

Enabling & Disabling Members

Members with the Organization permission can disable a member without removing them from the organization. A disabled member:

  • Cannot access the dashboard for this organization
  • Retains all their settings and data
  • Can be re-enabled at any time

This is useful for temporarily revoking access without losing a member's configuration.

Removing Members

Members with the Organization permission can permanently remove a non-owner member from the organization. This deletes all of that member's permissions, brand access, board access, and shift type assignments. Adding the same person back later therefore starts them from nothing rather than quietly restoring their old access. This action requires confirmation.

Blocked Words

Maintain an organization-wide list of words and phrases that visitors can't send in chat. When a visitor's message contains a blocked entry, it isn't sent — they see a short hint asking them to rephrase, and the message never reaches your team, the conversation history, or the AI assistant.

  • Add a word or phrase in the input and press Enter or click Add — the list saves automatically
  • Remove an entry by clicking the × on its chip
  • Matching is whole-word and case-insensitive — blocking spam catches SPAM and Spam, but not spammy
  • Accented forms count as separate words — add each variant you want to block
  • Multi-word phrases are supported
  • Up to 200 entries, each up to 50 characters
Blocked words apply to widget chat messages — both AI and live-chat conversations. They don't apply to Facebook/Instagram conversations or voice calls.
The list is checked in the visitor's browser for instant feedback (and enforced again on the server), so a technically savvy visitor could inspect it. Don't add anything confidential — like internal terms or personal names you wouldn't want seen.

Understanding Permissions

Yaplet uses a layered permission system that controls what features each team member can access. There are two levels:

Organization Permissions (Module-Based)

Organization permissions define the maximum set of features available to your entire team. These are determined by the modules you've enabled — if a module isn't enabled, nobody in your organization can access it.

Think of organization permissions as the ceiling. No individual user can have more permissions than your enabled modules allow.

For example, if your plan doesn't include Voice AI, no team member — not even the owner — will see the Voice & calls permission at all.

What a New Organization Starts With

Every new organization is granted fourteen rights, and nobody in it can be given more than these until a module is bought: Audience, Brands & chat widgets, Copilot, Inbox, Knowledgebase, Newsletter, Newsletter → Campaigns, Organization, Overview, Settings, Settings → Domain, Settings → Email, Settings → Message templates and Vex AI.

Documentation is not among them. It is a paid module, so a new account cannot publish a documentation set until it is bought.

User Permissions (Individual)

Within the boundaries of your enabled modules, owners can customize which features each member can access. This allows fine-grained control over your team.

Owners automatically have all permissions that your enabled modules allow. You cannot restrict the owner's access.

Key characteristics of the permission system:

  • Hierarchical — Permissions are organized in a parent-child tree. For example, Inbox is a parent, and Inbox.AI, Inbox.Rephrase, Inbox.Summary are children. Enabling a child automatically enables its parent.
  • Cascading — Disabling a parent permission automatically disables all of its children.
  • Select All / Deselect All — Quickly grant or revoke all permissions at once, with a running count above the list ("12 of 47 selected").

Renamed Permissions

Eight permissions were renamed when the dashboard reorganised around brands. The old names are gone; these are the labels an admin reads today.

Old nameLabel now shown
WidgetsBrands & chat widgets
Widgets → BrandingRemove branding
Automation → AIVex AI
Automation → CustomChat workflows
Automation → VoiceVoice & calls
Automation → FormForms (a child of Tickets)
Settings → BoardsBoard management (a child of Tickets)
Newsletter → WorkflowsEmail automations

There is no Automation parent switch any more. Vex AI, Chat workflows and Voice & calls are three independent top-level permissions, and turning one off has no effect on the others. Inbox.AI also stopped rendering as the nonsense string "A I" and now reads Inbox AI.

What Each Permission Unlocks

The menu these rights open is new, so it is worth spelling out where each one lands.

PermissionWhat it opens
Brands & chat widgetsThe brand's Chat widget page, Brand settings, and + New brand
Vex AIThe brand's Vex pages, its Products page, and the AI-sources half of Knowledge
Voice & callsThe brand's Voice page, Inbox → Calls, and Settings → Organization settings → Phone numbers
Chat workflowsThe brand's Workflows page
OverviewThe brand's Overview page as well as Home → Overview
TicketsThe Tickets section; Board management additionally opens + New board and a board's Settings tab, and Forms opens a board's Forms tab

Two things follow from this. A member who can open none of the brand's pages and cannot create a brand doesn't see the Brand heading in the menu at all. And Voice & calls reaches outside the brand: it is also what shows the organization's Phone numbers page.

Knowledge is the one page that works as "any one of three": it opens for a member holding Vex AI, Knowledgebase or Documentation, and each zone inside it then enforces its own right. Be aware that the actions on a knowledge source — Show at your web address, Take down, Copy to another brand, Move to another brand and Delete — all require Vex AI specifically. A member with Knowledgebase but not Vex AI can open the page but not use those buttons.

Permission Presets

Instead of configuring permissions one by one, you can use presets to quickly assign a predefined set of permissions to a member.

How Permissions Are Checked

When a team member tries to access a feature, Yaplet checks:

  1. Does the organization have this permission available (based on the modules you've enabled)?
  2. Is the user an owner? If yes, the permission is granted automatically. This shortcut covers feature permissions only — brand access is bypassed by owners and admins, while board access is bypassed by owners alone.
  3. Does the user have this specific permission assigned?

If any check fails, the feature is hidden or access is denied.

Sending Notifications

Owners and admins can send direct notifications to individual team members from the Organizations page. This is useful for communicating important updates, reminders, or announcements that a specific member needs to see immediately.

To send a notification, click the Send notification button on a member's card. A modal opens with the following options:

FieldDescription
TitleThe notification headline (required)
DescriptionAn optional longer message with more detail
ColorThe notification's color theme — "Info", "Success", "Warning", "Error", or "Primary"
IconChoose from preset icons: Info, Warning, Check, Bell, Chat, Star, Gift, Megaphone, Calendar, or Wrench
Action URLAn optional link — if provided, the notification becomes clickable and takes the member to that page

Once sent, the notification is delivered instantly in real-time. The target member will:

  1. Hear a notification sound
  2. See a toast popup in their dashboard
  3. See the notification in their notification bell popover with a red badge

The member can dismiss the notification when they're done with it.

This feature requires the Organization permission. Only owners and users with this permission can send notifications.

Brand Access

Access is granted per brand, not per widget. In each member's expanded card, the Brand access section lists your organization's brands in the order they were created, with a switch each. The helper line reads "Owners and admins always have access to every brand."

  • Toggle a brand on to grant access, off to restrict
  • Use Select All to grant every brand at once
  • Click Save to apply

Granting a brand gives that agent the brand's conversations in their Inbox and that brand's section in the left-hand menu. It is no longer an inbox-only boundary.

What changes for a restricted agent:

SurfaceBehavior
Brand section in the sidebarOnly lists brands they have been granted
Inbox conversation listOnly shows chats from permitted brands
Widget filter dropdownOnly lists widgets belonging to permitted brands
Visitors listOnly shows visitors browsing permitted brands
Realtime message toastsDropped for brands they don't have
Push notifications (web + mobile)Not sent for brands they don't have
Owners and admins bypass this restriction — they always have every brand. No switches are shown for them at all, and neither is the Select All button; their card carries only the helper line quoted above.
Because access now keys on the brand rather than on a widget, a brand with no chat widget is properly restricted too. Previously such a brand matched nobody's list and was therefore shown to every restricted agent. Ticking an agent on the Agents list inside the chat widget designer writes exactly the same grant — it gives them the widget's whole brand, and unticking takes the brand away.

Board Access

Boards are used for tracking bugs, feature requests, and custom items. By default, members may not have access to all boards.

Owners can configure per-member board access by toggling which boards each member can see and interact with.

  • Use the Select All button to grant access to every board at once
  • Toggle individual boards on or off
  • Members will only see boards they have been granted access to
Board access and brand access are not bypassed by the same people. Owners always see every board; an admin can still be restricted to certain boards. Brand access, by contrast, is bypassed by owners and admins.

Hourly Pay Rate

Each team member can have an individual hourly pay rate (in USD). This value is used by the Shifts module to calculate shift costs and payroll.

  • Set the rate in the member's expanded card
  • Leave it empty if the member doesn't need time tracking
  • The rate is combined with shift type rate multipliers to calculate actual pay for different shift types

Shift Type Assignments

If your organization uses Shifts, you can control which shift types each member is allowed to use when clocking in.

Shift types define different categories of work, such as:

PropertyDescription
NameThe shift type label (e.g., "Regular", "Night Shift", "Weekend")
Rate MultiplierA multiplier applied to the member's base pay rate (e.g., 1.5x for overtime)
OnlineWhether the member should be marked as available for live chat during this shift

Owners can assign shift types per member:

  • Use Select All to give access to all shift types
  • Toggle individual shift types on or off
  • Members will only see their assigned shift types when starting a shift, and starting an unassigned one is refused by the server as well
Shift types are created and managed in Team → Shifts → Shift Types. The Organizations page is where you assign them to individual members.

Saving Changes

When you modify a member's permissions, brand access, board access, pay rate, or shift types, the changes are tracked locally until you click Save. You can make multiple changes across different settings before saving.

Changes are not applied until you save. If you navigate away without saving, your modifications will be lost.

After saving, a real-time update is broadcast to the affected member — their dashboard will automatically reflect the new permissions without needing to refresh.