- or
No existing idea results
- ~ No ideas found ~
5046 results found
-
splashtop view only
When using the splashtop client it would be nice to take advantage of the view-only feature that's available in their latest version. ( https://support-splashtopbusiness.splashtop.com/hc/en-us/articles/360056900592-View-Only-Mode )
12 votes -
oauth2 - Login to atera using Microsoft 365 Account
it's very easy to integrate office 365 OAuth2 integration for logins... please do so
give us the ability to just click the microsoft or google icon at the bottom of the login page... if we are logged into an account that has the same email as a user on the system... waallllaaaaa we log in
87 votes -
Snippets for Agent and Ticket Fields
I would love to have more snippets related to default and custom fields associated with agents, tickets, users, sites, and assets. Having this information is especially useful for templating information provided by the end-user or technicians.
1 vote -
Convert a registered filter into button
Having the ability to convert a predefined filter into a button or create buttons for quick access to filters (e.g., unassigned, SLA breached, critical, etc.).
1 vote -
Software Inventory - software update function directly from report
When I check my Update Versions in the Software Inventory, I miss the Funtion to activate the Update for this Software in this List.
also nice Features:
- Report for all Devices wich not installed actual Version
- Marker for Offline Devices during creation the report
- Export Function for all version results5 votes -
Granular Remote Desktop Settings Per Customer
Dear Atera Team,
Firstly, I’d like to express our gratitude for the incredible value Atera has brought to our business. Your platform has revolutionised how we operate, driving efficiencies across our workflows and empowering us to deliver outstanding support to our customers. It’s been a game-changer for us!
As enthusiastic users of Atera, we occasionally encounter small challenges where we feel there’s an opportunity to enhance the platform even further. One such area is the management of remote desktop functionality.
We have a use case where some of our customers require us to have remote access to their devices, while others specifically request that we do not. It would be immensely beneficial if Atera offered the ability to configure remote desktop settings on a per-customer basis. Ideally, this would allow us to enable or disable the remote desktop agent (e.g., Splashtop or AnyDesk) during the customer creation stage, or as part of the initial Atera agent installation process.
While we’re aware of the registry key method to disable these agents post-installation, it’s not always feasible for environments with hundreds or even thousands of devices, particularly when some are rarely online. Attempting to retrospectively disable remote desktop in such cases can take significant time and effort, which isn’t always practical.
By introducing this functionality, Atera could not only simplify compliance with individual customer requirements but also enhance deployment efficiency and reduce the administrative overhead for teams like ours.
We’re huge fans of Atera and are passionate about supporting your journey as much as you’ve supported ours. We hope this suggestion is something that resonates with your vision for the platform, and we’d love to see it come to life!
Thank you for considering this request, and please don’t hesitate to reach out if you need further clarification or details.
Best regards,
IanDear Atera Team,
Firstly, I’d like to express our gratitude for the incredible value Atera has brought to our business. Your platform has revolutionised how we operate, driving efficiencies across our workflows and empowering us to deliver outstanding support to our customers. It’s been a game-changer for us!
As enthusiastic users of Atera, we occasionally encounter small challenges where we feel there’s an opportunity to enhance the platform even further. One such area is the management of remote desktop functionality.
We have a use case where some of our customers require us to have remote access to their devices, while…
2 votes -
Granular Splashtop / Anydesk deployment
Dear Atera Team,
Firstly, I’d like to express our gratitude for the incredible value Atera has brought to our business. Your platform has revolutionised how we operate, driving efficiencies across our workflows and empowering us to deliver outstanding support to our customers. It’s been a game-changer for us!
As enthusiastic users of Atera, we occasionally encounter small challenges where we feel there’s an opportunity to enhance the platform even further. One such area is the management of remote desktop functionality.
We have a use case where some of our customers require us to have remote access to their devices, while others specifically request that we do not. It would be immensely beneficial if Atera offered the ability to configure remote desktop settings on a per-customer basis. Ideally, this would allow us to enable or disable the remote desktop agent (e.g., Splashtop or AnyDesk) during the customer creation stage, or as part of the initial Atera agent installation process.
While we’re aware of the registry key method to disable these agents post-installation, it’s not always feasible for environments with hundreds or even thousands of devices, particularly when some are rarely online. Attempting to retrospectively disable remote desktop in such cases can take significant time and effort, which isn’t always practical.
By introducing this functionality, Atera could not only simplify compliance with individual customer requirements but also enhance deployment efficiency and reduce the administrative overhead for teams like ours.
We’re huge fans of Atera and are passionate about supporting your journey as much as you’ve supported ours. We hope this suggestion is something that resonates with your vision for the platform, and we’d love to see it come to life!
Thank you for considering this request, and please don’t hesitate to reach out if you need further clarification or details.
Dear Atera Team,
Firstly, I’d like to express our gratitude for the incredible value Atera has brought to our business. Your platform has revolutionised how we operate, driving efficiencies across our workflows and empowering us to deliver outstanding support to our customers. It’s been a game-changer for us!
As enthusiastic users of Atera, we occasionally encounter small challenges where we feel there’s an opportunity to enhance the platform even further. One such area is the management of remote desktop functionality.
We have a use case where some of our customers require us to have remote access to their devices, while…
2 votes -
Alerts for new software installation
I would like to have a feature, wherein if any users install software without informing IT support, alert is generated and send to admin.
This is required since we observed some software's like Adobe can be installed even without administrator rights.
33 votes -
Enhanced Domain Name and Credential Management for Network Discovery
Seeking improvements to the Network Discovery feature to better accommodate various authentication scenarios.
Key Requests:
Custom Domain Name Input: Allow users to manually enter or modify the short domain name used for remote authentication during network scans. This would enable better compatibility with systems where the default domain retrieved by the scanning agent does not align with the required authentication domain.
Credential Flexibility for Non-Domain Environments: Introduce functionality that allows the entry of local admin credentials when performing remote installations on non-domain joined computers. This would enhance usability in workgroup environments where standard local accounts are used.
Support for Multiple UPN Suffixes: Enhance the system to recognize and accommodate multiple User Principal Name (UPN) suffixes. This will streamline the login process for users managing multiple client environments.
Benefit:
Implementing these features would significantly improve the user experience, particularly for those working with diverse network configurations and authentication requirements.Seeking improvements to the Network Discovery feature to better accommodate various authentication scenarios.
Key Requests:
Custom Domain Name Input: Allow users to manually enter or modify the short domain name used for remote authentication during network scans. This would enable better compatibility with systems where the default domain retrieved by the scanning agent does not align with the required authentication domain.
Credential Flexibility for Non-Domain Environments: Introduce functionality that allows the entry of local admin credentials when performing remote installations on non-domain joined computers. This would enhance usability in workgroup environments where standard local accounts are used.
Support for Multiple…
4 votes -
custom fields tickets
Allow Custom Fields in Tickets that only apply for certain customers. Thank you.
2 votes -
one place for customer portal options
All options for the portal should be under one admin section. At the moment the default options for tickets seen and other items are under "Account Settings" I feel all customer portal options should be under "Customer Portal" including customisable options.
10 votes -
Filtering for devices by Disk Type
Filtering for devices by Disk Type doesn't seem to be an option - We can sort by size, free space, model, bitlocker status, but not by disk type.
We still have some spinning rust and are upgrading them as we find them. I would LOVE to filter out the device list by systems that need an upgrade.
1 vote -
workhours
Pls. enhance the API to retrieve a list of all workhourrecords of a month (or filtered by start / end date).
Currently we must iterate through all tickets to retrieve the workhourrecords.2 votes -
workhours
Pls. enhance the API so one can access all workhourrecords filtered by date.
Currently, we must iterate through all the tickets to get the workhourrecords.2 votes -
Auto Tag depending on installesd Server role
Automatically assign tags based on server roles so that it is possible to control update times based on tags.
For example, Hyper-V servers receive the tag “Hyper-V” DHCP servers receive the tag “DHCP” etc.1 vote -
Add Auto Tag based on installed Server role.
Tags bassiert auf Serverrole automatisiert zuordnern. damit es möglicht ist update Zeite basierent auf Tags zu stuern.
zum beispiel Hyper-V Server erhalten Tag "Hyper-V" DHCP Server erhalten Tag "DHCP" usw.1 vote -
Splashtop SOS
For new customers / users I currently still use Teamviewer Quicksupport to remotely install the Atera agent and then swap to Splashtop.
As my Teamviewer subscription will soon expire, it would've been nice Splashtop SOS was actually included in the Atera subscription the same way that Teamviewer Quicksupport is with Teamviewer Premium/Corporate/Enterprise instead of having to pay for a separate Splashtop subscription again.
Or I could use Microsoft Quick Assist, but still I'd rather prefer to also use Splashtop SOS for quick support sessions.I'm pretty sure Atera can fulfill this dream ;-)
223 votesCongratulations 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!
-
API Expanding
Folder management :
Get Folders <Customer> doesn't exist
Post ( rename ) <Customer>, <folder> doesn't exist
Create New folder ( doesn't catch duplicate folder names )2 votes -
Atera Accounts
There are partners who utilize ATERA for both internal and/or external purposes, with their accounts fully configured and populated with devices, automation policies, and other settings.
Recently, a partner requested the ability to merge or move their ATERA account under ours, treating them as a customer.
Why this capability would be beneficial for partners:
Simplified Billing and Management:
Partners could consolidate their accounts under a central management system, simplifying billing processes and enabling efficient oversight.
Streamlined Support and Services:By operating under a single reseller or partner account, customers can benefit from centralized technical support, unified policies, and seamless service delivery.
Enhanced Collaboration:Partners operating as customers could access shared resources and advanced configurations, enabling faster deployment of solutions and consistency across services.
Scalability and Customization:This setup would allow partners to scale their operations easily while maintaining their individual settings and customizations under the primary reseller account.
This capability could create a stronger ecosystem within ATERA, fostering collaboration and efficiency for partners who need such flexibility.There are partners who utilize ATERA for both internal and/or external purposes, with their accounts fully configured and populated with devices, automation policies, and other settings.
Recently, a partner requested the ability to merge or move their ATERA account under ours, treating them as a customer.
Why this capability would be beneficial for partners:
Simplified Billing and Management:
Partners could consolidate their accounts under a central management system, simplifying billing processes and enabling efficient oversight.
Streamlined Support and Services:By operating under a single reseller or partner account, customers can benefit from centralized technical support, unified policies, and seamless service…
2 votes -
Alert on system desync with assigned tech when changing
We frequently have new tickets come in where one of us takes the ticket and then the next tech assigns themselves very shortly afterwards, as they see it as unassigned still.
There should be a way for the system to notice the tech sees it as unassigned but the backend system is changing it from a user to another user and trigger an alert or stop the action.This causes an issue with when the first tech to grab the ticket has it disappear from their queue and it ends up in the other tech's queue instead. THis is particularly disruptive to our workflow and ability to effectively service our clients
We frequently have new tickets come in where one of us takes the ticket and then the next tech assigns themselves very shortly afterwards, as they see it as unassigned still.
There should be a way for the system to notice the tech sees it as unassigned but the backend system is changing it from a user to another user and trigger an alert or stop the action.This causes an issue with when the first tech to grab the ticket has it disappear from their queue and it ends up in the other tech's queue instead. THis is particularly…
3 votes
- Don't see your idea?