How to use the Google Docs plugin

The Google Docs plugin allows you to embed a Google Document into your app, making it easy to share guides, resources, or written content with users.

Requirements

• This is a Boost plugin, available on the Standard, Growth, and Business plans.

• Documents must have the correct sharing permissions enabled for others to view or edit

• Users need to be signed into their Google accounts to access the document

How to use the Google Docs plugin

1. Log in, go to Builder in the left navigation

2. Click the + button to open the Plugin Marketplace

   • Search for Google Docs, then click Add Plugin

   • Name your plugin (e.g., “Shared Documents”) and click Add

3. Click the Content tab:

   • Paste your Google Docs URL into the field

   • Make sure the document’s sharing settings allow users with the link to view (or edit, if applicable)

   • You won’t see a preview in the emulator — to test, click Preview on Mobile and scan the QR code

   • Add the plugin to a visible area (such as the home screen, navigation bar, or side menu) to test it properly

4. Click the Security tab:

   • Turn on Require Login to restrict access to logged-in users

   • (Optional) Add tag-based restrictions to limit access to specific groups

5. Click the Tagging tab:

   • Enter a tag name to automatically apply to users when they open this feature

   • Click Add Tag

6. Click the Purchase tab:

   • Check Require Purchase to enable

   • Choose your product type (e.g., Single Purchase or Subscription)

   • Upload an image, fill out purchase text, and add success/failure messages

7. Click the Analytics tab to see feature performance:

   • View data such as number of views, users, and devices over time

Pro tips

• Always test document access in an incognito browser to confirm visibility before publishing.

• Use “View-only” sharing for informational documents and “Edit” access only for collaborative use cases.

• Pair this plugin with Folders or WYSIWYG features to organize multiple documents within one section.

• Avoid linking private or restricted documents, as users will see an error screen if access is denied.