Settings and activity
45 results found
-
864 votes
Matt Hardwick
supported this idea
·
-
40 votesMatt Hardwick
supported this idea
·
-
162 votesMatt Hardwick
supported this idea
·
-
65 votesMatt Hardwick
supported this idea
·
-
38 votesMatt Hardwick
supported this idea
·
-
15 votesMatt Hardwick
supported this idea
·
-
23 votesMatt Hardwick
supported this idea
·
-
1,249 votesMatt Hardwick
supported this idea
·
-
14 votesMatt Hardwick
supported this idea
·
-
14 votesMatt Hardwick
supported this idea
·
-
5 votesMatt Hardwick
supported this idea
·
-
52 votesMatt Hardwick
supported this idea
·
-
38 votesMatt Hardwick
supported this idea
·
-
69 votesMatt Hardwick
supported this idea
·
-
32 votes
An error occurred while saving the comment Matt Hardwick
supported this idea
·
-
63 votes
Congratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
Matt Hardwick
supported this idea
·
-
34 votesMatt Hardwick
supported this idea
·
-
54 votes
An error occurred while saving the comment Matt Hardwick
commented
*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.
Matt Hardwick
shared this idea
·
-
88 votes
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
·
-
55 votesMatt Hardwick
supported this idea
·
I think we need to go one further and have multiple keys with the option to limit the scope per key. Want a R/W key, create one; want it limited to a specific customer, just select one customer, rather than all; need a read-only for all customers, create that and just don't tick write.