When you create a new agent or edit an existing one in Freshdesk, you have to define their role as well as the scope of tickets that they're allowed to see. To be clear, Ticket Scope and Agent Roles are two different things in Freshdesk, but they can be used together to achieve want you want in terms of access control and permissions.
Agent Role defines the kind of activities an agent is allowed to do in your helpdesk. This covers activities such as replying to tickets, adding notes and so on, but doesn't define the tickets that they'd be allowed to perform these activities on.
Note: It is mandatory to associate an agent with a role while creating a new agent in your helpdesk.
Ticket Scope, meanwhile, defines the level of access an agent has with respect to tickets in your helpdesk. You can choose between three levels of Scope: (a) Global, (b) Group-Level, and (c) Restricted.
Agents with Global Access can view all tickets across your helpdesk. Agents with Group and Restricted Access though, can only view tickets that have been assigned to them or a Group they belong to.
Please note that the Scope only controls what agents can view, not what they do - that is what the Roles are for. For example, you can assign roles to the agent to define whether they can reply to a ticket or forward a conversation, and then set their scope to specify which tickets they can actually view.
That means you can set the scope of an agent to just view tickets assigned to them, but give them complete control over all your configurations and setup. Or you can even create an agent with Global Access, allowing them to view everything coming into your support, but if you tighten the noose on their Roles, all they can do is add a private note to the ticket.
When you create a new agent or edit an existing one in Freshdesk, you have to define the scope of tickets that this agent should be allowed to see, and what role(s) they should be playing in your support desk. To be clear, Ticket Scope and Agent Roles are two different things in Freshdesk, but they can be used together to achieve want you want in terms of access control and permissions.
Agent Role - defines the kind of activities an agent is allowed to do in your helpdesk. This covers things like whether somebody is allowed to reply to tickets, add notes etc., but doesn't talk about which ticket exactly.
Note: It is mandatory to associate an agent with a role while creating a new agent in your helpdesk.
Ticket Scope - defines the level of access an agent has with respect to tickets in your helpdesk. You can choose between three levels of Scope: (a) Global, (b) Group-Level, and (c) Restricted.
Agents with Global Access can view all tickets across your helpdesk. Agents with Group and Restricted Access though, can only view tickets that have been assigned to a Group they belong to, or themselves respectively.
Please note that the Scope only controls what agents can view, not what they do. The do part is what the Roles are for. For example, you can assign roles to the agent to define whether they can reply to a ticket, or forward a conversation, and then set their scope to specify which tickets they can actually view.
That means you can set the scope of an agent to just view tickets assigned to them, but give them complete control over all your configurations and setup. Or you can even create an agent with Global Access, allowing them to view everything coming into your support, but if you tighten the noose on their Roles, all they can do is add a private note to the ticket.