Understanding and setting light agent permissions



image avatar

Lisa Kelly

Zendesk Documentation Team

Edited May 07, 2025


28

77

86 comments

Can you explain more on what needs to be configured for Light Agents to see HC articles that are restricted to agents? In your table, it says “View areas of the Help Center knowledge base and community that are restricted to agents.”

I have to either make them a full Agent for Support or an Agent in Guide (not View). This opens up access rights that I rather not grant to everyone.

THX!

0


Hey Adam, thank you so much for taking the time to provide us with your feedback here. I wanted to point you in the direction of our product feedback forum for Admin Center where we collect product feedback and where our PM’s review feedback from our customers. We would greatly appreciate you using this forum to share your feedback with us for better visibility. Here is our product feedback template to get you started. Thank you!

0


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


 desde el dia de ayer los agentes ligth no  le salen las opcion de filtrar vistas 

0


I don't understand why a light agent cannot submit a request on the knowledge base and cc in the customer.

While the request is submitted, the cc does not come into the ticket.

Annoying.

0


Why can't a clone of light agent be a light agent but a paid license. I have created a clone of light agent and allowed it to access tickets organization wide. But, the moment I map a user to this cloned role, it consumes a paid license. Ironically, as per Zendesk, a clone of Light Agent will not be considered same as the original. Second, it is not about the permission as one can change permission of the default role for organization access. A conundrum whether to call it silly or malicious on Zendesk's part.

0


Hi Gina

Our contact page (don't want to put up my email address in case of spam) is linked below. If you fill out that form I will get it and I will be in contact. We are based in Melbourne, Australia.

https://www.gravitycx.com.au/contact

Cheers

Chad

0


Hi Chad, definitely keen to have a chat. The biggest issue we face is the store not being able to see their solved ticket as the ticket reassigns to the Head Office Customer Service agent when they solve the ticket. If we could find a solution to that, it would be a huge win!

0


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


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


Sign in to leave a comment.