The following example shows which add-on trigger functionsĪre executed (if any) to create a homepage UI for different manifest However, the UI shown forĪn add-on in any given host product depends on the presence of theĬorresponding manifest field, and whether there's an associated None of the homepageTrigger sections are required. for Gmail, this homepage function never executes. this in Calendar and Drive and the homepageTrigger is disabled By default, call 'buildHomePage' to render homepage content Identically-structured per-host overrides available in each host application'sĬonfig, at, , In addition to the common configuration, there are also Will not show a homepage (or any other functionality in that host). Isn't present in the manifest, then the add-on is disabled for Gmail and Note: In order for a host to use the common homepage, bothĪnd the host's top-level resource must be present in the add-on

Homepage cards to be disabled for all hosts (unless overridden for that Thisįield is optional, and defaults to true. Host application shows the card headers in a list that the user can selectĮnabled: Whether homepage cards should be enabled for this scope. RunFunction: The name of the Apps Script function that theįramework invokes to render homepage add-on cards.

When a UI interaction in a non-contextual card results in aĭesigning a homepage isn't mandatory but highly recommended if you do not define any, a generic cardĬontaining your add-on name is used whenever a user would otherwise navigateįield to configure the default homepage (non-contextual) add-on content for.

Pop every other card off of the internal stacks.

When the user clicks the back button enough times to.

For example, from editing a Calendar event to the

When the user switches from a contextual context to a non-contextual context.

When the add-on is first opened in the host (after authorization).

Your add-on homepage is displayed when one of the following conditions are met: Used in hosts where you haven't specified a custom homepage. You can also decide to define a single common default homepage that is You can have multiple homepages, one for each host application that your add-onĮxtends.

Manifest and implementing one or more homepageTrigger functions (see You can define a homepage for your add-on by specifying it in your project

New users how to interact with your add-on. Place for when a user first opens your add-on, and are useful for teaching

Homepages can also provide an initial starting Homepages let you show non-contextual content, just like the Outside a specific context, such as when the user is viewing their Gmail inbox Non-contextual cards are used to display a user interface when the user is That provides the ability to define one or more non-contextual cards. Homepages are a new Google Workspace add-ons feature

Disable add ons in google chrome