Applications¶
Your devices require applications to serve a purpose. On the Applications menu, several tabs will give you access to features and sub-menus in order to manage applications and how they act on your device.
Library¶
This is the main tab you will be faced when entering the Applications menu. This is where all your business apps live. You may upload them, check which ones are currently being used, delete old unused ones, and more.
Once you've uploaded your business apps, they need to be linked to Profiles in order for them to be distributed to devices in the field.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.
You can pick and choose these permissions when creating a new Custom Role or MDM API token.
Permission category - "Applications"
Read (fms.application.read)
-
What it does: Allows users to
- Access the different Applications pages (/applications/...).
- See filters related to applications in the Profiles page.
- see the Manage Applications menu in the Profiles and Applications pages.
Note that the following permissions are also required in order to access the Manage Applications menu:
- fms.profile.read
- fms.profile.update
-
Where it applies:
- Applications (/applications)
- Essentials (applications/essentials)
- Whitelists (applications/whitelists)
- Configurations (applications/configurations)
- App store (applications/store)
- Profiles (/profiles)
- What happens without this permission:
- The Applications pages listed below can’t be accessed.
- The filters related to the applications are not visible in the Profile page
- The Manage Applications menu is not visible in both the Applications and the Profiles pages
Create (fms.application.create)
- What it does: Allows users to upload applications.
- Where it applies: Application page (/applications).
- What happens without this permission: The buttons to upload applications are not visible.
Delete (fms.application.delete)
- What it does: Allows users to delete applications.
- Where it applies: Application page (/applications).
- What happens without this permission: The buttons to delete applications are not visible.
Download (fms.application.download)
- What it does: Allows users to download applications.
- Where it applies: Application page (/applications).
- What happens without this permission: The buttons to download applications are not visible.
Essentials¶
Some applications have rather simple use-cases, but you might not want to develop them in-house as they will take time from your developers, which you would prefer be spent on more business-related tasks. Such applications could be, for example, an app to send and receive SMS messages, or an app to store contact information on the device.
To address these simple use-cases, Famoco provides what we call "Essential Apps".
If you find a need for these, simply add them to your Profiles.
Whitelists¶
When manipulating many devices across multiple organizations and fleets, or between different modes (Production VS Developer), it is possible that some leftover unwanted apps remain on the devices due to conflicting configurations. On the opposite end, while developing a new application and testing it on your devices, the MDM will try to uninstall what it considers an unknown application.
Whitelists allow you to ensure that anything not on the MDM profile, or not explicitly listed as allowed as an exception, will be totally cleaned from the device.
Once you've created a Whitelist, you need to add them to your Profiles for it to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.
You can pick and choose these permissions when creating a new Custom Role or MDM API token.
Permission category - "Applications - Whitelists"
Read (fms.applicationwhitelist.read)
- What it does: Allows users to access the Application Whitelists page.
- Where it applies: Application Whitelists page (/applications/whitelists).
- What happens without this permission: The Applications Whitelists page can’t be accessed.
Create (fms.applicationwhitelist.create)
- What it does: Allows users to create Applications Whitelists.
- Where it applies: Applications Whitelists page (/applications/whitelists).
- What happens without this permission: Buttons to create Applications Whitelists are not visible.
Update (fms.applicationwhitelist.update)
- What it does: Allows users to edit Applications Whitelists.
- Where it applies: Applications Whitelists page (/applications/whitelists).
- What happens without this permission: Buttons to edit Applications Whitelists are not visible.
Delete (fms.applicationwhitelist.delete)
- What it does: Allows users to delete Applications Whitelists.
- Where it applies: Applications Whitelists page (/applications/whitelists).
- What happens without this permission: Buttons to delete Applications Whitelists are not visible.
Configuration¶
What if you wanted different behaviours for the same app depending on the fleet of devices? Without building multiple different versions of your app, of course.
App Configuration allows you to do exactly that. Create multiple configuration files and push them to your different devices. Example: display a different user interface depending on the type of users between Fleet A and Fleet B.
Please refer to the Developer Docs - App Config sample code page in order to get more information about how your business apps are able to receive configurations from the MDM.
Once you've created App Configurations, you need to add them to your Profiles for them to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.
You can pick and choose these permissions when creating a new Custom Role or MDM API token.
Permission category - "Applications - Configuration"
Read (fms.applicationconfiguration.read)
- What it does:
- Access the Applications Configuration page.
- See the App Configuration filter in the Profiles page.
- See the Configurations section in the profile form./
Note that the following permission is also required in order to access the Applications Configuration page:
- fms.application.read
- Where it applies:
- Applications Configuration page (/applications/configurations)
- Profiles page (/profiles)
- What happens without this permission:
- The Applications Configuration page can’t be accessed.
- The App Configuration filter in the Profiles page is not visible.
- The Configurations section in the profile form is not visible.
Create (fms.applicationconfiguration.create)
- What it does: Allows users to edit Applications Configurations.
- Where it applies: Applications Configuration page (/applications/configurations)
- What happens without this permission: Buttons to edit Applications Configurations are not visible
Delete (fms.applicationconfiguration.delete)
- What it does: Allows users to delete Applications Configurations.
- Where it applies: Applications Configuration page (/applications/configurations)
- What happens without this permission: Buttons to delete Applications Configurations are not visible
App Store¶
This feature requires Famoco Layer version 3.19.0 or above.
Sometimes, you might want to provide optional apps to your users (i.e. not force them to install applications but still present them as viable options). Creating App Stores allows you to decide which applications to provide and add compelling descriptions to display to your end-users.
Once set up, users will see a new icon on their device's app launcher, from which they can see these applications and decide whether to install them or not. Please check the corresponding Famoco Layer user docs page to understand how they're displayed on the device.
Once you've created App Store configurations, you need to add them to your Profiles for them to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.
You can pick and choose these permissions when creating a new Custom Role or MDM API token.
Permission category - "Applications - App Store"
Read (fms.appstore.read)
- What it does: Allows users to access the App Store page.
Note that the following permissions are also required in order to access the Manage Applications menu:
- fms.application.read
- Where it applies:
- App store page (/applications/store).
- Profiles page (/profiles) - to link an App Store to a Profile.
- What happens without this permission:
- The App Store page can’t be accessed
- The Stores section in a profile form is not visible
Create (fms.appstore.create)
- What it does: Allows users to create an App Store.
- Where it applies: App store page (/applications/store)
- What happens without this permission: Buttons to create App Stores are not visible
Update (fms.appstore.update)
- What it does: Allows users to edit App Stores.
- Where it applies: App store page (/applications/store)
- What happens without this permission: Buttons to edit App Stores are not visible
Delete (fms.appstore.delete)
- What it does: Allows users to delete App Stores.
- Where it applies: App store page (/applications/store)
- What happens without this permission: Buttons to delete App Stores are not visible