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!

424 results found

  1. Create a Vanta integration

    Vanta is an automated compliance tool. If SimpleMDM created an integration, it would be much easier for us to deploy across various products as part of a comprehensive compliance package.

    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. Enable adding multiple devices to app assignment groups Via API

    It would be nice to be able to add multiple devices using their device ID's to an app assignment group using the API. There is no easy way to add multiple devices to an assignment group unless they are already in a device group, and you may want to add specific devices in ag group rather than the full group for some apps, IE: installers.

    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)
  3. Expand Webhook triggers

    If we had the ability to choose which webhook events to subscribe per endpoint (https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46289557-support-choosing-which-webhook-events-to-subscribe), the addition of more triggers would be valuable in automating and validating workflows.
    Here are some of the possible triggers:
    abm.device.removed
    profile.added
    profile.updated
    profile.removed
    application.added
    application.updated
    application.removed
    script.added
    script.updated
    script.removed
    script.job.run

    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. API device profile install status

    In webUI you can see the profile install status, but in API you can only see "assigned" and no visibility of whether it installed or not. This is useful information, particularly in my case when assigning a SCEP profile where the CA is in corporate network. The profile install frequently fails due to devices being off LAN.
    This could be an install status when querying device/profiles or an installed profile list when querying devices, which we'd compare to assigned profiles.

    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)
  5. 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)
  6. 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)
  7. 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)
  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)
    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. Implement "force password change when the user authenticates"

    As per https://support.apple.com/en-ca/guide/deployment/dep4d6a472a/web, Apple has an API for forcing a user password change. This is useful when updating password policy - passwords that met the old policy but no longer meet the new policy are not evaluated and forced to change. This setting, however, would make it so.

    6 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)
  10. Add the possibility to mark a custom attribute as secret with the API

    In the SimpleMDM UI is it possible to mark a custom attribute as secret. When using this API it is not possible to whether the attribute is secret. It is also not possible to change this and mark secret an attribute that already exist.

    I would like to be able to mark a custom attribute as secret using the API and to get its status back.

    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)
  11. Provide option to flush attributes and recalculate the device name on re-enrollment.

    If a device is wiped and re-enrolled, but is not deleted, the device name and attributes 'stick' to the device when it is re-enrolled. Deleting devices immediately isn't always possible, since we may need to wait for a queued wipe command to reach the device.

    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)
  12. 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)
  13. 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)
  14. Allow pushing contacts to a group

    Send phone contacts to a group via a direct push

    5 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)
  15. 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)
  16. Further Document or Create Tutorial for SimpleMDM App Deployment

    I've seen mentioned in Slack and seen in my own deployments that a fair amount of confusion comes from having SimpleMDM appear to be listed as an available app, even though a customer still needs to purchase it via VPP in order to deploy it. In my own first usage, I attempted to deploy with out purchasing, and when I figured out what was going on, I was able to correct the problem, but the installation took some time. I've seen at least one other user confused about this in the Mac Admins Slack, and I would expect that this…

    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)
  17. Force user's device to enroll when an Office 365 email account is added

    Force user's device to enroll when an Office 365 email account is added. I see in my 365 portal that Microsoft is supporting external MDM providers already Airwatch, Mobileiron.

    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)
  18. Okta Device Trust integration

    Okta have nice "Device trust" setting do you guys think it will be possible to cooperate with them and make this happen?

    https://help.okta.com/en/prod/Content/Topics/Mobile/Okta_Device_Trust_Jamf_macOS_Devices.htm

    It is easy for iOS/Windows but they need some API access to verify device in MDM.

    Thanks

    5 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)
  19. App installation dependencies for macOS

    We have some installation dependencies for applications that we're deploying to macOS, but it doesn't appear possible to specify dependencies for Apps & Media within SimpleMDM. Because of that, we're unable to control the order that those packages are installed in. It would be nice to have the ability to mark certain app install bundles as dependent upon others.

    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)
  20. Allow for search params via dep_servers/$id/dep_devices

    Similar to /devices/ allow searching for dep devices by "attributes": {"serial_number"}, or "relationships": {"device": {"data": { "type": "id" {$id}}}}.

    Or possibly add a relationship on the device record to its DEP device entry.

    5 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)
1 2 5 7 9 21 22
  • Don't see your idea?

Suggestions

Categories

Feedback and Knowledge Base