¶ Nomid MDM Portal - Library
Application: Portal Nomid MDM
Document: V1.1.0
Last updated: 19/06/2026
Package file: en_US
Editorial language: en-US
The Library centralizes reusable portal resources, such as applications, contacts, and links. These items are reused in policies, launchers, and distribution flows.
Important: Changing a library item may impact policies and devices that depend on it. Review links before replacing or removing a resource.
¶ Overview
¶ Library Tabs
The main Library tabs, such as Apps, Contacts and Links.
This area is used to switch between reusable resources that can then be associated with policies.
¶ Screen elements
- Apps: centralizes reusable applications into policies.
- Contacts: organizes corporate contact lists.
- Links: maintains web shortcuts that can be published in the launcher or in policies.
- Search and filters: help you find resources before creating duplicates.
- Creation actions: allow you to add new items to the library as per permission.
¶ Application in operation
- Click on the tab for the type of resource you want to manage. Register first in the Library and then link in Policies, avoiding repeating the same configuration in several policies.
¶ Applications
¶ Application list
The list of applications registered in the Library.
This area is used to query apps available for use in policies, including public, private, managed, or manually added apps.
¶ Screen elements
- App list: shows apps available for reuse.
- Name and package: avoid confusion between similar apps.
- Version/status: indicates availability and update.
- Actions: allow you to edit, remove or review app details.
- Use in policies: The library app can be included in one or more policies.
¶ Application in operation
- Use search to locate the app, review name/package and click actions to edit. When creating policies, select apps from this library to control installation and permissions.
¶ Add application
¶ Result of selections and settings
- Managed Google Play: registers an app approved by the managed store for policy distribution.
- Upload/internal registration: allows a private app or corporate APK, requiring version and source validation.
- Name: identifies the app for administrators in Library and Policies.
- Package name: links the rule to the correct app; wrong package installs or controls another app.
- Version/file: defines the distributed artifact when there is internal control.
- Save: makes the app available for selection in policies.
The form to add application to Library.
This area is used to register an app that will be reused in policies, usually by package, Play Store/Managed Google Play or other supported source.
¶ Screen elements
- App origin: defines whether the application comes from Managed Google Play, upload or internal registration.
- Name and package: correctly identify the app that will be used in the policies.
- File or reference: informs the approved APK, link or registration.
- Version: helps control update and compatibility.
- Availability: makes the app selectable in the Apps tab of the policies.
¶ How to fill it in
- Source: choose Managed Google Play, upload/internal registration, or another supported method.
- Name: use a clear label so administrators identify the app in the policy.
- Package name: confirm the exact identifier to avoid installing the wrong app.
- Version/file/link: fill in when there is version control or an internal artifact.
- After saving: include the app in Policies > Apps and test installation on a pilot device.
¶ Application in operation
- Select add app, enter name, package/source and other necessary fields. Save and then go to Policies > Apps to add the app to a policy.
¶ Contacts
¶ Contact list
The list of contacts or lists of contacts registered in the Library.
This area is used to organize corporate contacts to distribute to devices via policy.
¶ Screen elements
- Contact lists: group reusable corporate contacts.
- List name: facilitates policy selection.
- Number of contacts: helps you review the content before applying.
- Actions: allow you to edit, update or remove obsolete lists.
- Operational use: provides support, supervisors, emergency or internal sectors on the device.
¶ Application in operation
- Create lists by area, customer, branch or operation. Then link the desired list in the Contacts tab of the policy.
¶ Add contact list
¶ Result of selections and settings
- Create list: creates the reusable contact grouping.
- List name: defines how administrators will find the set in policies.
- Description/purpose: helps identify whether the list is for support, emergency, branch, or customer.
- Save and continue: allows adding contacts in the next step.
- Cancel: discards creation and avoids empty or duplicate lists.
The first step of creating a contact list.
This area is used to name and prepare a list that will group contacts for distribution to devices.
¶ Screen elements
- List Name: identifies the set of contacts.
- Individual contact: includes name, telephone number and necessary information.
- Import or manual inclusion: allows you to create small or large lists depending on the operation.
- Validation: confirms numbers and format before distributing to devices.
- Policy membership: delivers the list only to devices that need it.
¶ How to fill it in
- List name: use a pattern by area, branch, customer, or operation.
- Description: record purpose and audience that will receive the contacts.
- Save/next: creates the container for adding contacts in the next step.
- Reuse: keep a single list when multiple policies use the same contacts.
¶ Application in operation
- Select add, enter a clear name for the list and save/advance. Use names like “Field Support” or “Contacts Branch Center”.
¶ Add contacts
¶ Result of selections and settings
- Add contact manually: includes a person, department, or service individually.
- Contact name: will be displayed on the device and should be recognizable to the user.
- Phone: defines the published number; incorrect format prevents correct calls.
- Email/other data: complements identification when supported.
- Remove contact: prevents obsolete numbers from continuing to be distributed.
- Save list: publishes the current version for use in linked policies.
The step of including contacts in the list.
This area is used to add names, telephone numbers, emails or other contact data that will be delivered to the devices.
¶ Screen elements
- List Name: identifies the set of contacts.
- Individual contact: includes name, telephone number and necessary information.
- Import or manual inclusion: allows you to create small or large lists depending on the operation.
- Validation: confirms numbers and format before distributing to devices.
- Policy membership: delivers the list only to devices that need it.
¶ How to fill it in
- Contact name: enter a person, department, or service recognizable on the device.
- Phone/email: validate international/local format according to company standard.
- Add/remove: keep the list updated before publishing policies.
- Test: apply to a pilot policy and confirm contacts appear on the device.
¶ Application in operation
- Fill in each contact with correct data, save the list and test it on a pilot policy. Review periodically to remove old numbers.
¶ Links
¶ List of links
The list of links registered in the Library.
This area is used to maintain reusable web shortcuts, such as internal portals, corporate systems, dashboards or support pages.
¶ Screen elements
- List of links: shows registered web shortcuts.
- Name and URL: identify each resource.
- Status: indicates whether the link is available for use.
- Actions: allow you to edit, remove or review the registration.
- Reuse: avoids recreating the same shortcut across multiple policies.
¶ Application in operation
- Register links in the Library and associate them with the launcher/policy when you want to make shortcuts available on the device.
¶ Add link
¶ Result of selections and settings
- Link name: defines the visible label for user and administrator.
- URL: defines the opened destination; it must include the correct protocol, such as https://.
- Icon/description: improves recognition in launcher or list.
- Save: makes the link reusable in policies/launcher.
- Internal URL: may require VPN, corporate Wi-Fi, or proxy to work on the device.
- Edit existing link: changes the destination for all policies reusing that item.
The form to add a link to the Library.
This area is used to create a web shortcut with name, URL and identifying information for later use in policies or launcher.
¶ Screen elements
- Link name: defines the label that will appear to the user.
- URL: informs the full address of the web resource.
- Icon or description: helps the user recognize the shortcut.
- Validation: ensures that the address opens correctly before publishing.
- Application: the link can be used in launcher, policy or corporate shortcuts.
¶ How to fill it in
- Link name: will be the visible label for the user in the launcher or shortcut.
- URL: enter the full address with
https://when applicable. - Icon/description: make the internal system or portal easy to recognize.
- Validation: open the link before publishing and confirm access on corporate/mobile network.
- Later use: associate the link with the launcher or policy that must make it available.
¶ Application in operation
- Enter a friendly name and complete URL, confirm that the address opens correctly and save. Then add the link in the policy/launcher when it needs to appear to the end user.