Settings and activity
40 results found
-
5 votes
D 1 shared this idea ·
-
6 votes
D 1 shared this idea ·
-
38 votes
D 1 supported this idea ·
-
9 votes
D 1 supported this idea ·
-
23 votes
D 1 supported this idea ·
-
8 votes
D 1 supported this idea ·
-
8 votes
D 1 supported this idea ·
-
7 votes
D 1 supported this idea ·
-
42 votes
D 1 supported this idea ·
-
23 votes
D 1 supported this idea ·
-
29 votes
Hi,
Great news! Your idea has been approved and is planned for implementation, however this will require a longer duration than Q3 '25.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
You can also follow this in our Pubic Roadmap - API endpoint - get asset.
Best regards,
The Atera Team
D 1 supported this idea ·
-
17 votes
D 1 supported this idea ·
-
26 votes
D 1 supported this idea ·
-
14 votes
D 1 supported this idea ·
-
42 votes
D 1 supported this idea ·
-
14 votes
D 1 supported this idea ·
-
24 votes
D 1 supported this idea ·
-
32 votes
D 1 supported this idea ·
-
54 votes
An error occurred while saving the comment D 1 supported this idea ·
-
15 votes
D 1 supported this idea ·
Also of concern is that there are no permissions that can be set for the API Key and expiry dates of API keys.
If multiple API Keys are able to be created, then permissions/roles of those API Keys would be good to have.
For example...a API Key could be configured to only have read access to Assets, but not Tickets.