Settings and activity
21 results found
-
4 votes
Ben Ahlquist
shared this idea
·
-
4 votesBen Ahlquist
shared this idea
·
-
573 votesBen Ahlquist
supported this idea
·
-
4 votesBen Ahlquist
shared this idea
·
-
7 votes
An error occurred while saving the comment Ben Ahlquist
supported this idea
·
-
161 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment Ben Ahlquist
commented
Any updates on this request? We have about 1/3 of our users that routinely use multiple devices. We currently only are able to set their primary device as the Related Agent, but it would sure be nice to associate multiple devices/agents with one user.
Ben Ahlquist
supported this idea
·
-
8 votesBen Ahlquist
supported this idea
·
-
5 votesBen Ahlquist
supported this idea
·
-
7 votesBen Ahlquist
supported this idea
·
-
2 votesBen Ahlquist
shared this idea
·
-
3 votesBen Ahlquist
shared this idea
·
-
12 votesBen Ahlquist
supported this idea
·
-
679 votesBen Ahlquist
supported this idea
·
-
1,532 votes
Congratulations 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!
Ben Ahlquist
supported this idea
·
-
634 votes
Congratulations 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!
Ben Ahlquist
supported this idea
·
-
26 votes
An error occurred while saving the comment Ben Ahlquist
commented
It seems the only time the welcome email sends is when a user is manually created. We intend to use Azure AD sync (once it's working (https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/47085382-azure-ad-group-sync-query-group-name-to-get-aroun) and CSV import (in the meantime) to provision ALL of our users.
It would certainly be nice to have this email fire during both import functions - really, any time a user is created regardless of method, this email should fire.
Someone spent a lot of time building in the capability of the welcome email in the first place, only to have it designed to work for what I bet is the least-used scenario of user creation.
Ben Ahlquist
supported this idea
·
-
5 votes
An error occurred while saving the comment Ben Ahlquist
commented
This would be very useful!
Ben Ahlquist
supported this idea
·
-
21 votes
An error occurred while saving the comment Ben Ahlquist
commented
This would be very useful!
Ben Ahlquist
supported this idea
·
-
4 votesBen Ahlquist
shared this idea
·
-
3 votes
An error occurred while saving the comment Ben Ahlquist
commented
I'm trying to provision our ~325 users via CSV import today and zero emails are firing in my testing. Add the same users manually in Atera and the emails come through without issue. I've got a support ticket open for this as well. It would sure be nice if this worked.
There's no way I'm manually adding them just so they can get a welcome email. This really needs to be fixed.
Ben Ahlquist
supported this idea
·
IMO the agent on the ticket itself should remain static - as that ticket likely applied to that specific agent. I didn't realize the agent field would dynamically change when a user's profile is updated with a new agent (for instance, in an equipment refresh). And, I didn't realize the User's Related Agent field would change when I change the "Device" field on the ticket.
We reuse and repurpose our equipment and it would sure be nice for the ticket history to follow the equipment/device/agent. We also have users who use multiple devices (also see here: https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44068440-assign-a-contact-to-multiple-agents-and-or-assign) - a ticket they send in might apply to any one of those devices they "own".