Custom Actions Coming soon
Script links and extensions
Every custom action on a site collection, a web and each of its lists: classic script links, SPFx application customizers and command sets, menu items and ribbon buttons, plus the tenant-wide extensions that apply. Add or remove classic script links, refresh a script's cache, or report across sites.
What it does
- What is injecting this script into every page?
- Which libraries carry a command set, and from which app?
- Which sites still use classic script links before a migration?
How it runs
- Sign in, then choose. Manage one site, or Report across sites.
- Manage. The grid lists every scope. Filter by kind; select a row to see every property.
- Change. Configuration like this has no recycle bin, so ShareMaster re-reads it first, refuses if it changed since you loaded it, saves a backup file before anything changes, asks you, then reads it back. Backups restore from the Backups button. A restored action comes back with a new id.
How it works
Manage reads the custom actions on the site collection, on the web and on every list of that web, and the tenant-wide extensions in the app catalog that apply. A part SharePoint refuses or fails to return is named on a Not read line instead of being left out silently. Report mode reads the sites you pick and writes one workbook; it changes nothing.
What it can change is narrow on purpose. Add writes a classic script link at site collection or web scope: a .js address becomes a script source, a .css address becomes a small script block that adds the stylesheet, and any other address is refused. Edit changes the title, sequence and address of a script link. Refresh cache rewrites a cache-busting value on the script address so browsers fetch it again. Remove works on any action at site collection, web or list scope, including SPFx application customizers and command sets, and says when that takes a header or toolbar off pages. Tenant-wide extensions are never changed here.
Every change runs in a fixed order: the action is re-read by its id, compared with what the grid showed, backed up to a file on this computer, confirmed by you with the backup's location in the question, written, then read back. If the backup cannot be written, nothing is sent. A read-back that does not show the change is reported as a failure, never as done. Removing or changing more than ten actions in one go asks you to type the count. Each backup records the sign-in account, the credential type and how the change ended, and each change is written to the app log.
Script links on a site that blocks custom script need custom script allowed for the change. ShareMaster asks first, records on disk that it owes a restore, allows it, makes the change and turns it back off whatever happened. If turning it off fails, a red banner stays with Retry and leaving the page asks first; if the app closes in between, the next start finds the record and offers to turn it off, only when you say so and only after checking it is still in the state ShareMaster left it. With the certificate the setting is never touched. A restore from Backups is itself a new change through the same steps, and a re-added action gets a new id.
What you get
An Excel workbook, named like Custom actions 2026-10-07 14-22.xlsx, kept in Report History whether or not you save it.
Summary sheet
Counts by kind and by location, and one row per site.
Custom actions sheet
One row per action per scope.
| Column | Example |
|---|---|
| Site | https://contoso.sharepoint.com/sites/hr |
| Scope | Web |
| Kind | Script link |
| Location | ScriptLink |
| Source | ~sitecollection/SiteAssets/app.js |
Tenant-wide extensions sheet
The app catalog's Tenant Wide Extensions rows.
Refused sheet
Sites or parts that could not be read, with the reason.
What you need
- Site owner (Full Control) on the site.
- Read on the app catalog to list tenant-wide extensions; when refused that part is reported as not read.
- Classic script links on a site where custom script is blocked need custom script turned on for the change (a SharePoint Administrator signed in as a person). Locked on the certificate.
What it will not do
- Script links run only on classic pages.
- Tenant-wide extensions are read only here: change them in the app catalog's Tenant Wide Extensions list.
- An extension that came with an installed app may be put back by the app.
- Changing an action's scope is add the new one, check it, then remove the old one: two confirmed steps.