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

Add apps google chrome homepage