
- Suite Growth plans include up to 50 light agents.
- Suite Professional plans include up to 100 light agents.
- Suite Enterprise plans include up to 1000 light agents.
- Suite Enterprise Plus plans include up to 5000 light agents.
This article contains the following sections:
Understanding what light agents can do
Light agents have the following access and permissions.
Area | Light agents can... | Light agents can't... |
---|---|---|
Tickets |
|
|
People |
|
|
Guide (not available in Team plans) |
|
|
Reports |
|
|
Views |
|
|
Business rules |
|
|
Channels |
|
|
Mail API |
|
|
Apps |
|
|
Zendesk Chat |
|
|
Zendesk Talk |
|
Configuring light agent ticket access and reporting permissions
After you understand when to use the light agent role and what they can do, you can configure some of the permissions. The method you use to configure permissions for light agents varies depending on whether you are on a Suite Growth, Professional, or Enterprise plan. You can configure options for ticket access for light agents, and, if you're on Suite Professional or above, you can additionally configure access to reports. The other light agent permissions shown in the table above can't be changed.
Configuring light agent permissions with Suite Growth and Professional
If you're using Suite Growth or Professional, you can configure light agent permissions for reports and ticket access.
To edit reporting and ticket permissions for light agents (Suite Growth or Professional)
- In Admin Center, click
Workspaces in the sidebar, then select Agent tools > Agent interface.
- Next to Light Agent access, select an option for What kind of tickets can
this agent access?:
- All within this agent's group(s) for light agents to access only tickets in their groups.
- Requested by end users in this agent's organization for light agents to access only tickets requested by end users in their organization.
- All for light agents to access all tickets.
- If you selected All within this agent's group(s) above, and you want light agents to still be able to assign tickets to any group when they're the requester, also select Agent can assign to any group.
- For What can this agent do with reports, set Insights reporting permissions to Can view only or Cannot view.
- When you are finished, click Save.
Configuring light agent permissions with Suite Enterprise
If you're using Suite Enterprise, you can only configure light agent permissions for ticket access.
To edit reporting and ticket permissions for light agents (Enterprise)
You can't clone or modify the light agent role, except for the two settings for tickets and reporting.
- In Admin Center, click
People in the sidebar, then select Team > Roles.
- Next to the Light agent role, click edit.
If you are using Explore, you can only change settings in the Tickets section.
- Under Tickets, select an option for What kind of tickets can this agent
access?:
- All within this agent's group(s) for light agents to access only tickets in their groups.
- Requested by end users in this agent's organization for light agents to access only tickets requested by end users in their organization. Light agents with Suite Enterprise can't access queries or edit Explore reports, but you can share Explore dashboards with them in view only mode.
- All for light agents to access all tickets.
- If you selected All within this agent's group(s) above, and you want light agents to still be able to assign tickets to any group when they're the requester, also select Agent can assign to any group.
- Click Save.
57 Comments
Hi all
I am asking for a workaround. If a ticket is solved and a light agent that is a cc responds, the ticket does not change to Open and therefore, is never actioned. I am looking for a trigger to open the ticket.
Any thoughts on what trigger would work?
Please advise.
Thank you!
Dana Barr
Just did something like this a couple weeks ago. You'll need this condition:
So that it doesn't fire all the time, you should include additional conditions. In our specific use case, it's any time a light agent that is CC'd updates the ticket. They always update via email, so we include this condition:
We also have it restricted by form and other conditions, but it all depends on your needs. If you need more help, let me know what you're trying to accomplish and I'll see if I can.
Also, the action would be:
Please update the document to reference Agent vs Light Agent differences related to "Get started". A light agent is not provided with the "Get started" content.

Hi Darren,

