Skip to content

Suggestions

Have a great idea that you’d like to see added to our service? Perhaps there’s an existing feature that you’d like to have extended or modified? Share it here!

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

458 results found

  1. iOS Remote View/Control

    I used an MDM program (Mosyle MDM) in the past that allowed the agent to remote into iPhones and iPads to help the user with their issues. It makes things much easier, instead of using Facetime and asking the user to share their screen because they don't know how most of the time. Please add Remote View and maybe the ability to control and click. Thank you!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Allow a scheduled rotation of auto-admin passwords

    I'd like to see the ability for SimpleMDM to auto-rotate admin passwords on a specified schedule. Right now that task is only completed by the UI or an API script. The UI clicking is impossible with 1000s of machines and scripting it with an API call takes hours to run. Having an automated schedule inside the UI to auto-rotate every month or so would remove the chore of password rotation.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Descriptive page titles

    Descriptive page titles would help a lot when navigating history or having lots of tabs open.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. API Request: Ability to upload/change icons for uploaded macOS pkgs.

    Currently in the API, only pkg uploads and changes are supported. However the ability to upload or change icons is unavailable.

    The reason this is important for us is we maintain over a dozen instances and the ability to programatically set icons for our items would drastically reduce the amount of work required for us to configure especially when we're deploying new items.

    If possible, we'd greatly appreciate the following added to the API:
    - Apps -> Create:
    - New optional argument: icon.
    - Sets icon during upload.
    - Apps -> Update:
    - New optional argument: icon.
    - Replaces current…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Add the Homebrew package to shared Apps

    Homebrew is now distributed as a pkg: https://github.com/Homebrew/brew/releases/tag/4.1.13

    I'm distributing this but it would be nice if it was automatically updated for me :D

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. add the ability to preview Welcome Screens as they are created

    Rather than have to iterate changes to Welcome Screens with real hardware, it would be nice to have a generated preview in-browser as part of Enrollments > {enrollment_name} > Welcome Screen.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Add a Dark Mode option

    Add an option for dark mode on the web interface.

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Devices API - Create - Extend method to include optional params for DEP device ID and device name

    When creating a device using the Devices API create method (https://api.simplemdm.com/#devices), there are only two parameters that can be passed to it, 'name' and 'group_id'.

    It would be very helpful, especially for devices that are expected to go through automated device enrolment, if we could pass a DEP device ID parameter to it so that a DEP device that is not yet enrolled will automatically be assigned to the nominated device group.
    If the DEP device id parameter is assigned, then the response probably shouldn't include an enrolment URL, as this param should indicate the device is expected…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Prepopulate Job Name Field for New Jobs

    When creating a new job please auto populate the Job Name with something unique rather than leaving it blank. For example, something related to the current timescriptnameSerialNumber would be useful.

    The admin should be able to edit this prepopulated name if they so wish.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Report on installed certificates

    I'd like to see SimpleMDM report on installed certificates for all device types. A common feature in other MDMs, CertificateListCommand (https://developer.apple.com/documentation/devicemanagement/certificatelistcommand) has been around since iOS 4 and macOS 10.7 (!).

    While we have other tools to report on certificates (like osquery), it's useful to have MDM as a data source as well since oftentimes installed certificates originate via profiles. Knowing certificate health within the same product has benefits, and could allow for more advanced certificate management directly in SimpleMDM.

    Important fields...
    - Certificate name
    - CA/issued by
    - Expiration
    - Current validity status
    - If possible, whether…

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Add Apple Silicon Dialpad App

    https://www.dialpad.com/download/

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Reject enrollments for unsupported macOS versions when using SAML

    I am requesting SimpleMDM add guards for ADE where a macOS device is under 10.15. Copying directly from enrollment authentication config...

    "OSes prior to macOS 10.15 and iOS 13 using Automated Enrollment and all devices enrolled with Apple Configurator do not support SAML authentication and will not be authenticated. Optionally enroll them in a less secure initial device group."

    A helpful setting for sure since it means a device can be dropped into a group with no access to organization profiles, packages, or secrets. However, the device is still allowed to enroll and takes up a license. If that Mac…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Add username field to `device.enrolled` webhook event

    The goal is to have a username field in the device.enrolled webhook event.

    This field would be populated using the the custom attribute defined in the "Username custom attribute" setting in the Automated Enrollment Authentication section.

    In our use case, a user will be prompted to auth using Okta during Automated Device Enrollment (ADE). The username that is returned by Okta would be part of the webhook event payload. We use the username and device serial number to help with automating other internal processes to help determine which user is assigned to which device.

    This could be covered by https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46831099-control-webhook-data…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Allow SimpleMDM to release devices in ABM/ASM

    Allow SimpleMDM to release devices without having to sign in to Apple Business Manager. This feature is enabled by default when you add an MDM server in ABM/ASM. You can remove this feature by deselecting the option for any new or existing MDM servers you created.

    But SimpleMDM has not implemented this feature yet. Would be nice to automate the decommissioning process of the devices.

    https://support.apple.com/en-sg/guide/apple-business-manager/axmec4d28461/web

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Support choosing which webhook events to subscribe to per endpoint

    https://api.simplemdm.com/#webhooks

    The current webhook events are as follows...

    device.changed_group
    device.enrolled
    device.unenrolled
    device.lock.enabled
    abm.device.added

    Whenever any of these events occurs, the webhook endpoint is pinged. However, processing these can get particularly noisy, especially in large environments and (hopefully) as SimpleMDM adds more supported events.

    I am asking to add support for selecting which events are subscribed to per webhook endpoint. This way only events needed for a particular workflow are sent and the webhook receiver requires less work to filter out unneeded data.

    The UI could look like other SimpleMDM settings with checkboxes for each event, where by default all are…

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. Allow entry of Custom Integers for Software Update Delay Fields in Restrictions Payload

    Currently we only have the option to choose from predefined options in the dropdown list as shown below.
    Please add the ability to add a custom ineger up to the maximum allowed by Apple.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Add reMarkable to shared apps

    DMG file available publicly here:
    https://downloads.remarkable.com/

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. Support "Non-Removable" flag on deployed iOS Store Apps

    As noted here on the SimpleMDM blog, an option was added to iOS starting in 14.x where individual apps can be marked as "non-removable" by the administrator when being deployed.

    https://simplemdm.com/blog/mdm-ios-14-macos-11-big-sur/
    https://it-training.apple.com/tutorials/deployment/dm195

    "To prevent a user from uninstalling a managed app, mark the app as nonremovable when you assign the managed app to a user or device. Depending on your MDM solution, you might need to deselect a Removable attribute or set a nonremovable attribute. With your MDM solution, you may also be able to set this attribute on apps that are already installed on a device."

    I feel it…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Add support for ZIP and XIP as well as DMG

    A fair number of apps are distributed as ZIPs (and one prominent app uses XIPs) instead of DMGs. It would be convenient to be able to upload these as is, instead of having to locally convert them to DMGs first $(unzip App.zip && hdiutil create -format ULMO -o App.dmg -srcfolder App.app)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Scope profiles to build version

    With the advent of RSRs, the OS version is no longer a definitive identifier of what OS rev a system is on. The OS build numbers would be a more consistent way to identify target OSes.

    Historically, macOS minor builds have followed an pattern of
    [Major OS number][A...Z minor build][Patch Number] moniker.

    Now with RSRs, the build numbers are a bit more complicated but the values still go up and each build number is larger than the last based on the pattern above.

    13.3.1 22E261
    13.3.1 RSR 22E772610a
    13.4.0 22F66
    13.4.1 22F82
    13.4.1 RSR 22F770820b

    I propose that Build numbers…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 3 5 7 … 22 23
  • Don't see your idea?

Suggestions

Categories

Feedback and Knowledge Base

(thinking…)