SlideRepo Support

Welcome. SlideRepo is built and supported by The No Good Company.

The fastest way to get help is the built-in reporter inside the add-in itself. It attaches diagnostics automatically so we can investigate without a back-and-forth.

Quick links

📨 Email: info@thenogoodcompany.com
🐞 In-app: PowerPoint → SlideRepo task pane → Information menu (ⓘ) → Report a bug
🔒 Privacy: privacy.html
📄 Terms: terms.html
💳 Pricing: pricing.html

Before you contact us: quick fixes

A lot of issues clear up after one of these:

Reload the task pane. Close the SlideRepo pane and reopen it from the Insert ribbon. PowerPoint will fetch the latest version of the add-in.
Sign out and back in. Information menu → Sign out, then sign back in. This refreshes your Microsoft 365 session.
Check your SharePoint permissions. SlideRepo uses SharePoint’s own permissions. If you can’t see a repo or get an “access denied” message, ask your SharePoint admin to confirm you have access to that document library.
Try a different host. If something looks broken on PowerPoint for the web, try the Desktop app (or vice versa) to narrow it down.
Check your network. SlideRepo needs to talk to graph.microsoft.com and login.microsoftonline.com. Corporate proxies sometimes block these.

If you’ve tried the above and still hit the issue, send us a report. We read every one.

How to send a great bug report

Easiest way: use the in-app reporter

Open the SlideRepo task pane.
Click the Information menu (the ⓘ button next to your name).
Choose Report a bug.
Describe what you tried to do, what you expected, and what actually happened.
Optionally attach a screenshot.
Click Send report.

The Add-in attaches a diagnostics log and environment info automatically, so you don’t have to gather any of it yourself.

Or by email

If you’d rather email us directly at info@thenogoodcompany.com, please include:

A short title that sums up the problem.
The PowerPoint host you’re on (Desktop on Mac/Windows, Web, iPad).
Your PowerPoint version (Help → About).
The active repo name (and which SharePoint site, if you’re comfortable sharing).
Steps to reproduce: what you did, in order.
What you expected.
What you saw: error messages, screenshots, or a screen recording if you can.
The approximate time the problem happened (so we can correlate if needed).

Common questions

Where does my data go?

Your slides, configuration, and audit log stay in your own SharePoint and OneDrive. We have no access to them and no way to gain access.

Three narrow things do reach us: a bug report, if you press Send in the Report a bug dialog (including the diagnostics log it attaches); standard web-server logs when PowerPoint loads the add-in’s files; and, if your organization bought SlideRepo through Microsoft AppSource, the purchase and contact details Microsoft passes to us as the publisher. The Privacy Policy describes each in full, including how long we keep it.

Why does SlideRepo ask for `Mail.Send`?

So the Add-in can send approval/rejection notification emails to slide submitters and admins from your own account, for example telling someone their slide was approved. We never use this permission to send mail without you triggering it. (Bug reports do not use this scope; they go to our support system over an authenticated API.)

How do I uninstall SlideRepo?

In PowerPoint: Insert → My Add-ins → SlideRepo → Remove.
Cleanup (optional): If you want to remove the configuration files SlideRepo created, look for a .slidelib/ folder and a .slidelib-hub/ folder in your OneDrive, and a _config.json in each SharePoint repo’s root. Delete them if you no longer need them. Slides themselves are normal PowerPoint files and stay where they are.

Does SlideRepo work offline?

No. SlideRepo needs to reach Microsoft Graph (graph.microsoft.com) and Microsoft sign-in (login.microsoftonline.com) to do anything. Once slides are inserted into your deck, that deck of course still works offline like any PowerPoint file.

Can multiple teams have their own slide library?

Yes. SlideRepo supports multiple repos. Each can have its own admins, categories, and approval policy. Users see the repos they have SharePoint access to. To add or create one, open Settings → Repos.

What languages does SlideRepo support?

English, French, Spanish, and Arabic (right-to-left). You can switch from the Information menu → Language. Admins can also override translations per repo via Settings → Custom Labels.

My duplicate-detection seems off and a near-duplicate wasn’t caught.

SlideRepo uses a perceptual-hash (pHash) comparison of the slide’s rendered thumbnail plus a text comparison. If a slide was heavily re-styled or has very little visual content, dedup may not flag it. If you think a real duplicate was missed, please send a bug report with both slide files attached. It helps us tune the detection.

I have a billing or subscription question.

Billing runs through Microsoft AppSource, not us. For invoices, payment methods, changing your seat count, or cancelling, use the Microsoft 365 admin center or Azure portal where the subscription lives.

For anything about the licence itself, such as what your plan includes or whether you need more seats, email us and we’ll sort it out.

Do I lose my slides if I cancel?

No. Your slides are ordinary PowerPoint files in your own SharePoint, and your categories, audit log, and settings are plain files alongside them. Cancelling removes your access to the add-in, not your library. Everything stays exactly where it is and stays usable in PowerPoint and SharePoint.

Where does the diagnostics log come from?

SlideRepo keeps a small in-memory log of the actions and errors during your current session. It’s not persisted anywhere unless you explicitly send a bug report (then it’s attached to the ticket as a file). To see it locally for your own debugging, open the task pane with ?debug=1 appended to the URL.

What’s your response time?

It depends on your plan:

Plan	Support
Starter and Team	Email support. We aim to acknowledge within two business days.
Enterprise	Priority support with an agreed SLA, plus a named contact.

Critical issues get triaged ahead of the queue on every plan. We’re a small team, so please don’t take silence as us not caring; we read every report.

Status, roadmap, and feedback

We’re not posting a public roadmap yet, but we’re actively iterating. The best way to influence what comes next is to send us a report describing the workflow you want to be smoother. Concrete examples land much harder than feature wishlists.

Contact

The No Good Company
info@thenogoodcompany.com