How to Create Team Roles and Permissions in ZazzyAgent
Giving every employee full access to ZazzyAgent is usually unnecessary.
A support agent doesn't need to modify API integrations.
A developer doesn't necessarily need access to billing or every customer conversation.
A marketing employee may need broadcasts but not automation-development tools.
Team Roles let you create permission sets for different jobs.
What is a Team Role?
A Team Role is a collection of permissions.
For example:
Support Agent
could have access to:
Subscribers
Live Chat
Relevant customer tools
while:
Developer
could have:
Flow Builder
API integrations
AI configuration
The exact permissions available depend on the current ZazzyAgent account configuration.
Why use roles?
Without roles:
User 1 → custom permissions
User 2 → custom permissions
User 3 → custom permissions
User 4 → custom permissions
This becomes difficult to maintain.
With roles:
Support Role
↓
Rahul
Priya
Amit
One permission structure can be assigned to multiple people.
Step 1: Open User Permission
Open the administration area.
Go to:
User Permission
This is where Team Roles are created and managed.
Step 2: Create a new role
Choose:
Create
Then create a new Team Role.
Step 3: Name the role
Give the role a clear name.
Examples:
Support Agent
Sales Manager
Automation Developer
Marketing Manager
Avoid:
Role 1
Step 4: Set platform access
The role can control access to supported platform/channel areas.
For example, a user may need:
but not:
or a particular role may need access to several channels.
Choose only what that person's job requires.
Step 5: Set feature permissions
ZazzyAgent roles can control access to different platform modules.
Depending on the available configuration, this can include areas such as:
Subscribers
Broadcasts
AI
Live Chat
Integrations
Flow Builder
WhatsApp features
Administration
The objective is to give the user the tools required for the job without opening unrelated areas.
Permission levels
A role can use different permission levels for supported modules.
The common levels are:
Create
Update
Delete
Special
What does Create mean?
Create allows a user to add new items in the relevant module.
For example:
Create a new broadcast.
What does Update mean?
Update allows a user to modify existing configuration.
For example:
Edit an existing flow.
What does Delete mean?
Delete allows the user to remove existing items.
This should be assigned carefully.
Deleting a production flow or customer-related data can have significant consequences.
What does Special mean?
Special permissions provide additional functionality beyond the standard Create/Update/Delete controls for modules that support them.
Only grant Special permission when the user actually needs it.
Example: Support Agent role
A support employee might need:
Subscribers
→ View/update
Live Chat
→ Full operational access
Broadcasts
→ No access
API Developer
→ No access
Administration
→ Limited/no access
The exact combination should match your business.
Example: Marketing role
A marketing user might need:
Broadcasts
→ Create/Update
Subscribers
→ View/filter
Live Chat
→ Optional
API Developer
→ No access
Example: Developer role
A technical user might need:
Flow Builder
→ Create/Update
HTTP API
→ Create/Update
Webhooks
→ Create/Update
AI Configuration
→ Update
but not necessarily:
Customer Live Chat
Least privilege
A useful rule is:
Give each role the minimum access required to perform its job.
If someone needs more access later, you can expand the role.
It's much easier to manage a controlled permission structure than unrestricted access for everyone.
Assign the role to users
Once the role is created, assign it when creating or editing a Team Member.
For example:
Support Role
↓
Rahul
Priya
Both users inherit the role's permissions.
Change a role later
Suppose you realize that support employees need access to one additional module.
Instead of changing every employee individually, update the Team Role.
Users assigned to that role can then receive the updated permission structure.
Role vs individual permissions
A role is the reusable permission structure.
A team member is the person receiving that structure.
Think:
Role = rules
User = person
Platform access vs feature access
These are different.
For example:
Instagram access
doesn't automatically mean:
Full administration access to everything related to Instagram and the entire account.
Permissions can be controlled at multiple levels.
Be careful with Delete
Delete permissions should be assigned intentionally.
A person who only needs to edit flows probably doesn't need permission to delete them.
This reduces accidental removal of production assets.
Be careful with Special permissions
Special permissions can expose advanced functionality.
Don't use:
Give everyone Special because it is easier.
Use it when required.
Review roles regularly
As your business changes, review:
Who has which role
Which modules the role can access
Whether Create is needed
Whether Delete is needed
Whether Special is needed
Example organization
Business
↓
Team Roles
├── Owner/Admin
├── Sales
├── Support
├── Marketing
└── Developer
↓
Team Members
This structure scales much better than assigning permissions randomly.
Common mistakes
Too much access
Remove permissions the employee doesn't need.
Too little access
Add the specific module required rather than giving full administrator access.
Everyone has Delete
Restrict destructive permissions.
Role names are unclear
Use job-based names.
Permission changes aren't reflected as expected
Check which role the user is actually assigned to.
Recommended permission strategy
Start with the employee's job.
Ask:
What do they need to accomplish?
Then:
Which ZazzyAgent modules are required?
Then:
Do they need Create, Update, Delete or Special access?
Build the role around those answers.
The key idea
A good Team Role doesn't answer:
What can ZazzyAgent do?
It answers:
What does this particular employee need to do?
That keeps your workspace easier to operate and safer to manage.