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!

415 results found

  1. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Customize Self Service Kiosk

    I want to be able to change text and icon for the kiosk

    https://kb.filewave.com/attachments/16?open=true

    Doesn't have to be this complete but simple changes so it says <company name> software kiosk

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Include "less than macOS version" and "greater than macOS version" for profile scoping

    It would be very helpful to be able to define "less than" and "greater than" macOS version when scoping profiles. For example, I would prefer to specify "less than macOS 12" for a profile to apply to all versions of macOS 11. As it is, I have to update the maximum OS version every time a new dot release comes out.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Disable ActivationLock via API

    It should be possible to disable the ActivationLock via API call, this is specificly helpfull if you want to decomission a device.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Control Webhook data

    Webhooks are very limited in what they provide without triggering another API call to pull in more information. The ability to control the payload within the webhook endpoint creation screen would be a huge help in interfacing with other programs. The ability to add static data to the payload (like we can already do to the header) or be able to add dynamic data through attribute support.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Add support for additional com.apple.MCX keys in FileVault profile type

    The current FileVault profile builder in the admin GUI only has options included in com.apple.MCX.FileVault2, the escrow payload, and dontAllowFDEDisable. Please add support for dontAllowFDEEnable and DestroyFVKeyOnStandby from com.apple.MCX as well.

    Apple docs here: https://developer.apple.com/documentation/devicemanagement/fdefilevaultoptions

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Improve Device Search with More Attributes

    Currently device search only supports device name, serial number, IMEI, MAC, and phone number.

    Scenarios where search doesn't return the results I need:
    - When I need to search by a custom attribute. For example, say I want to return all devices where the username attribute is "nathaniel.strauss". I am unable to since those attributes are not exposed in search. This is a common ask - "How many devices does x have?" The same holds true for any custom attribute set from SAML assertion - team, department, etc.
    - When the device name (SimpleMDM defined) doesn't match the Device Name…

    61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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…

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  11. Provide a mechanism to assign profiles and applications based on attribute values.

    I'd really like to assign apps and profiles based on attributes collected by an enrollment customization welcome screen form.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  12. Add device EID from DeviceInformationResponse.QueryResponses.ServiceSubscriptionProperty command

    Hello,

    as part of eSIM distribution it will be very nice to have EID of the devices accessible via API in device details (adding EID to portal will be also nice).

    Can you please add EID to each device from MDM command (this command is already in use by SimpleMDM for other data) https://developer.apple.com/documentation/devicemanagement/deviceinformationresponse/queryresponses/servicesubscriptionproperty

    Thank you David.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  13. Simplify User Enrollment using SAML Attribute(s)

    When using User Enrollment pre populate the Managed Apple ID form with an attribute from the SAML auth process (or better yet skip the screen all together). The scenario is that a user's IDP username might be the same as their managed apple id username and entering it again is duplicative.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  14. Nested Custom Attributes

    Description: It would be extremely useful to have the ability to nest custom attributes in SimpleMDM. This feature would allow administrators to create custom attributes that reference or depend on other custom attributes, enabling dynamic and interconnected data management.

    Use Case: For instance, suppose an organization has a custom attribute called "munkimanifestdepartement" that is a dropdown value in the DEP (Device Enrollment Program) welcome screen. The organization also wants to create another custom attribute called "munkimanifest" that includes the department value selected in "munkimanifestdepartement" along with additional static text. By nesting the custom attribute "munki

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  15. Regex Rules for Custom Attribute Validation

    Description: It would be highly beneficial to have the ability to use regular expressions (regex) to validate user-defined custom attributes in SimpleMDM. This feature would allow administrators to set specific rules and patterns that user inputs must adhere to, ensuring data accuracy and consistency.

    Use Case: For example, suppose an organization has a custom attribute for employee IDs. By implementing regex rules, the administrator can define that the employee ID must follow a specific format, such as a combination of letters and numbers. Any user input that does not match the defined regex pattern would be flagged as invalid, preventing…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  16. Build in native support for Nudge

    As Mac admins, it's fair to say that the current state of patch management isn't great... and that Nudge is the go to open source tool to get devices patched in a timely fashion. I can also see that other vendors have actually integrated Nudge into their products.

    It would be awesome if SimpleMDM would consider something similar - not least because of how well you've integrated Munki.

    Selfishly it means I don't have to roll it out myself... ;)

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  18. More granularity on the SimpleMDM menu bar icon...

    So, we've just rolled out Nudge and have used the SimpleMDM agent to do so. And now I'm being grumbled at about the Managed Software Centre Icon taking up valuable menu bar space...

    I appreciate I can kill it via the UI - but it's a bit all or nothing, and when we start adding apps to self-service, the menu bar app seems as good a place as any to direct our end users.

    So - can we set icon visibility per assignment group?

    I think what I'm basically saying is if all apps are managed, and there's no self-service…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  19. 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…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  • Don't see your idea?

Suggestions

Categories

Feedback and Knowledge Base