Agent permissions
Add permissions so that agent couldnt ban / ignore the user. And that the "Admins" could sellect the permissions for them :)
Ideas from comments:
- Option to choose if Agent should get offline messages or not;
- Option for unbanning people by agents;
- Who can only see reports for a particular website;
- Who can and can't see the analytics;
- Who can whisper;
- Who can edit global shortcuts;
- Disable "+Add" property;
- Forbid users to rename/create aliases;
- Another agent shouldn't see other agent conversations;
- Select countries to which agent is restricted to answer chat from;
- Restrict agent to certain languages;
- Agents that didn't create or assigned to a ticket shouldn't be allowed to delete a ticket;
- Option to hide chats: agents belonging to different departments should have access to there department chats only;
- Restrict agents from deleting conversations.
Pluss/YBOT Support
shared this idea
Hi there dear tawker,
We are currently planning on developing granular permissions that will solve this problem.
Hope this will be solved in the near future.
-
Daniel
commented
We use Tawk in our company.
Congratulations, it's the best of all we know so far.
It would be interesting that an agent had no access to the chat of another agent, unless the chat was transferred from one agent to another agent, or invited to join the chat.
Thank you. -
Thom
commented
I would like for admins to be able to logout agents. I have my widget set to not display when no agent is online. If an agent leaves for the day and forgets to logout, the widget still appears. Would like to be able to logout agents or better yet, have the API allow logout all agents. That way we could have a button on our admin site to logout everyone.
-
Max
commented
If your Pre-Ticket form asks for an email, an admin can make it so agents can't see the customers email.
-
Vikas Bare
commented
Add setting in manage agents 'Show Site & Pages' to Agents. This will help Admin to restrict agent from creating new sites and pages setup.
-
Ross
commented
A regular agent can view older chats in the History section. When an older chat is opened up by that agent, a bunch of icons appear at the top of the pop-up window that displays the older chat. One icon is a trash icon.
When the trash icon is clicked it asks if the agent wants to delete that specific chat. If they say yes, nothing happens (as it should).
I would prefer a regular agent not even be able to see the trash button. -
Max
commented
It will be good is agent can see only his own chats.
-
Pablo brierley
commented
an specific agent can see only a part of the site, like some agents for sales some for productions or administration, when you add the code in the footer or header of a wordpress or osclass sites....
-
TS
commented
What?
-
Tom
commented
Invite new agents as agents not admin. Regular agents cannot delete chat history but admins can.
-
Anonymous
commented
I had instances where my agents delete chat history because they sometimes speak rudely to my customers.
As a result I am loosing customers which is key to any business
-
Z
commented
I think under managing agents, the admin should have the ability to restrict agents from viewing all chat history. Ideally, an admin would decide if an agent should have access to chat history. Additionally the admin would be able to make a specific chat unavailable to one or more agents in the history.
Extended feature: This could be done by date range. So that if a new agent is created, they would not necessarily be able to see the lifetime history of chats. :)
-
TheSecondFarm
commented
Create a new rule (manager) that will be able to add more stuffs or take of stuffs from sistem
-
Mario Latif
commented
Agent permissions are same as Admin , and they can edit thier role to Admin.
-
Anonymous
commented
Add permissions so that an agent cannot impersonate another user / Restrict user to only chat page (make dashboard disabled for agents)