Settings and activity
21 results found
-
99 votes
Michael Jimenez
supported this idea
·
-
448 votesMichael Jimenez
supported this idea
·
-
919 votesMichael Jimenez
supported this idea
·
-
127 votes
An error occurred while saving the comment Michael Jimenez
supported this idea
·
-
35 votes
An error occurred while saving the comment Michael Jimenez
commented
I have requested more granular permissions many times. It is critical that we be able to manage what technicians are capable of doing.
Michael Jimenez
supported this idea
·
-
9 votesMichael Jimenez
shared this idea
·
-
13 votesMichael Jimenez
supported this idea
·
-
23 votesMichael Jimenez
supported this idea
·
-
35 votesMichael Jimenez
supported this idea
·
-
4 votesMichael Jimenez
shared this idea
·
-
6 votesMichael Jimenez
supported this idea
·
-
6 votesMichael Jimenez
shared this idea
·
-
12 votes
-
129 votes
An error occurred while saving the comment Michael Jimenez
commented
This has probably been said, but we need the ability for non-admins to be able to create and update quick response templates. It's silly that you have to be an admin in order to do some of the most basic tasks.
-
6 votesMichael Jimenez
shared this idea
·
-
22 votesMichael Jimenez
supported this idea
·
-
840 votes
-
294 votes
-
341 votes
-
2,289 votes
I understand there are reasons why the account may not be able to be completely removed from the system. Maintaining a historical record of who solved a problem is important.
Perhaps we could just get a separate tab for "Deleted Techs" that keeps the active techs page clean and let's us validate that the tech no longer can access the system, but allows the historical record to remain active?
"Disabled" can still be used to temporarily lock a tech out, but we should be able to designate that the tech is no longer with our company and have a bucket for that.