You can build a global app that is deployed on a product’s left-navigation pane placeholder that is available for app building. In the app manifest, configure these common placeholders at modules.common. The common placeholders available for app building depend on the module you add in the manifest along with the common module
Note:Clicking on any of the links in the following table navigates you to the corresponding module’s documentation. To come back to the common module documentation, in the left navigation pane of this document, from the Module drop-down box, select the common module.
| If the other module is… | The app can be deployed on… | The common placeholders available for app building are… |
|---|---|---|
support_email support_ticket support_portal support_agent support_contact support_company | Freshdesk | |
service_ticket service_asset service_change service_user | Freshservice | |
appointment contact cpq_document deal phone product sales_account task | Freshsales Suite Freshsales Classic | |
lead | Freshsales Classic | |
chat_conversation | Freshsales Suite If an app is built for chat_conversation, it can work with Freshchat as well but a full_page_app or a left_nav_cti app cannot be rendered in stand-alone Freshchat accounts. | |
call caller_conversation caller_metrics caller_agent notification | If an app is built for these modules, it can work with Freshcaller but a full_page_app (app built only to work on the common module) cannot be rendered in Freshcaller. | N/A |
| chat_user | If an app is built for this module, it can work with Freshchat but a full_page_app (app built only to work on the common module) cannot be rendered in Freshchat. | N/A |