Google Docs add-ons and requested permissions
An add-on can request access to information beyond the paragraph you are editing. Review the requested permissions before deciding whether the task justifies them. Google’s add-on instructions describe installation and data-access requests.
A formatting task example
A fictional team wants to format a document. Compare a narrowly scoped formatting add-on with another option requesting wider file access. Read what each option does and which data it would be allowed to use; a familiar name or a short installation flow doesn’t explain why it needs access to unrelated files.
Use the team’s policy. If an option asks for unrelated access, record that reason rather than treating every permission request as a routine confirmation.
Installation boundaries
The course models extension selection and permission review locally. It doesn’t install software, authorize a Google account or run an extension. In Google’s live products, add-ons use the Workspace Marketplace and may be restricted by an administrator. Files opened in Office editing mode must be converted to the native format before using add-ons.
Continue with sharing permissions and document templates for other controlled document workflows.