Agent Ticket Scope

Agent ticket scope is the set of access rules within a help desk that controls which tickets a support agent can see and open. It acts as a permission layer: scope determines ticket visibility by department, group, or individual assignment, separate from what an agent is allowed to do inside a ticket. Well-defined scopes prevent agents from accessing unrelated queues, protect sensitive customer data, and keep each agent’s ticket list focused on relevant work.

Scope access levels

Agent ticket scope usually falls into three access levels: global, group-level, and restricted. Global access lets an agent see every ticket in the help desk regardless of group, assignment, or department, so it is typically reserved for team leads and admins. Group-level access limits visibility to tickets in the agent’s group plus tickets assigned directly to that agent. Restricted access limits agents to only tickets explicitly assigned to them, which is useful for outsourced teams or tier-1 agents.

Scope vs. agent roles

Scope answers “which tickets can I see?” while a role answers “what can I do inside a ticket?” For example, an agent with global scope but a viewer role can see all tickets but cannot reply, add internal notes, or change ticket status. Conversely, an agent with restricted scope and a full agent role can perform ticket actions, but only on assigned tickets.

Administrators combine scope and role to build granular permission profiles. High-sensitivity departments may pair restricted scope with full-action roles, while general support queues often use group-level scope with standard agent roles. This separation is the foundation of ticket access control for support agents because visibility and actions can be managed independently.

Ready to grow your business?

Start your free trial today and see results within days.

Request demo Start free trial

Group-based view-only access

Some help desks support a view-only permission within group-level scope: agents can read tickets in a specified group but cannot reply, edit, or reassign them. This is useful for QA reviewers, team leads who monitor queue health without intervening, or cross-department observers who need context without changing ticket state. In LiveAgent, administrators can approximate this by combining department-level scope restrictions with role permissions that limit ticket actions.

Why scope varies by organization

Ticket scope requirements differ by organization size and structure. In a small team of three agents handling all inquiries, global access keeps operations simple because everyone sees everything. Larger enterprises with multiple departments, brands, or regions use restricted and group-level scopes so billing agents do not see HR tickets, and regional teams only work their own queues. LiveAgent’s Ticket Coverage Tool lets administrators verify an agent’s current visibility as teams change.

Join our newsletter

The latest tips and deals delivered straight to your inbox.

Email address

Subscribe

Security and confidentiality

By controlling access, agent ticket scope helps maintain the confidentiality of sensitive information, ensuring only authorized personnel can view or interact with certain tickets.

Efficiency and customer impact

When agent ticket scope is correctly configured, tickets are routed to the right agent on the first attempt, eliminating manual reassignments and reducing time-to-first-reply. Agents work from a focused queue of relevant tickets instead of scanning an unfiltered inbox, which speeds up resolution and reduces context-switching errors.

How to configure agent ticket scope in LiveAgent

Administrators configure scope in LiveAgent by assigning agents to departments under Configuration > Agents > Departments. An agent’s visible ticket set is the union of tickets in assigned departments. For finer control, department-level roles can further restrict whether the agent can reply, add notes, or only view tickets. The setup applies to the agent panel and mobile app.

To configure agent ticket scope in LiveAgent:

1. Open Configuration > Agents and select the agent you want to configure.
2. Go to the Departments tab and check or uncheck departments. The agent will see tickets belonging to every checked department.
3. Set the agent’s role within each department to control whether they can view tickets, reply, add notes, or perform broader ticket actions.
4. Verify the result with the Ticket Coverage Tool by checking exactly which tickets are visible to that agent.
5. Adjust department assignments as needed and re-check. Repeat for other agents or apply bulk department assignments for teams with identical scope requirements.

Agent ticket scope gives administrators a practical way to balance visibility, security, and speed. The best setup gives each agent enough access to solve assigned customer issues without exposing unrelated queues or sensitive internal information.