No Matches Found!
Try with a different search term
We have users assigned the Mobi Technicians role as we don't want them to have full Admin rights to the Console. Since we have moved to Mobi Control Cloud and assigned this permission, those users are not able to via Profiles. I contacted support and they said we have to open each profile and edit the permissions and add Mobi Technicians. We have hundreds of profiles as we use them for email etc. is there a work around for this besides making them admins?
Thanks
Sue
this only goes for 2025.1.X which i guess very less customers are using yet
So, in my opinion you have 3 options:
Beyond Profile Permissions they all will likely need Package permission granted. The Packages will only be visible to who uploaded them and the Administrator role by default. You'd need to add that Technician role to every single Package I believe.
HI Sue,
The default permissions granted for "MobiControl Technicians" template are rather restricted, mainly for viewing non-critical info/policies and managing less sensitive items such as packages. I personally consider it to be too restrictive and seldom recommend my customers to use such template nor to modify the permissions settings in such template. Instead, new customized "restricted administrator" role is usually created with very critical/sensitive "Manage" permissions (e.g. users/permissions, root certificates, root group, library path, absolute path, and many items available in the global-settings tab in the web-console ) disabled for junior or new-hired administrators. The new role can also be configured to have different/no permissions in different device root-group(s)/sub-groups to facilitate division-of-labour between different restricted administrators for handling different set of devices within the same organization.
So, in your case, the fastest solution would similarly be creating a new custom role/group with your required permission(s) such as managing profiles, and then assigning all your previously created/new user(s) to have such newly added role/in the new group having the new role to handle new profiles created in the future. Already created profiles, unfortunately, have to be reconfigured either manually or programmatically with REST API. However, if your approach of using hundreds of profiles for email can somehow be reduced to a single/handful of new profiles by optimally using standard and/or custom attribute macro(s), then there is no need to worry about reconfiguring the old profiles.
Hi Sue,
Thank you for posting on SOTI Pulse, and a big thanks to Remy, Rafael, Matt, and Raymond for their valuable input—their expertise and willingness to help are greatly appreciated!
Have you had a chance to test the solutions suggested by Remy, Raymond, and Rafael? Were they able to resolve your issue?
If not, or if you have any further questions or concerns, please don’t hesitate to reach out. We're here to support you every step of the way.
Regards,
