- 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.
77 comments
砂川 祐子
Hi
I want zendesk to be able to set the authority of Light agents more strictly.
The reason is that our team wants to limit the members who can access personal information as much as possible. Also, I want to give the light agents only the ability to write a help center.
It would be a problem for light agents to be able to see the end user's profile.
I am wondering about the below:
Ordinary agents such as "staff" can be restricted from viewing the list of user profiles. Why can't Light Agents do that?
I don't think there is a way to solve this at the moment, so I would like you to add this function.
Thank you.
PS
Thanks, Nicole.
I posted feedback.
https://support.zendesk.com/hc/en-us/community/posts/1260803650150-Setting-the-authority-of-Light-agents-more-strictly-about-member-tab
2
Nicole Saunders
Thanks for sharing your thoughts, Yuko. If you would like to submit an official feature request, please post your comment in the Product Feedback topic in the Community. This is our official communication channel with the product managers.
If you haven't posted there before, here's information on how to write an effective feedback post.
1
Glenn McConnell
We have Suite Growth and I do not see a Roles option in the Manage>People area. I have a couple light agents I need to set up
1
Beau P.
Hello Allison,
As long as agents have permissions to the article, light agents too should be able to edit. See https://support.zendesk.com/hc/en-us/articles/360001211527
Beau | Customer Advocate
Ask our Zendesk Community
1
Delphine Pougnard
Good morning,
Not sure if this has already been addressed previously, sorry if it is a repeat question.
I'm having trouble with the current light agents permissions. When one of our light agent replies on a solved ticket, it does not change the status to open. So our agents don't receive any notification / can't be aware they have replied.
This is problematic as our light agents are not aware we could not see their reply and our agents sometimes miss important notes that require action their end.
Is there any workaround to cover this scenario: if a light agent adds an internal note on a solved ticket, the ticket status will change to open.
Has anyone faced a similar problem and found a solution ?
Thanks
1
Beau P.
Hello Delphine,
You can setup a trigger for the purpose of reopening tickets upon light agent response, please see Brett's threaded recipe in the community post here: https://support.zendesk.com/hc/en-us/community/posts/360000925927-Set-ticket-to-open-when-a-light-agent-post-an-internal-note Note that the one amendment you'd make to the recipe would be changing the "status" condition to "status > is > solved".
Beau | Customer Advocate
Ask our Zendesk Community
1
Nikki
I really wish that we could set a Light Agent as our billing admin. The billing admin (who is actually our CEO) doesn't make public replies or need other features of a full admin - just should have ownership of billing and important matters like that. Would love to not have to pay for a full seat for them!
4
DJ Buenavista Jr.
Thank you for reaching out to Zendesk Support.
In regards to your concern, you can give permission to light agents by editing their roles in the Admin Center and enabling them to manage Guide.
This setting however is only for Enterprise plans, for Growth and Professional, you can do this by creating management permissions. You can check our article, Creating management permissions to define agent editing and publishing rights for more information about this.
Thank you!
Kind regards,
1
ADMIN
I would like to turn off some features for Light Agents - currently my options are greyed out.
The most pressing are the lights agents ability to view customer lists - as this is a data privacy risk in multibrand set ups.
I understand greying out these settings to not add to light agent abilities - but I need to subtract from light agent abilities. Can I have some support on how to do this?
1
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
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
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
Adam Martin
It is kind of painful that light-agents cannot unfollow tickets b/c they do not have cc edit access. Can this be changed so they can at least remove themselves from that field?
2
Lisa Kelly
Hi Amie,
Please work with the Advocacy team to create a ticket for this.
0
Sam Weekley
I find it disappointing that this is not available for light agents
- Use agent email forwarding to forward an email to your support address, creating a ticket with a public comment.
Our use case would be for our salesmen forwarding emails directly on behalf of customers. Usually with something like “Please process”. We can either set them up as a light agent and the text comes through as a bulk private comment or not set them up in the system at all but the customer will see the “Please process" part.
For me it would be ideal if the Light Agents comment could come through as a private comment with the customers comment a public comment with the ticket changing the requester to the customer.
This seems to make sense as technically the Light Agent is not creating a public comment it is the customer.
0
bill cicchetti
Is there a reason Light Agents cannot expand the list of CC'd users on a ticket? If there are more CC'd users than what fits on the screen the “+ <#> more” option is not available. This isn't a case of a Light agent trying to update a ticket, only to see who is CC's on the ticket.
0
Stephanie Fleming
Hello! I am trying to set up a trigger so that when a light agent makes an internal note the status changes to open.
An artice has been suggested in these comments. It no longer exists. https://support.zendesk.com/hc/en-us/community/posts/360000925927-Set-ticket-to-open-when-a-light-agent-post-an-internal-note
This community thread was then suggested, but the suggested trigger comment was removed. https://support.zendesk.com/hc/en-us/community/posts/5928020321178-Is-there-a-way-to-set-that-when-a-light-agent-makes-an-internal-note-on-a-ticket-it-will-set-the-ticket-to-open-if-it-is-on-pending-or-on-hold
Please advise on how we can set up this trigger so internal notes do not get missed! Thanks!
0