A user who is set as an admin of Deparment A is able to change their assigned department to Master department and access devices from other Departments too
Can this behaviour be prevented?
Hi Nikhil,
This decision was made assuming that admin is a responsible user irrespective of the department . Although an admin who is part of Department A with a scope , will not be able to view devices of other departments , unless he is part of a department with no scope [ which kind of means no filter] .
Thanks,
Prashanth
Hi Prashanth
Thanks for the prompt clarification.
Although an
adminwho is part of Department A with a scope , will not be able to view devices of other departments, unless he is part of a department with no scope
Understood
This decision was made assuming that
adminis a responsible user irrespective of the department
Even if we were internally we are okay with admins being able to shift departments, the modus operandi of our operations requires us to have certain controls in place. Hence the request, will it be possible to restrict the admins’ ability to change their own departments, and give that permission only to an Admin of the Master Department (i.e. a super-admin)?
Alternatively, will it be possible to give some of the permissions associated with an Admin account to an Operator account, like uploading of artifacts in the “OTA Upgrade” section, and viewing the “Deployment” tab in a device? Currently, an operator gets the following error when they try to access the Deployments in a devices:
Hi @nikhil,
- We currently do not support a super-admin being able to control a bunch of admins . We dont have that kind of hierarchy in place . It would not be possible to achieve something like that.
- You’re right , we’ve now allowed
artifact uploadto [adminandoperator] andviewing of deploymentstoall roles. This will be available in release2.49.xonwards