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.
Switching & Renaming Teams
At the top of the page, the Workspace section lets you:
- Switch between organizations you belong to with the Current workspace picker β picking another one switches the whole dashboard to it right away
- Rename your organization by editing the Workspace name field β the name your team sees when they switch between workspaces. Save changes (and Discard) appear at the top of the section once you change the name
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. Any other open dashboard tab then shows a Team switched in another window notice until you click Reload this tab β or until you switch back, which closes it by itself.
Team Members
The Members section lists everyone who can sign in to this workspace as expandable cards. Each card shows:
- Avatar with an online/offline status indicator
- Username and email
- Role β either
OwnerorMember - 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
- On wider screens, a Notifications on (green bell) or No notifications (gray) badge that shows whether the member would get a browser notification for new chats while their Yaplet tab is closed or asleep β hover it for the details; the phone app is not counted (see Desktop Notifications under Dashboard β Inbox)
- A Send notification button (see below)
Click on a member to expand their card and access all management options. Your own card does not expand.
Inviting New Members
Click the Add member button
Click the Add member button at the top of the Members section. The Invite member window opens.
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 and every board switched on. Untick the brands and boards 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. If you are not the owner (administrators included), the step lists only the permissions, brands and boards you hold yourself: it opens with the part of the chat-agent set you hold and all of your own brands and boards switched on, and if you hold no brand, the Brand access section is not shown. Trying to grant more than you hold is refused with "You can only grant permissions you hold yourself" (or "β¦brandsβ¦", "β¦boardsβ¦") β the same rule Edit access follows.
They accept
Click Invite. The invitation is created only when its email actually goes out. If it can't be sent, nothing is created, an error says why (for example "The invitation email could not be sent. Try again." or one of the limit messages below), and the Invite member window stays open with the address you typed and the access you chose, so you can fix the problem and try again. On success the window closes and the invitation appears under Invitations. 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.
Invitations are also limited: each organization can send at most 20 invitations an hour and 50 a day, and the same email address can receive at most 3 invitations a day β canceling an invitation and inviting again still counts. A refused invitation shows one of these messages:
- "Your workspace has sent 20 invitations in the last hour. Try again later."
- "Your workspace has reached today's limit of 50 invitations."
- "This address has received too many invitations today."
Invitations that haven't been accepted yet are listed in the Invitations section ("People you invited who haven't joined yet"), each marked Invited with the same access summary as a member row. Open one to adjust a pending member's permissions and brand access with Edit access before they accept, or cancel it with Delete invitation.
Enabling & Disabling Members
Members with the Organization permission can disable a member without removing them from the organization, with the Disable button in the Actions row of the member's expanded card. A disabled member:
- Cannot access the dashboard for this organization
- Cannot open or change anything of the organization from the Yaplet mobile app or a connected AI app either β this takes effect at once (some actions within half a minute)
- Retains all their settings and data
- Can be re-enabled at any time with the Enable button, which restores everything
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 with the Remove button in the Actions row. 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. A removed member can also no longer open their old chats with Yaplet, the assistant inside the dashboard, and neither can a disabled or suspended member. 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
spamcatchesSPAMandSpam, but notspammy - 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
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.
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 seventeen rights, and nobody in it can be given more than these until a module is bought: Audience, Brands & chat widgets, Content sources, Yaplet assistant, Yaplet speaks first, Inbox, Knowledgebase, Newsletter, Newsletter β Campaigns, Organization, Overview, Settings, Settings β Api, Settings β Domain, Settings β Email, Settings β Message Templates and AI agent.
Yaplet assistant is the right to use Yaplet, the assistant inside your dashboard. AI agent is the right to manage your website's AI agent.
Documentation is not among them. It is a paid module, so a new account cannot publish a documentation set until it is bought (it is open during the free 14 days).
Yaplet speaks first is a child of Yaplet assistant that lets Yaplet speak first. Owners have it automatically, and any other member gets it when the owner ticks it for them.
User Permissions (Individual)
Within the boundaries of your enabled modules, owners β and anyone with the Organization permission, up to the permissions they hold themselves β can customize which features each member can access. This allows fine-grained control over your team.
Key characteristics of the permission system:
- Hierarchical β Permissions are organized in a parent-child tree. For example, Inbox is a parent, and Inbox AI, Rephrase and Summary are among its children. A child's checkbox stays grayed out until its parent is switched on.
- Cascading β Disabling a parent permission automatically disables all of its children.
- Select All β Quickly grant all permissions at once; click it again to clear them all. A running count sits next to it ("12 of 47 selected").
What Each Permission Unlocks
This is where each right takes you.
| Permission | What it opens |
|---|---|
| Brands & chat widgets | The brand's Chat widget page, Brand settings, and οΌ New brand |
| AI agent | The brand's AI agent page |
| Content sources | The brand's Products page, the AI-sources half of Knowledge, and the brand's Content sources page |
| Voice & calls | The Phone section of the brand's AI agent page, Inbox β Calls, and Settings β Connections β Phone numbers |
| Chat workflows | The brand's Workflows page |
| Overview | The Overview page |
| Tickets | The 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 card in the sidebar at all. And Voice & calls reaches outside the brand: it is also what shows the organization's Phone numbers page.
AI agent, Chat workflows and Voice & calls are three independent top-level permissions, and turning one off has no effect on the others.
Your own branding only takes the "Powered by Yaplet" badge off the chat widget and help center. Renaming the website AI has its own permission, Rename Yaplet, which is available on Enterprise plans only.
Permission Presets
Instead of configuring permissions one by one, you can use presets to quickly assign a predefined set of permissions to a member. Click Apply Preset above the permission list and pick one; its menu has the groups Your Presets, Create Preset and Default Presets.
Yaplet includes built-in presets for common roles:
| Preset | Included Permissions |
|---|---|
| Chat Agent | Audience, Inbox, Inbox AI, Rephrase, Summary, Settings, Message Templates, Time Management |
| Newsletter Agent | Newsletter, Campaigns, Email automations, Newsletter Autopilot |
| Tickets Agent | Inbox, Settings, Message Templates, Time Management, Tickets |
Each preset only offers the permissions your organization actually holds β anything your plan doesn't include is dropped from it.
Owners can create custom presets tailored to their team's needs: choose Create Preset in the Apply Preset menu, give it a Preset Name, pick its permissions and click Create Preset. Custom presets are saved to your organization, appear under Your Presets and can be reused across all members. You can also delete custom presets when they're no longer needed.
How Permissions Are Checked
When a team member tries to access a feature, Yaplet checks:
- Does the organization have this permission available (based on the modules you've enabled)?
- 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.
- Does the user have this specific permission assigned?
If any check fails, the feature is hidden or access is denied.
Sending Notifications
Owners, and members with the right permissions, 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:
| Field | Description |
|---|---|
| Title | The notification headline (required) |
| Description | An optional longer message with more detail |
| Color | The notification's color theme β "Info", "Success", "Warning", "Error", or "Primary" |
| Icon | Choose from preset icons: Info, Warning, Check, Bell, Chat, Star, Gift, Megaphone, Calendar, or Wrench |
| Action URL | An 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:
- Hear a notification sound
- See a toast popup in their dashboard
- See the notification in their notification bell popover with a red badge
The member can dismiss the notification when they're done with it.
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 card and pages in the sidebar.
What changes for a restricted agent:
| Surface | Behavior |
|---|---|
| Brand card and switcher in the sidebar | Only lists brands they have been granted |
| Inbox conversation list | Only shows chats from permitted brands |
| Phone calls (Inbox β Calls) | Only shows calls filed against permitted brands; calls of a brand with no chat widget stay visible to everyone |
| Widget filter dropdown | Only lists widgets belonging to permitted brands |
| Visitors list | Only shows visitors browsing permitted brands |
| Realtime message toasts | Dropped for brands they don't have |
| Push notifications (web + mobile) | Not sent for brands they don't have |
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
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. Only the owner can change a pay rate
- 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:
| Property | Description |
|---|---|
| Name | The shift type label (e.g., "Regular", "Night Shift", "Weekend") |
| Rate Multiplier | A multiplier applied to the member's base pay rate (e.g., 1.5x for overtime) |
| Online | Whether the member should be marked as available for live chat during this shift |
Only the owner 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 cannot start an unassigned one
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 in the Actions row of that member's card. You can make multiple changes across different settings before saving.
After saving, a real-time update is broadcast to the affected member β their dashboard will automatically reflect the new permissions without needing to refresh.
Suspended Organizations
Yaplet's team can suspend an organization that is used for spam, phishing or other abuse, or whose email sending puts the delivery of other customers' email at risk. A suspension is a full stop: the organization can't send or change anything until Yaplet lifts it.
What Members See
Every dashboard page shows a red This workspace is suspended banner with the reason Yaplet gave and a Contact support button. Members can still:
- Sign in and read everything β conversations, contacts, reports and settings
- Export their own data
- Manage billing β pay, change the card, cancel the subscription
- Change their own email address and sign out
Anything that sends or changes something is refused with the message "This workspace is suspended." A reply typed in the inbox goes back into the composer, so the text isn't lost. The mobile app shows no banner, only the same message when someone tries to act. An owner can't delete their account while an organization they own is suspended.
What Stops
- No email leaves the organization β no replies, transcripts, ticket emails, newsletters or automation emails. Running and paused campaigns are canceled, email automations are switched off, and newsletter emails waiting in the queue are dropped.
- Your website and public pages go dark β the chat bubble disappears from your site, and your help center, documentation, roadmap and other public pages answer "page not found".
- Connections are refused β API keys and connected AI assistants stop working.
- Other channels stop β incoming email and Messenger and Instagram messages are not received (they are not kept and don't arrive later), AI phone agents stop taking calls, and social posting stops.
Owners get an email and an in-app notification when the organization is suspended, and again when the suspension is lifted.
Getting It Lifted
Only Yaplet can lift a suspension: use the Contact support button in the banner, or write to [email protected]. Once it is lifted, everything works again at once β except newsletters. Canceled campaigns stay canceled and email automations stay switched off until you start them again.