Skip to content

Ideas and Feedback

Ideas and Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

55 results found

  1. There needs to be a Knowledge Management role for technicians that doesn't require full admin rights, so techs can create and edit articles and share with each other without needed access to the entire platform.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. For roles and permission: ability to create groups of technicians and then assign those groups to the customer so they can have access to the clients. As soon as you add a new technician to a group, that technician will then have access to X client. As of right now, if we create a new customer, we then need to go to each technician and give them that access. It can take a long time. A lot of our technician have a different role each.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Currently there is a permission option to view other technician ticket but there should be an additional permission (on and off) for a technician ability to close tickets that don't belong to them.
    SLA, time entry and CSAT are linked with ticket owner and tech should not have the ability to close ticket on behalf of another technician. Only team leader or Admin should have this ability. We want all our tech to view all tickets, as when a customer calls and if the tech is not available, they can provide update to client. But technician should be restricted from…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Atera should have additional billable (or free...) roles other than technicians. We have project managers & help desk admins that do not provide technical support.

    We don't use Atera's ticketing because our admin staff would cost us an extra $300/month just for them use the help desk, nothing else.

    We would love a discounted "role" of a "Help Desk Manager" who like a technician has granular access to help desk tickets per assigned client. But that's all they can do.

    We have someone that can manage tickets, assign tickets, but do not have to be a full $150/month agent since…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Permission Ticks for custom roles to be considered
    Allow A role to create a Customer
    Allow a role to remove a customer
    Allow access to all customers With exception/exclusion
    Allow to Modify or submission to Knowledgebase (with ability to restore previous version)
    Allow to create KB for internal
    Allow to create KB For Customer
    Allow to create Scripts
    Allow full admin - with customized Feature/plugin blocking

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. I gather it won’t happen everywhere but certainly happens at our end (and most companies I work with); but we employ an accounts lady who handles all purchase ledger invoicing (buying a pen, paying for the supply of gas or electricity but also for Office365 or AWS) which is mostly done via our business partners portals.
    So basically one (free of charge) account should be made available per company that strictly covers administrative duties limited to Atera subscriptions and licensing, add and remove agents’ licences, edit payment details such as credit card details, invoices, etc.

    27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Roles within Admin need to have the ability to have more control of what features each group has.
    Under RMM, the "Edit Device" feature is too strict. We want to be able to allow certain technicians to edit device names but not be able to delete them.

    Setting that can be turned off so that no technicians have the ability to delete anything.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. In case of IT support teams spread on multiple sites (e.g. Technician A has an admin role for Site A, technician B has an admin role for Site B) as a supervisor for all sites and resident on site C, I would like to be able to assign tickets (or change requests) to technicians without having to make them admins of site C.
    In summary: the ability to assign multiple roles to the same techincian or be able to differentiate ACL for each site within a single role

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Ticketing only Atera license

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Should have custom read/contribute/modify/delete access for Knowledgebase.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Separate permission to manage threshold profile

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. I do not want any Admin or technician having access to the files and folders of an end-user. So either this "File Transfer" option should be configurable under Permission-Roles or there should be granular permissions for the "Desktop Remote Manage" permission under RMM in Roles. I wouldn't mind this feature to be totally disabled as this can raise a flag in security audits or can cause a management concern where security of data is of topmost priority.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Ability to fully remove a technician, not just disable the account, to keep the user list neat and tidy.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Expanding on earlier idea would be good to have the following:
    In Role Permissions:
    Build on to Desktop Remote Management and Server Remote Management but have a new item:
    Server Remote Access - Toggle remote access on or off for Servers.

    This way we can have a tech monitoring servers and running scripts we have made but make the tech assigned to role unable to remote into servers (Think L1 or L2 tech).
    Speaking of scripts, before "Manage Scripts" have a toggle to:
    "View Scripts" - on and off so that we can assign L1 or L2 tech the ability…

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Reduced license for management to check tickets, run reports etc. I don't think its fair to charge a full license fee for a user that doesn't use most of the features

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Ability to remove "view" option for scripts for tech that are not admin - Currently when they run the script on a device, there is option to view the script. The use case for that is, if we are using API key in the script to use custom fields, we don't want to expose our API key to normal technicians.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Roles & Permissions: when limiting access to a specific customer, the technician shouldn't be able to delete or edit IT Automation Profiles/Scripts that are assigned to other customers

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Would like to have SNMP Templates Management added as an assignable role under RMM like Manage Scripts.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. We have a problem where we need to restrict admin access to just management. However when we have tried to create custom roles previously, we have to specify which customers that role has access to. On top of this, when new customers are added to the system, we have to manually edit this role to enable those new customers each time.

    There needs to be a checkbox to allow access to all customers when editing the role.

    In the meantime, we have given up on using 'roles' and have to give everyone the admin role :(

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. I think it would be good if there were separate permissions to edit the knowledge base without being a full administrator. A process description does not have to open up the possibilities in the same way as the right to extend a license.

    41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?