Property Bags Coming soon
Web, list, folder and tenant
See and change the hidden key and value settings SharePoint keeps on a web, a list, a folder and the app catalog (storage entities), including which keys search indexes. Or report them across many sites.
What it does
- What custom settings has someone put on this site?
- Is this property indexed for search?
- Which sites carry a given key, and with what value?
How it runs
- Sign in, then choose. Manage one site, or Report across sites.
- Manage. Pick the scope: web, list, folder, or a storage entity scope. System keys are hidden until you show them.
- 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.
- Report. Pick sites, choose what to include, and get one workbook.
How it works
Manage reads one bag at a time: the web's, a list's (held on the list's root folder), a folder's by its path, or the storage entities of the tenant app catalog or a site collection app catalog. SharePoint's own system keys are recognised and hidden until you show them, and changing or removing one asks an extra warning first. Whether a key is indexed is read from the list of indexed keys SharePoint keeps in the same bag, and ticking or clearing Indexed updates that list along with the value. A value keeps its type, and text that does not parse as that type is refused before anything is sent.
Every add, change, removal, import and restore re-reads the key, stops if it no longer matches what you loaded, saves a backup file on this computer holding the whole bag at that scope, asks you, writes, and reads it back. A failed backup means nothing is sent, and a read-back that does not show the change is reported as a failure. More than ten keys in one action asks you to type the count. Each backup records the sign-in account, the credential type and the outcome, and each change goes to the app log.
On a site that blocks custom script, a web value is written without lifting the block when the tenant allows web property bag updates on such sites; ShareMaster reads that tenant setting once per connection, and only when a write meets a blocked site. Otherwise, and always for list and folder bags, it asks to allow custom script for the change, turns it back off afterwards, and keeps a record on disk until a re-read confirms it is off, with the same banner and next-start offer as Custom Actions. If the tenant setting could not be read, the question says so. Storage entities do not involve custom script; a refusal from SharePoint is shown as it came.
Import reads a JSON export or backup, lists every key it would add or change, and sends each one as its own checked and backed-up change. It works on web, list and folder bags only. In Report mode, values of keys whose names look like secrets (containing secret, password, key or token) are hidden in the workbook unless you choose to include them.
What you get
An Excel workbook, named like Property bags 2026-10-07 14-22.xlsx, kept in Report History whether or not you save it.
Summary sheet
Scope, options, sites read and refused, and one row per site.
Property bag sheet
One row per key per scope.
| Column | Example |
|---|---|
| Site | https://contoso.sharepoint.com/sites/hr |
| Scope | Web |
| Key | DepartmentCode |
| Value | HR-01 |
| Indexed | Yes |
Storage entities sheet
The tenant app catalog's properties.
Refused sheet
Sites or parts that could not be read, with the reason.
What you need
- Site owner (Full Control) for web, list and folder values.
- SharePoint Administrator to write tenant storage entities; reading them needs read on the app catalog.
- On a site where custom script is blocked, a web value change needs custom script turned on for the change, which a SharePoint Administrator signed in as a person can do. ShareMaster turns it on, makes the change and turns it back off. With the certificate this is locked, with that reason.
What it will not do
- Search indexes property bags only on the web and on a list's root folder, not on other folders.
- An edit keeps the value's type; text that does not parse as that type is refused.
- Import only adds and changes keys; it never removes one that is missing from the file.