![Available on all Suite plans](https://zen-marketing-documentation.s3.amazonaws.com/docs/en/plan_available_suite_all.png)
![Available on Support Professional plans and above with add-on](https://zen-marketing-documentation.s3.amazonaws.com/docs/en/plan_available_add_p_add_e.png)
- 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. This also means the light agent won't be able to update organization fields for end users or lookup relationship fields that point to organizations.
- 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?:
- Requested by end users in their organizations for light agents to access only tickets requested by end users in their organization. This also means the light agent won't be able to update organization fields for end users or lookup relationship fields that point to organizations. 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 within their groups for light agents to access only tickets in their
groups.
- Assign tickets to any group for light agents to be able to assign tickets to groups they don't belong to, including private groups.
-
Within their groups and all public groups
- Assign tickets to any group for light agents to be able to assign tickets to private groups they don't belong to.
- 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.
76 comments
Dana B
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!
0
Lou
Dana B
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:
1
Darren Stephens
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.
![](/hc/user_images/4LL-MCT7auZD-hIXbDpQTQ.png)
0
Lisa Kelly
Hi Darren,
![](/hc/user_images/vFYmeKr7s8Vw-6fqxjvYRQ.png)
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.
0
Darren Stephens
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.
0
Lisa Kelly
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.
0
Chad Susa (Gravity CX - Zendesk Partner)
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
0
Cheeny Aban
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.
0
Soporte
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.
0
Lou
You would need to set up a new role. The Light Agent role is a default role that can't be changed.
0
Soporte
Lou thanks for your reply, I guess this can't be done on a growth plan is it?
0
Lou
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
0
Dave Dyson
Custom rules require either the Support or Suite Enterprise plan: Creating custom roles and assigning agents
0
Rob Lees
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?
1
Lou
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
1
Rob Lees
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.
0
Lou
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
0
Simon Chang
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?
0
Dave Dyson
0
Jake Warren
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?
0
Christine
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!
0
Chris.Chapman
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
0
Lou
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.
0
Kate Woollard
It doesn't look like light agents can view deals or send notes to sales via the sell app. Is this correct?
0
Dainne Kiara Lucena-Laxamana
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.
0
Jozsef Hajdu
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
0
Gabriel Manlapig
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!
1
Gina
Hi there, we have a bit of a unique set up with Zendesk. We are a quick service restaurant chain. We have set up each store as a light agent. All customer complaints are fielded by the CS Team at head office and where the complaint is store specific, the CS agent will triage it to the store. The store contacts the customer and resolved the issue then writes an internal note to CS Team noting how they resolved it and to please solve the ticket.
This system is working well, however, I need the stores to see their solved tickets (for audit purposes) but because it is not them that is solving the ticket and because they are only a light agent, they cant see the tickets.
Ive tried changing the light agent role to 'within their groups and all public groups' which means they can see the 'Solved' view however it also shows them all other views for our other businesses. Is there any way I can set it up so the stores can remain light agents but see their historical solved tickets?
0
Pedro Rodrigues
Hi Gina, if your light agents are allowed to access any tickets within their groups and any public groups, you should be able to set up a View for your Stores to see solved tickets, regardless of who solved them.
Exmaple. You can create a trigger that detects the Store's internal note (and group reassignment, if it happens during the same action/event), and add a tag ('stores_solved'). Then your View would be available to the Stores group, and have two conditions: status is greater than On-hold (or Pending if you're not using On-hold status), and tags contain stores_solved).
Additionally, if you need each store to see their own tickets exclusively - that is, store A shouldn't be able to see store B's tickets and vice versa - then I'd suggest taking a look at Organizations and consider modifying the light agent role to tickets "Requested by end users in their organisations" (if that doesn't affect any other teams with light agent roles and different workflows/tasks). This change would allow you to have a single "Stores" group but multiple Orgs (for example: "Stores Org • Store A", "Stores Org • Stores B". Because of the role's settings, the same Solved tickets view would show Store A different tickets than Store B.
These are just examples of how to address this issue based on my interpretation of the situation described.
Hope it helps!
0
Chad Susa (Gravity CX - Zendesk Partner)
Hi Gina,
We are a Zendesk partner and we worked with a Zendesk customer (furniture retailer) to configure something similar.
Each store is a Light Agent and they create tickets for various support issues including requests on behalf of the store customers (end customers are requesters) as well as creating their own tickets for 'Store Support' (the stores are the requester).
They wanted the ability for the Stores (Light Agents) to access a view to be able to see ONLY their tickets they have created for end users, which were assigned as normal to the HQ customer service team, as well their own tickets where the store needed support from HQ.
They didn't want to use Organisations as mentioned above by Pedro (which is a great idea).
Our solution is a little in depth so it might be best to explain one-to-one with you.
Let me know if you interested.
The other thing that might work is using the 'Followed Tickets' view under the agent profile. When you say "All customer complaints are fielded by the CS Team at head office and where the complaint is store specific, the CS agent will triage it to the store." - how are they 'triaged' out to the stores? Do you add them as a follower to the ticket? If so, your stores can access the 'Followed tickets' view under their individual profile to see tickets they are followers on. (See below)
Cheers
Chad
0