Integrations

How Pishik works with SharePoint, OneDrive, and Google Drive

Pishik is a share-link product, not a file store. Your documents never touch our servers. Instead of uploading a file, you paste a share link for each document when you create a contract — the file stays exactly where it already lives, in SharePoint, OneDrive, or Google Drive. Pishik stores the link and the workflow around it; it never stores, copies, or opens the file itself.

That's the whole model, and it's deliberate: your storage keeps its own access controls, versioning, and audit trail, and there's no second copy of a sensitive contract sitting somewhere else.

What you can link

Anything your storage can share by link — Word, Excel, Google Docs, Sheets, and PDFs all work. A single contract can hold several linked documents (for example a Main Agreement plus an Excel exhibit), each reviewed separately; see multi-part contracts and per-document routing.

Good to know — because Pishik only keeps the link, any document your reviewers can open from an https:// link will work. SharePoint, OneDrive, and Google Drive are what we build and test against, so they're the smoothest path.

Get a share link for each provider

You create the link in the storage tool itself, then paste it into Pishik. These are the provider's own Share dialogs — the same steps the app shows under Settings → Documents.

SharePoint / OneDrive (Word, Excel, PDFs…)

1. Open the document in SharePoint or OneDrive.
2. Click Share and choose who the link works for: People in your organization, People you choose (add your reviewers' emails), or Only people with existing access.
3. Pick Can edit (reviewers can use track-changes) or Can view (read-only), then Copy link.
4. Paste the link into Pishik when you add the contract or part.

Google Drive (Docs, Sheets, PDFs…)

1. Open the file in Google Docs, Sheets, or Drive.
2. Click Share — keep General access on Restricted and add your reviewers' emails, choosing Commenter (suggestions only) or Editor.
3. Click Copy link.
4. Paste the link into Pishik when you add the contract or part.

For the full walk-through of creating a contract from links, see Create your first contract from share links.

How reviewers use the link

Each reviewer's email includes the document link. They open it in the tool it already lives in and comment, redline, or track changes there — with the rights your link grants. Whether they can edit is decided entirely by how you scope the link, which is worth getting right: see Scope your share links safely.

Common mistake — this is links, not uploads. If a reviewer sees "you need access" or a broken document, it's a sharing-permission issue on your storage, not a Pishik problem. Fix the link's scope and resend. See A reviewer can't open the document.

Scope your share links safely

The share link is the reviewer's key to your document. Because Pishik just passes the link along, two things are entirely in your hands when you create it: who can open the document, and whether they can edit it. Getting the scope right keeps a contract in front of the right people — and only them.

You need — edit or manage access on the document, so you can change its sharing settings in SharePoint, OneDrive, or Google Drive.

Choose the tightest scope that works

Prefer the narrowest option that still lets your reviewers in. Two are almost always right:

Why "Anyone with the link" is risky

An Anyone link (SharePoint / OneDrive) or Anyone with the link (Google Drive) opens for whoever obtains it — including people you never intended. Review links travel through email, get forwarded, and are scanned by mail-security tools along the way, so an unrestricted document link can end up far outside your team. Scope the link to your organization or to the specific people reviewing instead.

Editing rights follow the link

If you want reviewers to redline or leave tracked changes, you have to grant it in the link:

• SharePoint / OneDrive — Can edit for track-changes; Can view is read-only.
• Google Drive — Editor or Commenter for suggestions; Viewer is read-only.

A view-only link gives reviewers no way to mark up the document, so their feedback has to live in the comment box on their decision page instead. Choose the rights to match how you want them to work; see the reviewer's side in How to review.

Common mistake — sending a view-only link and expecting redlines, or reaching for Anyone with the link because a named-people link asked the reviewer to sign in. If an external reviewer genuinely can't authenticate, add their exact address to the link rather than opening it to everyone. See A reviewer can't open the document.

Send email from your own domain

Pishik sends every review request, reminder, status update, assignment, and on-behalf notice for you, automatically. Those emails go out through a configured mail channel, and replies land in your team's own inbox — never in Pishik. Pishik keeps delivery metadata (recipient, subject, timestamp, and status) and nothing more.

The delivery channels

You need — this is set up with us, not from a Settings screen. The active channel is configured where Pishik is hosted, so there's no self-serve switch inside the app. If your team wants review email sent from your own Microsoft 365 tenant, Azure, or SMTP — so it comes from your domain rather than ours — contact support and we'll arrange it.

Where replies go

Replies route to your team's reply-to address — your own, or a company-wide one your admin sets — never back into Pishik. You control that address yourself; see Company branding: logo, name, and reply-to. You can also tailor the content of every email (instructions, signature, reminder template, and more) under Customize the emails Pishik sends.

Microsoft 365 and your Sent Items

When your workspace sends through a connected Microsoft 365 mailbox, a copy of each email stays in that mailbox's own Sent Items — that's your mailbox, in your tenant, not ours. Pishik has send-only access and never reads mailbox contents. It stores delivery metadata (recipient, subject, timestamp, and status), never the mailbox itself. More on that posture in Where your data lives.

Honest delivery statuses

Every send is recorded on the Sent page with a truthful status — Delivered, Failed, or Logged — never an optimistic guess. If a message fails, the row tells you why and offers a one-click resend, and you can open any entry to see exactly what the recipient received.

What Pishik doesn't integrate with yet — honestly

We'd rather tell you what isn't here than let you assume it is. Here's the honest state of the three things people ask about most.

Microsoft Entra SSO — coming soon

Single sign-on with Microsoft work accounts (Entra ID) is in progress, so your whole team will be able to sign in with the login they already have. It isn't available yet. For now, everyone signs in with email and password, with self-serve reset if a password is forgotten and optional two-factor authentication for a second factor. Automated user provisioning (SCIM) and enforced SSO are planned to follow SSO itself.

Deep SharePoint integration — on the roadmap

Today, storage works through the share-link model: you paste links and Pishik never touches your files. There is no API-level integration and no webhooks — Pishik doesn't browse your SharePoint, sync folders, or read document contents. A deeper, API-level SharePoint integration is on the roadmap, but it isn't here yet, and nothing on the site or in the app should be read to imply it is.

E-signature — not planned

Pishik is not an e-signature tool and there are no plans to make it one. It records signing and execution status — mark each side signed, set signature dates, and link the final executed document — but it never sends a document out for signature. Use your e-signature tool of choice, then record the outcome in Pishik so the audit trail is complete. See Signature and execution tracking.