How ShareMaster signs in
Each sign-in method, what it can reach, and what stays on your computer
ShareMaster works in your Microsoft 365 by signing in, and how it signs in decides what it can reach and who could use that access. This page explains each method in plain terms: whose identity it uses, where its secrets are kept, what is sent to ShareMaster and what is not, and how to turn it off. Each statement about sign-in here is checked against ShareMaster's own code.
Reads only. Nothing in SharePoint is changed.
What does it tell you?
- If I set up Cert authentication, can the ShareMaster company get into my files?
- What is the difference between App, Cert and User authentication?
- Where is the certificate kept, and who can use it?
- What does ShareMaster send to its own servers?
- How do I switch Cert authentication off?
How each sign-in works
- The three ways to sign in. ShareMaster offers three ways to sign in to SharePoint: App authentication (your own Microsoft sign-in), Cert authentication (a certificate kept on your computer) and User authentication (a SharePoint browser session).
- App authentication: you, signed in. App authentication is delegated: every call is made as the person who signed in, so ShareMaster can only do what that person can already do in SharePoint. App authentication uses ShareMaster's own Microsoft app as a public client, with no client secret. After you sign in, the desktop app keeps your Microsoft sign-in in a token cache on this computer, under your Windows profile, so later runs need no new sign-in until it expires or you clear it.
- Cert authentication: a certificate kept on your computer. Cert authentication registers an app named "ShareMaster Auth" in your own Microsoft 365 tenant, for your tenant only. It is created with your administrator's sign-in and approved by your administrator. The certificate is created on your computer. Only its public half is added to the app in your tenant; the private key stays on your computer in ShareMaster's local database, encrypted by Windows for your Windows account: another Windows user, or someone with only a copy of the database, can't read it, but a program running as you can. The certificate app works without a person signed in, so it is given application permissions: full control of every SharePoint site and read access to every mailbox in your tenant. Write access to mailboxes is added only if you turn on an email tool that needs it. Because the certificate can act on your whole tenant, treat the computer it is kept on like an admin's: an administrator of that computer could copy the key once ShareMaster has loaded it.
- User authentication: a SharePoint browser session. User authentication signs you in to SharePoint in a browser window inside ShareMaster and keeps that browser session on this computer, encrypted by Windows for your Windows account: another Windows user, or someone with only a copy of the file, can't read it, but a program running as you can. It acts as you, like App authentication.
- ShareMaster Monitor's Windows service. ShareMaster Monitor's Windows service uses its own certificate for each tenant, kept in the computer's certificate store. Its key cannot be exported and only the service, Administrators and SYSTEM can read it. It renews itself before it expires.
- Archive and scheduled reports in your Azure. Archive and scheduled reports run as Azure Functions in your own Azure subscription, signed in with a managed identity there.
- What is sent to ShareMaster. Signing in to your ShareMaster account sends your ShareMaster username and password and an identifier for this computer to sharemaster.io, in the body of the request. Diagnostics send error and usage events to ShareMaster, with web addresses, file paths and email addresses replaced by codes at the standard level. Turn Diagnostics off in Settings and nothing is sent. A question in the Ask box sends your question and the last few messages of the conversation to sharemaster.io. A question about your last run also sends facts from a fixed list, such as error codes and counts, and never file names, addresses, people or site URLs.
- The web tools on sharemaster.io. The web recycle bin on sharemaster.io is different: it runs on ShareMaster's server, so after you sign in there it keeps your Microsoft sign-in on that server until you disconnect, sign out and forget it, leave it unused for 24 hours, or 7 days at most. Its tokens are encrypted with a key held on that server, so a copy of the database or a backup alone can't be read; it does not protect against someone who has taken over the server itself. Everything the web tools keep is listed at sharemaster.io/privacy/web-tools.
- Switching Cert authentication off. To stop Cert authentication completely, delete the "ShareMaster Auth" app in Microsoft Entra. Deleting the setup in ShareMaster's Settings stops ShareMaster using it on this computer but leaves the app in your tenant.
What will it not do?
- This page describes the desktop app and the web tools as they are built today.
- The permissions App and Cert authentication use are approved in your tenant by your administrator, and are listed against ShareMaster's apps in Microsoft Entra.
Read next
- AI keys: Your own AI provider keys: where they are kept and what is sent.