Can you clarify what "Getting started" material you're referring to. Do you mean the Getting started tab that Admins see? Neither agents nor light agents can see that.
Hi Lisa, thanks for your follow up. I do mean the "Get started" section. This appears for Agents and Admins, Light agents do not have this. Would like to have reference to this within the documentation, would have raised my awareness of this difference.
Hi Darren,
Thanks for explaining! The Getting Started for agents covers items that we say light agents can't do. For example, creating a view, creating a macro. So, it makes sense that it wouldn't be available for light agents. We don't think it's necessary to mention this specifically, since we already cover these limitations in the article.
Hi All
As per above article (see this comment), how do we change the permissions for Light Agents to view all tickets on the Growth Suite plan?
Cheers
Chad
I can see that one of our Engineers was able to assist you regarding your Support Request. Thank you again for sending feedback! We appreciate it.
HI! I was wondering if there's any way to limit light agents access to the "Peoples" tab, I'm setting up a couple of temp. agents but I don't want them to have access to all my customers' database.
You would need to set up a new role. The Light Agent role is a default role that can't be changed.
Lou thanks for your reply, I guess this can't be done on a growth plan is it?
I'm not familiar with the Growth plan and can't find detail about it on the web site.
Looks like you're right. I found this and it mentions that can only be done on Enterprise plans.
Creating custom roles and assigning agents
Custom rules require either the Support or Suite Enterprise plan: Creating custom roles and assigning agents
We have a form that we use for an internal help center that only our Light Agents use.
I've seen issues with tickets not moving from Pending/Solved to Open status when the Light Agent replies to the ticket.
I saw the Lou comment on May 20, 2022, and tried to reproduce it, running into problems when our agents reply back in Support and try to save to pending/solved, it is triggering and changing back to Open. I would have thought the update via web form would stop that from happening.
Any advice?
Rob Lees
How are the Light Agents updating the ticket? I think that's key. Light agents CANNOT change the status of a ticket. I'm able to circumvent that with a trigger, but I did it when it's being updated via email. Not sure of other channels. See this article for more information on all the things Light Agents can and cannot do:
Understanding and setting light agent permissions
Hey Lou
Thanks for the reply!
They are replying via the "My Activities" and "Add to conversation" within our internal Help Center that we set up in ZD Guide.
Is a reply via the "Web form" channel considered the same as logging in and adding a comment as a Light Agent or is there a way to trigger off of that event?
My Trigger has "Update is via webform" as a condition, but I'm guessing the internal note vs Public reply is the culprit.
We struggle with how to handle internal support requests because of how the Light Agent permissions are configured. We are trying to move our customers and internal users away from using email as a support channel, but the Light Agent makes it nearly impossible because the internal comments severely limit the workflow.
Rob Lees
I'm not versed in that channel, so I can't say for sure. I would "assume" that no matter how the light agent updates, it will be a private note. I just use my trigger to set the status to Open so it will be visible to the people that need to see it was updated internally.
On a side not, I'm gonna find a way to use triggers to create a public reply by a light agent if it's the last thing I do LOL
Are there any intentions on making light agents able to be @mention? The reasoning given is:
Yet, we do have an option to enable Light agents to be CC'd into tickets, and adding that option still does not allow @mentions.
I'm simply trying to allow our internal end users to be able to mention each other without having to CC. Is this possible?
Why is it that Light Agents can see the "Customers" tab on the left menu bar when logged in, but not "Organizations"? They can search for organizations or click on the organization tab when looking at a ticket, so why not give the ability to search for an organization like they can for a customer/user?
As outlined in our article: About the Organizations page,
Light agents have limited permissions, hence the Organizations tab/page is not accessible to them. This is expected behavior.
Although we appreciate your input! If you have some time, I recommend starting a post about this on our Product Feedback page. Our Product Managers actively monitor our feedback threads, and conversations with high user engagement ultimately get flagged by the team for roadmap planning. You can use the Product Feedback Post Template. Thank you!
Under "Understanding What Light Agents Can Do," this is something light agents can't do:
However, in the Comments, Beau P says, "You can setup a trigger for the purpose of reopening tickets upon light agent response..."
I'm confused as to what we can use triggers to do. According to Beau P, we can use a trigger to allow a light agent to change the status of a ticket from Solved to Open. Does this mean we can use a trigger to allow a light agent to change the status of a ticket from Open to Solved? Can we use a trigger to allow a light agent to change the group assignment?
Light agents can add internal notes and triggers can respond to the text of private comments, so triggers could in theory allow light agents to change ticket statuses and group assignments - internal notes and triggers are native functionality, which I would think we'd be allowed to use as creatively as we like - in terms of light agent actions, when is it okay for us to do this and when is it not okay?
Chris C
There are a lot of things you can do with triggers and light agents. We do them all the time. I try to base the various actions on actual field changes(check box checked, drop-down set for a certain value, etc.). If you start down the road with comment text, you need to be careful that it's very specific or you'll have triggers firing all over the place.
About the only thing you can't do with triggers and light agents is public comments, but I'm determined to figure out a way to do it.
It doesn't look like light agents can view deals or send notes to sales via the sell app. Is this correct?
Hi Kate Woollard,
You are correct. In order to have access to Sell, you must be using an agent seat in your license as an agent or admin.
Hi, we use Enterprise Suite, I have cloned the Light agent role, since one Light agent role should access private groups and the other not. But the new role is considered as agent seat and is taking up our agent seats (even with less power than the locked Light agent role) Please advice what to do. Thanks
This is actually expected since all cloned roles will be considered custom-roles. Only system-created "Light Agent" roles will allow you to create and add users without taking one of your agent seats. Any user within a custom-role (even with less permission than the system Light agent role) would require an agent seat.
I hope this answers your question. Thank you!
Please sign in to leave a comment.