How to Restrict a Team Member to Specific Bots in ZazzyAgent

A business can have more than one bot.

For example:

• Main WhatsApp bot

• Support WhatsApp bot

• Instagram account

• Facebook account

• Separate client bots

Not every employee should necessarily have access to all of them.

ZazzyAgent allows team-member access to be restricted to specific bots.

Why restrict bot access?

Imagine an agency managing:

20 client bots.

You don't want a support employee for Client A accidentally changing Client B's automation.

Likewise, an Instagram manager may only need access to the company's Instagram bot.

Restricting bot access reduces accidental changes and unnecessary visibility.

Who should use restricted bot access?

It's especially useful for:

• Agencies

• Multi-brand businesses

• Businesses with separate departments

• Businesses with separate support/sales bots

• Teams managing multiple channels

How it works

A Team Role controls:

What a user can do.

Bot access controls:

Which bots they can work with.

For example:

Support Role
     +
Support WhatsApp Bot
     ↓
Support Employee

The employee may have support permissions but only for the selected bot.

Step 1: Open User Manager

Open:

User Manager

Find the team member you want to configure.

Choose:

Edit

Step 2: Locate allowed bots

Depending on your account configuration, you can specify the bots the user is allowed to manage.

Available bot categories can include:

• WhatsApp

• Meta/Instagram/Facebook

• Telegram

• Webchat

Step 3: Select the appropriate bot

Choose only the bots this person needs.

For example:

Support WhatsApp

rather than every WhatsApp bot in the account.

Example: Sales team

Suppose your business has:

Sales WhatsApp

Support WhatsApp

Internal WhatsApp

A sales employee may only need:

Sales WhatsApp

The support bot doesn't need to appear in their workspace.

Example: Agency

Your agency manages:

Client A

Client B

Client C

A team member assigned to Client A can be restricted to:

Client A bots.

This reduces the chance of accidentally editing another client's automation.

Bot access and roles are separate

Suppose:

User A

has the Developer role.

They may have permission to edit flows.

But if they're only allowed to access:

Client A bot

they shouldn't be able to edit Client B's flows.

This creates two layers of control:

Team Role
"What can you do?"
        +
Bot Access
"Where can you do it?"

Don't give access to every bot by default

Ask:

Does this employee actually need access?

If not, leave it restricted.

Multiple bots for one employee

Some employees genuinely need several bots.

For example:

A support manager handles WhatsApp and Instagram.

Give that person access to the relevant bots only.

What if a new bot is added later?

Review whether existing team members should receive access.

Don't assume they automatically need it.

Changing departments

Suppose an employee moves:

Sales → Support

Update their bot access and role together.

For example:

Old:
Sales Role
Sales Bot

New:
Support Role
Support Bot

Temporarily restrict access

If someone is temporarily away, consider setting the user's status to:

Inactive

rather than deleting their account.

This preserves the account structure for later reactivation.

Bot access and Live Chat

A team member may have access to a particular bot but still have separate restrictions on which conversations they can see in Live Chat.

These are different controls.

Example

User has access to:

Support WhatsApp Bot

But:

Allow Only Assigned Chat in Livechat

is enabled.

The user may then be limited to the conversations assigned to them.

Common mistakes

User sees too many bots

Review their allowed-bot configuration.

User can't access the required bot

Check both:

• Role permissions

• Allowed bot

Both can matter.

User has the right role but still can't perform an action

The role may not include the required module permission.

Employee moved departments but still sees old bots

Update bot access when changing roles.

Recommended model

Use:

Team Role

for job responsibility.

Use:

Allowed Bots

for business/channel responsibility.

Use:

Live Chat restrictions

for conversation responsibility.

The three-layer model

Role
 ↓
What can the user do?

Bot Access
 ↓
Which bots can they manage?

Assigned Chats
 ↓
Which conversations can they see?

Separating these controls gives you much more precise team management.