How Flexshop, Helpdesk and CRM use AMS
AMS is the record of your assets; other Juvaro products read it, and CRM shares customers with it.
AMS is the system of record for your assets: what you own, who holds it and where it is. Other Juvaro products read that record instead of keeping their own copy.
| Product | What it does with AMS | Where you see it |
|---|---|---|
| Helpdesk | Links tickets to assets with its asset picker, and suggests knowledge articles linked to an asset. | In AMS: the Support cases card. In Helpdesk: the ticket's Asset field. Support cases from Helpdesk |
| Flexshop | Flexshop and AMS do not exchange data today. See the Flexshop articles. | In Flexshop only. AMS has no Flexshop screens. |
| CRM | Shares customers with AMS. CRM customers and their promoted contacts appear in AMS read-only; a customer created in AMS is created in CRM too. | In AMS: AdministrationCustomers (MSP mode) and the Users page. Customers (MSP mode) |
| Tenant Portal | Grants access, holds teams, your language and your email settings. | Grant access, Language and email settings |
| Integration Hub | Connects device-management and REST sources (Intune, Jamf, REST JSON) for loads bigger than a spreadsheet. | Assets from a connected system can be created again by the next sync if you delete them in AMS only. Import data |
What is not connected
- AMS does not create Helpdesk tickets.
- AMS has no Flexshop or HCM screens. Orders, people and leave are handled in those products.
- Renaming a customer whose name is kept in CRM is refused in AMS; rename it in CRM.