SPO-Assist vs SP Editor: Which SharePoint Online Chrome Extension Do You Need?
If you manage or build on SharePoint Online, you've probably found yourself digging through devtools or clicking through five settings pages just to find a field's internal name or check who has access to a list. Both SPO-Assist and SP Editor exist to fix that — but they're built for different jobs.
The short answer
SPO-Assist is an admin-focused quick-actions extension. It surfaces the information admins need constantly — internal field names, who has access, content types, views, sample data — and adds deep-links back into classic settings pages, without leaving the page you're on.
SP Editor is a developer toolbox. It's built for people writing and injecting code against SharePoint — PnP JS and Graph SDK consoles, a REST client, webhook management, and a file editor for pushing JS/CSS changes to a site.
If your day-to-day is administering sites — permissions, content types, list configuration, troubleshooting access issues — SPO-Assist is the leaner, faster tool. If your day-to-day is writing code against SharePoint — testing REST calls, injecting scripts, managing webhooks — SP Editor's toolbox will feel more at home.
Feature-by-feature
| Task | SPO-Assist | SP Editor |
|---|---|---|
| Field internal names | Yes, one click | Via property inspection |
| Who has access to a list/site | Yes, built-in | Not a core feature |
| Content type lookup | Yes | Not a core feature |
| View/query inspection | Yes | Not a core feature |
| Classic settings deep-links | Yes | No |
| PnP JS / Graph SDK console | No | Yes |
| REST client | No | Yes |
| File editor (JS/CSS injection) | No | Yes |
| Webhook management | No | Yes |
Who each tool is for
Choose SPO-Assist if you're:
- A SharePoint Online administrator handling day-to-day access and configuration questions
- A consultant who jumps between many tenants and needs answers fast, without opening devtools
- Someone who wants a lightweight tool that doesn't require any setup or scripting knowledge
Choose SP Editor if you're:
- A SharePoint developer actively writing and testing code against SPO
- Managing webhooks or injecting custom scripts into sites regularly
- Comfortable working in devtools as part of your normal workflow
Can you use both?
Yes — plenty of consultants who wear both hats (admin and dev) run both extensions side by side. They don't overlap much: SPO-Assist handles the "what is this and who can see it" questions, SP Editor handles the "let me write and test some code" work.
Try SPO-Assist
If you spend more time answering "why can't this person see this file" or "what's the internal name of this column" than writing code, SPO-Assist is built for exactly that.