View's in MSP Backup are powerful, my idea is that a SuperUser can share Views for other team members
Currently the object (Create AD User) does not include
First and Last
The office365 create user has all of this and it would be useful if the create ad user object had the same information in order to create AD accounts that are not synced to Office 365.
We have the following situation: Our support technicians have access to most of our customers, but not all - e.g. some customers who quit their contract but are still in N-Central. No technician should see them, edit them or get alarms from them. We allow our technicians in N-Central 11.1 the access via an Access-Group, but obviously NOT with the SO-Level because not all of the customers should be seen. The following ...more »
There should be a check box that enables an "on leave" or "on holiday" mode for a user that redirects tickets to that user's backup user during that time. There should be an option for each user to select a user that is their backup for if the are on leave.
Similarly, when disabling a user, there should be an option to reassign their tickets and customers to another user.
Would like to add an easy way to notify via broadcast to clients (Not Email), for things like security issues, outages, and scheduled events. We would like to maintain an active alert until it is cleared by the N-Central Tech or N-Central administrator. Once cleared, the message will no longer list and no longer alert. A history of alerts are viewable in n-Central for Administrators and Techs. Must be able to push ...more »
Would like an status of who is logged in to n-central and provide chat access to those user.
If a customer is online to n-central, they can chat with only assigned level partner.
Allow managers/administrators to see in real time what each users is accessing at that time.
we would consider it a good idea to be able to specify an alternative user for restore so you could restore data to network shares with authentication.
Since you can do this while backing up already, we also need this for restore purposes.
There should be a way to filter Users when they attempt to register from the Front End User Registration page. Possibly by only allowing Users to register with Email Domain Names associated with Customers. This could prevent unwanted spam.
When a new user(s) registers from the Front End registration page I think there should be an option to automatically assign them to their associated Customer entry based upon their Email Domain Name they registered with.
While it's good that you offer two factor authentication, it would also be useful if you would include the origination IP address (and any other info) in the Audit Report - User Login Failed.
PLEASE VOTE FOR THIS IDEA!!!
We need ability to create Client Groups for user access by specifying All Clients except clients in the exclusion list. So, user would automatically have access to all new clients added, but would not have access to the specified exclusion list.