Settings and activity
23 results found
-
1 vote
Ben Courtade
shared this idea
·
-
5 votes
An error occurred while saving the comment Ben Courtade
supported this idea
·
-
13 votesBen Courtade
supported this idea
·
-
22 votesBen Courtade
supported this idea
·
-
68 votes
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
Best regards,
The Atera Team
Ben Courtade
supported this idea
·
-
4 votesBen Courtade
supported this idea
·
-
2 votesBen Courtade
supported this idea
·
-
4 votesBen Courtade
supported this idea
·
-
5 votesBen Courtade
supported this idea
·
-
9 votesBen Courtade
supported this idea
·
-
124 votes
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
[For major features only–] You can also follow this in our Pubic Roadmap.
Best regards,
The Atera Team
An error occurred while saving the comment Ben Courtade
commented
I would like to propose another type of variable for scripts that is more secure, for things like API keys.
There could be a secrets manager area with names for each secret, for example, "atera-api-key". Then the script could have something like {[secret=atera-api-key]}.
This would help us automate scripts that have sensitive information and ensure those keys aren't saved in plain text within the script.
Ben Courtade
supported this idea
·
-
39 votesBen Courtade
supported this idea
·
-
40 votesBen Courtade
supported this idea
·
-
11 votesBen Courtade
supported this idea
·
-
32 votesBen Courtade
supported this idea
·
-
14 votesBen Courtade
supported this idea
·
-
10 votesBen Courtade
supported this idea
·
-
24 votesBen Courtade
supported this idea
·
An error occurred while saving the comment Ben Courtade
commented
Agreed. We are including instructions to click the forgot password link once they reach the portal to set their own password. Emailing passwords is against our internal policies and isn't a good security practice in general.
It would be usable if it required a change on the first logon, but really we should have a variable available in the email template to include a direct link to set an initial password.
-
22 votesBen Courtade
supported this idea
·
-
2 votesBen Courtade
shared this idea
·
I'd very much like to see this implemented. Currently we can scope view and run permissions to a category. But script creation and editing are global. I'd like to be able to allow certain users to create and edit scripts in certain categories, but I definitely don't want them to edit scripts that are being applied outside their scope.