Settings and activity
49 results found
-
45 votes
An error occurred while saving the comment 
Matt Hardwick
shared this idea
·
-
85 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment Matt Hardwick
commented
Agreed, this should be a staple - competitors, even if the agent per se isn't branded put it in a branded folder/installer name makes it clear what it is and where it is from.
Matt Hardwick
supported this idea
·
-
51 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Matt Hardwick
supported this idea
·
-
4 votesMatt Hardwick
supported this idea
·
-
16 votesMatt Hardwick
supported this idea
·
-
48 votes
Nice! The feature you requested is being
reviewed by our product team. We
’
ll keep an
eye on the number of votes, and let you know if
a decision is reached to implement. Thank you
for being a partner in our process!
Matt Hardwick
supported this idea
·
-
2 votesMatt Hardwick
shared this idea
·
-
35 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Matt Hardwick
supported this idea
·
-
924 votesMatt Hardwick
supported this idea
·
*We need the option to create per app/per customer API keys.*
There are talks here of having separate read/write API keys but it needs to go one further. We need the option to create multiple keys and define the scope, limiting the features available and/or per customer. Currently keys are transferred in the to customer devices when used in a script, and thus pose a security risk.