- or
No existing idea results
- ~ No ideas found ~
4693 results found
-
Zapier new trigger-based on Entry of a new time entry to a ticket
Zapier new trigger-based on Entry of a new time entry to a ticket
1 vote -
Export tickets to pdf
the objective would be to be able to export a summary of the intervention in PDF in order to keep a paper trail signed by the client
16 votes -
Include Device Identifier in OTP Approval Emails
I’d like to request an enhancement to the OTP approval workflow for agent installation.
Currently, when a user attempts to install the Atera agent and is prompted for an OTP (which happens often because we have several clients in foreign countries with spotty internet), an email with the OTP code is sent to all agents. However, the email does not include any information identifying which device or user triggered the request.
In onboarding scenarios (for example, setting up 25 new users), multiple OTP prompts can occur at once, resulting in several emails with different OTP codes and no way to know which code belongs to which user. This creates confusion and slows down the onboarding process.
It would be extremely helpful if the OTP email included one or more of the following:
Device hostname and/or username
Public IP address
Any other unique identifier that ties the OTP request to a specific device or user
This additional context would allow us to quickly match each OTP to the correct user and streamline large-scale deployments.
Thank you for considering this improvement!
I’d like to request an enhancement to the OTP approval workflow for agent installation.
Currently, when a user attempts to install the Atera agent and is prompted for an OTP (which happens often because we have several clients in foreign countries with spotty internet), an email with the OTP code is sent to all agents. However, the email does not include any information identifying which device or user triggered the request.
In onboarding scenarios (for example, setting up 25 new users), multiple OTP prompts can occur at once, resulting in several emails with different OTP codes and no way to…
1 vote -
Free Dashboard Account
Add the ability to login to a dashboard account for media walls in offices etc so the whole room can view the core dashboard data continuously.
It's V expensive to pay for an account in full for this option when all we need is the dashboard showing on a big screen for visibility.
953 votes -
Access to KB’s from mobile app!
Provide access to KB articles from mobile app
11 votes -
There needs to be a way to delete the connection used for syncing customer contacts.
I moved a client to a new tenant. the old connection information is no longer valid but there is no way to remove it. the result is an error when trying to sync the customers
1 vote -
Postpone Software Updates
A Software Patch/Update Approval Process similar to the OS Patch Approval, but for software managed and updated by chocolatey or similar.
1 vote -
ticket timer auto stop
issue:
Tickets that get clicked on get a timer started (good feature). When we click out of the ticket of when there is a response given, the ticket timer should stop (requires manual pause). 99% of the time no one is going to pause the time.Feature required:
Auto pause the ticket timer after there is a response added to the ticket or if you happen to click on another section of Atera.6 votes -
Profil de seuil : délai d'exécution au démarrage
Suggestion d'amélioration – Profil de seuil : délai d'exécution au démarrage
Il serait très utile de pouvoir définir un délai d'exécution pour certains éléments du profil de seuil, notamment ceux liés à la vérification de services Windows. Par exemple, permettre de lancer la vérification d’un service 2 minutes après le démarrage du système permettrait de réduire significativement les fausses alertes générées avant que tous les services aient eu le temps de se stabiliser.1 vote -
Add Patching Status to the Public API for Dashboard Integration
We’d like the patching status to be exposed via the API (e.g., per asset/group with timestamps and current state). This would allow seamless integration with external dashboards and monitoring tools, enabling centralized visibility, trend analysis, and alerting without manual exports.
2 votes -
Please simplify the login process
When logging in, here's what I have to do
- Go to https://app.atera.com/auth0.html ("Login" button, top right, atera.com)
- Enter my email address, click "continue"
- A password field appears. Enter my password.
- I get a prompt to "Use fingerprint or face recognition" (which never works, it says "Something went wrong")
- I click "Try another method"
- I then click "Google Authentication or similar"
- On the following page a OTP field appears for my rolling code
Only after all this can I log in and get to working.
Now this wouldn't be so much of an issue if Atera didn't keep logging me out every fwe. I find myself going through this process multiple times a day.
I believe this might be some sort of concurrent-login protection DRM that is triggering me to get signed out all the time - I have 4 total computers I work from -- my laptop, my jumpbox virtual machine, my desktop at home and a desktop computer in the office, plus my iPhone where I have the app installed.
At the very least, steps 2/3/4 and steps 5/6/7 could be all rolled into two separate steps perhaps.
Plus the login process for the iOS app is similarly convoluted and just as forgetful of my credentials as the web!
Please, can something be done to resolve this?! I did actually speak to chat about it but I have a VERY
When logging in, here's what I have to do
- Go to https://app.atera.com/auth0.html ("Login" button, top right, atera.com)
- Enter my email address, click "continue"
- A password field appears. Enter my password.
- I get a prompt to "Use fingerprint or face recognition" (which never works, it says "Something went wrong")
- I click "Try another method"
- I then click "Google Authentication or similar"
- On the following page a OTP field appears for my rolling code
Only after all this can I log in and get to working.
Now this wouldn't be so much of an issue if Atera didn't keep logging me out…
68 votes -
Portal / Form Ticket Template - Improvements (consolidated)
Proper Template based form -
a pop up or separate ticket form where you organize the boxes like a proper form. Example - New User form. You could organize the boxes any where you want on the form in a logical flow
The questions and then answers in the ticket running down the side is very inefficient. Also, I would like to see all the results in the ticket, not on the side. or in the original FORM type format inside the ticket or in a pop-up or separate screen.,Checkbox or Dropdown - Multiple choice checkboxes or dropdown. I can do most of the forms that I need without multiple selections. This would be SUPER helpful.
Core fields flexibiltiy -
Ability to remove some of the core ticket fields. They are not necessary and just clutter the ticket template. Product category, etc. They will also just confuse the end user.Default field value -
Ability to set a default value for a field, date, Department, etc. That way you could have different variations of a single form that is pre-filled with a lot of the appropriate informationSave prefilled templates -
Ability to store a prefilled template per user so if they create a template they can reuse it. Maybe they could also go into the main store for sharing with othersClick to move
Click anywhere on the custom field to add it to the form. I hate having to click the tiny plus to move it overShow Fields
Option to have fields show on new template, service portal or create ticket in admin portal. ALL of these options show up in the admin portal when creating a ticket. If i set them to mandatory for the template they also become mandatory for the admin portal ticket. Why would this be a good idea? It makes a huge mess.
Proper Template based form -
a pop up or separate ticket form where you organize the boxes like a proper form. Example - New User form. You could organize the boxes any where you want on the form in a logical flow
The questions and then answers in the ticket running down the side is very inefficient. Also, I would like to see all the results in the ticket, not on the side. or in the original FORM type format inside the ticket or in a pop-up or separate screen.,Checkbox or Dropdown - Multiple choice checkboxes or dropdown. I…
39 votes -
Additional monitoring for IP/Domain/MX/DNS
Website IP/Domain Name monitoring
MX record and DNS record monitoring4 votes -
OKTA
GEO location violation (Impossible Travel)... VIP account lockout... Breached Credentials Detection... Suspicious Activity... Admin Activity Anomaly alert... Change to critical policy... Super Admin Role Changes... API Token Creation/Revocation... OKTA Service Interruptions/Degradation...
These are some of the items that would be ideal to notify or auto-ticket created.
3 votesHi,
Thank you for your valuable suggestion. While we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
We continuously review user feedback to inform our development priorities, so your idea remains on our radar.
Best regards,
The Atera Team
-
Asset Depreciation Tracking Based on Cost and Year Usage
Description: Add a native feature to calculate and track depreciation of IT assets based on purchase cost and age. Admins should be able to set depreciation method (e.g., straight-line), useful life, and view current book value. Include exportable reports for finance and budgeting purposes.
Use Case: Supports financial planning and asset replacement strategies by providing real-time depreciation data.
2 votes -
Device Check-In/Check-Out Workflow for Loaner Management
Description: Introduce a check-in/check-out status system for devices, distinguishing between permanently assigned assets and temporary loaners. Admins should be able to mark devices as “Checked Out” with user details and expected return date, and “Checked In” when returned. Include reporting capabilities for tracking overdue returns and usage frequency.
Use Case: Streamlines loaner device management and reduces loss or misplacement of shared assets.
2 votes -
Able to deploy patches from mobile app
Would be nice to be able to do patching form the mobile device app when you are on the go or need to patch a software but don't have access to a laptop etc.
11 votes -
Domain Expiration Tracking
I am looking at my Hudu and wondering if I really need it. I use it for knowledgebase for instructional procedures and tasks. As I work in Atera, I can use the knowledgebase for the same purpose. For tasks, I can create scheduled tickets. The only thing that Hudu has that Atera does not is the Expirations feature. You enter the client domain and it automatically looks at the domain records and ssl, and tracks when they expire. You can also set an alert to remind you 30 days, 7 days, etc.
17 votes -
Manually retire device
Give a tech the ability to manually retire a device instead of waiting on a pre-configured time to pass. Right now the only way to flag a device as retired is to ignore it until the allotted amount of time has passed for the system to change the status.
21 votes -
Patch Management (New) - save a view or filters
Patch Management (New) - save a view or filters
It would be nice to save views that we have filtered in the new Patch Management section of the Atera Portal. It is causing a lot frustration Atera resets the filters I am using. especially hard when I have do my monthly IT Reports.5 votes
- Don't see your idea?