Optionally allow webhooks to be configured to pass authorization headers, API Keys, as to add an additional layer of security verify authenticity of API calls from SimpleMDM to external services.

WARNING tells me something. Doesn't tell me where to go to fix it. Thx

I would like to remotely wipe an Apple TV like I can on JAMF.

Webclips have to share the name of the profile, our company has a specific naming convention for profiles and sometimes our webclips need to be named differently.

Linked in some ways to this request https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/37168075-add-more-granular-simplemdm-user-roles… (and yes, please more granular permissions!)

Would it be possible to restrict access to devices in MDM based on some kind of tagging?

So I can tag devices as “Kiosk” and grant helpdesk full admin access over those devices, but they won’t be able to see or modify devices tagged “user laptop” for example.

At the moment we achieve this using two separate SimpleMDM tenants, which works - but makes our plans to use auto-assignment of devices from Apple Business manager more challenging…

Provide Swagger Documentation for the API
A la https://swagger.io/docs/

LockPrimaryAccountInfo and put use of the saml login name
from:
https://developer.apple.com/documentation/devicemanagement/accountconfigurationcommand/command

and if possible collect the users full name from the saml login.

When a machine enrolls into MDM via ABM/ASM the current cadence is to install packages before creating the configured account.

This request is to make the account creation happen first so packages that install can use the account that is created by the MDM.

One instance is the ability to install the bootstrap token escrow with the local admin account.  

We are using few Custom Attributes that can have only some options (like kiosk app). Having drop-down list with options will be really nice.

Then it will allow us to set possible Attributes and help desk will just choice from drop-down list.

Thanks David

It would be excellent to allow a custom URL for the "Welcome screen" contents, including providing drop-in HTML for a "start enrollment" button. This way, we could for example redirect to existing EULA agreement pages and pop the user right back to the SimpleMDM workflow.

Under Passcode Policy, can the option be placed to require a passcode? I could not locate that option anywhere ...

On the main Devices View, include the serial number as a column. Or have the ability for Users to add fields to this table to customize the view.

We need a report to see device movements from users. Also see devices removed by and the related information

It would be extremely useful if a device dropping below a minimum specified battery level would trigger a notification to the administrator via email. This is a weak point with remotely located devices that are left on and accessible for long periods at a time. Even the genuine high wattage Apple chargers can require a power cycle after being left on for long periods, to avoid the device battery discharging faster than it is maintained.

allow exceptions to Apps that are still useful but are restricted to the profile settings.
if your profile settings have age restricted Apps set at 14+, have an exception box to allow Apps that have a 17+ to still function on device.

In Apple Configurator 2, there is an option to customise the “Trust” of a Wi-Fi configuration. This allows connecting to an enterprise network (in my case TTLS+PAP) without getting the “Untrusted Certificate” pop-up on iOS.
It would be great to be able to set these fields in the SimpleMDM UI too!
(I actually spent a few days searching why I was getting this pop-up on iOS, and not on macOS; turns out on macOS having the certificate installed in the keychain seems to be enough, but not on macOS…)

create automatic lists devices.
Devices are automatic assigned depending of some features like memory,, IOS version or specific version of an App installed.

Enrolling devices through Portable hotspot. When targeted devices are connected to admin device hotspot and by entering the user credentials for the login. Hence the mobile device is enrolled and the profiles are pushed.

If SSO is enabled on an instance it would be nice to disallow logins using application passwords (maybe admins or owners excluded).

We deploy Wandera using SimpleMDM to manage data use, but the integration on the Wandera side is weak. We can pass simple things during Wandera enrollment (device name, device ID, etc...) but that's about it. Is there a chance we could do more to bring these two tools together? Display Wandera stats in SimpleMDM or pull SimpleMDM information into Wandera post enrollment?