Evaluate and manage a Sheets add-on safely

Quick answer

Open Extensions > Add-ons > Get add-ons to inspect a listing, but decide whether the task needs an add-on before installing it. Review publisher identity, actual data access, costs and organizational approval. Use Manage add-ons to distinguish disabling use in one document from uninstalling across your files.

Define a concrete decision

This desktop-web exercise ends with an evidence-based install, hold or reject decision, plus a management plan. It does not install a product or claim any Marketplace listing is safe. Use a native Google Sheets practice file. If you are editing an Office-format file and Add-ons is missing, that is not proof that your account lacks every add-on; conversion to native Sheets is a separate file-format decision.

The scenario is small: you need to remove repeated product codes from an occasional import while preserving the original list for comparison. In AddonReview, enter A1 Code, then A2 P100, A3 P200, A4 P100, and A5 P300. Keep a copy of this original range. The desired distinct set has exactly three members: P100, P200 and P300. No customer or confidential business data is needed.

Before searching, write the acceptance conditions: preserve the original, produce three unique codes, avoid sending data externally unless explicitly approved, and avoid any recurring charge for this occasional job. Consider Sheets’ native data-cleanup tools first. A built-in solution that meets the requirements is a valid reason not to install anything.

Inspect a listing without granting access

Choose Extensions > Add-ons > Get add-ons and search for the actual task. Open a candidate’s full description rather than relying on a short card or a familiar-looking name. Record the exact listing URL and publisher shown, so a later review cannot accidentally refer to another product with a similar title.

Check the publisher’s support and privacy information, what data is processed, where processing occurs, whether data is retained, and what the product costs after any trial. Reviews and install counts can supply context but do not prove that your organization’s data use is allowed. A claimed security benefit is not equivalent to an administrator’s approval.

Do not click through an authorization flow simply to see whether it works. If the full requested scopes are unavailable until installation begins, record that as an unresolved approval gate. The decision can remain on hold until someone authorized to review the consent screen can evaluate it without granting access prematurely.

Work through two hypothetical candidates

These candidates are invented decision examples, not names or claims about real products:

• Candidate A describes duplicate cleanup but asks for broad spreadsheet access and an unrelated email capability. Its data-retention explanation is missing. Decision: reject for this small task until the publisher can justify the access and supply adequate documentation. A useful feature does not erase those unresolved risks.
• Candidate B describes current-document processing, supplies a clear privacy explanation and fits the cost constraint, but your organization has not approved it. Decision: hold for that review. Narrower access is better aligned with the task, not proof of safety or permission to install.
• Native alternative meets the three-code requirement on a copied range. Decision: prefer it for this occasional cleanup if the output checks pass, avoiding unnecessary persistent third-party access.

Your decision record should contain the task, candidate identity, evidence checked, unresolved questions, conclusion and date. “Looks reputable” is not a reproducible reason. The completed artifact for this tutorial is that record, not an installed extension.

If a later installation is approved

For a real approved candidate, Google’s documented desktop flow uses Install, then Continue, followed by a data-access consent screen for most add-ons. Compare the actual request with the approved scope before granting it. If the request differs materially, stop and obtain a new decision. Do not bypass blocked-app warnings or organization policy.

Test only the copied synthetic range. Whatever controls the chosen add-on supplies, verify that the output contains P100/P200/P300 once each and that the original four-row list remains available. This guide cannot name an unreviewed add-on’s buttons or promise a specific result.

For the changed case, append another P200 to the disposable input. There are now five input rows but still three distinct codes. Append P400 instead and there should be four distinct codes. Those two checks distinguish repeat handling from accidental deletion of a legitimate new item. If the tool edits in place unexpectedly, stop and restore from the preserved original rather than running it repeatedly.

Manage use and removal deliberately

For an add-on already installed with approval, open Extensions > Add-ons > Manage add-ons. Under its Options, Use in this document controls whether it is enabled in the current file. Record its previous state before a reversible test and restore that state afterward if the original workflow still needs it.

Uninstall is broader: Google’s help describes removing the add-on from all your files. Check whether another workbook depends on it before choosing that action. Disabling one document, uninstalling the product and revoking a related Google account connection are different decisions. Do not promise that one automatically erases data already retained by the provider.

After an authorized removal, reopen Manage add-ons and the practice file to verify the relevant state. Keep any ordinary output values you need, but inspect formulas or custom functions that might still depend on the add-on. A successful downloaded file does not prove the service continues to work elsewhere.

Troubleshooting and scope

Some add-ons depend on browser cookie behavior; do not weaken browser privacy settings blindly. Consult the vendor and your organization’s approved route. Android follows a different add-on/Play Store workflow, while the iOS help says add-ons are unavailable. These desktop controls should not be transplanted to either mobile app.

No real listing was endorsed, installed or granted access during authoring.

Official references

References: Google’s add-on installation and management help and Apps Script authorization model. For actual deployment, review the exact current listing, consent request and administrator policy rather than treating this hypothetical comparison as approval.