Connect your tools

Use ShareSign to research room documents, prepare an unsent agreement or check signing progress in the assistant you already use.

Open Requested access on ShareSign’s consent page. Choose your business, then approve only the permissions you need and your role and plan allow.

If a permission is missing, it cannot be approved there. Keep your working connection. Paste your agreement text in ShareSign or upload an existing PDF, or check your task in ShareSign.

You can connect a ShareSign Free, Pro or Business workspace. Free assistant access has no trial expiry and uses the same resource limits as the website; premium features keep their plan requirements. The public ShareSign connector is available on Claude Free. The optional workflow plugin adds skills and follows Claude’s paid-plan requirements; your organisation may restrict either route. Check Claude’s current plugin availability. For ChatGPT, check whether the ShareSign plugin is available to your account and organisation. Installing a plugin keeps your existing ShareSign plan and permissions.

Preparing text for review or saving an unsent draft does not use one of your monthly sends. ShareSign checks available capacity before creating a draft and again when you send it. Sent documents share the same allowance wherever you prepared them.

1. Choose a first task. Choose a first task and check the documents and access it needs.
2. Add ShareSign to your assistant. Keep this guide open while the public directory page opens in a new tab.

   Add ShareSign to ChatGPT. Choose Install plugin, then Connect ShareSign. If it is already installed, choose Try in chat.

   Add ShareSign to Claude. Choose Connect or Install when offered. If already connected, use that connection. For workflow skills in Code or Cowork, add the optional ShareSign workflow plugin on an eligible Claude plan.

3. Sign in to ShareSign and choose the business. Setup may open a separate browser window. Complete sign-in there, select the intended business and approve the permissions your task needs. Review the information each permission shares before approving it.
4. Return to the conversation. After a new ChatGPT installation, choose Set up ShareSign. In Claude, select ShareSign under the chat’s connectors menu. Your sidebar may say Plugins or Customize while Claude updates its layout. You can Open a Claude chat in a new tab. Ask the assistant to confirm the connected business and approved access before retrieving records. Switching workspaces in another ShareSign tab leaves this connection on its approved business.
5. Ask your task question and check the result. Copy a question from the task guide below. A research answer should identify its sources and coverage; a prepared agreement should have a saved, unsent draft and a ShareSign review link. Open the source or saved draft before taking the next action.

For setup and ready-to-use task questions, follow the ChatGPT guide or Claude guide. If setup is cancelled or the connection is missing, follow connection recovery. For another Claude surface, read Claude Code and Cowork setup.

For a signing-progress check, approve “Read agreements and templates” and ask:

In your room’s Files tab, choose Research this room with ChatGPT or Claude. Check the selected business and room, write your own question, then choose Copy room research prompt. Open your chosen assistant in the next step and paste the question when ready. Keep this page open while you connect. Choose Check again after updating your material or access; your question stays while you remain in the same room and business. If you change business, choose an accessible room there. In Templates, Prepare an unsent draft with ChatGPT or Claude opens preparation checks for either assistant. A Free workspace with room files can use assistant research within its existing access and resource limits.

Prepare your first assistant task checks your ShareSign business, role and saved material. Confirm the actual connection in your assistant as well. An empty business can start with a PDF or agreement text; a template is optional and follows your plan’s access. Room research needs searchable files in a room. Choose Check again after adding material. An empty result and missing permission need different next steps.

Follow the contract-clause research walkthrough for a worked example, the minimum permissions and how to check search coverage.

Choose the room and ask a specific question. Open the cited document and page to check the answer. Ask which files were searched and what could not be searched or fully retrieved. No matching excerpt does not establish that a clause is absent from every file. Keep source versions and conflicting provisions visible.

Search requires its own permission and can send matching document excerpts to your assistant provider. A scanned image or a file awaiting processing may not supply searchable text. Treat the result as evidence for your review.

Already have the agreement in ChatGPT or Claude? In Documents, choose New document, then Paste agreement text. If you have already selected files or entered a title, text preparation opens in a new tab so the upload stays available. Paste its text in ShareSign and review the generated PDF, signers and fields before accepting an unsent draft. To keep an existing PDF’s layout, upload that PDF for signing. Choose the intended business before adding either source. Each person signs through their own signing journey. You can use this route with signing access under your current plan and role, without giving the assistant more permissions. If you already have a saved ShareSign draft link, open that draft instead of uploading another copy.

Follow the agreement-preparation walkthrough to start with your PDF or text, review saved work and correct it before sending. Text authoring requires its separate permission and supporting tools. If the choice is unavailable, paste the text yourself in ShareSign and review its PDF and fields before accepting an unsent draft.

For an existing approved template, supply the recipient's name, email and role. Template access follows your plan. The assistant should ask for essential missing information, save an unsent draft and report readiness issues. The question below illustrates this optional template route; replace its fictional recipient with your intended signer.

Watch the real preparation and correction walkthrough, using a fictional business and the public Claude plugin. You can also read its transcript.

Correct the same saved draft

Ask for the precise change, then check that the assistant updated the existing draft. A recipient-name correction should keep the document identity, email address, fields and other terms. If someone else has edited the draft, compare the latest version before saving.

In chats with interactive review, separately approve Preview agreement pages when connecting to inspect the saved PDF page and select a field to check its owner, type and position. You can correct one recipient, field, title or message, then choose Save unsent correction. The saved version is checked before each correction. If someone changed the draft, refresh it and compare your proposed change before saving again. Drafting permission is required to save corrections. Existing connections keep their approved access. Without page-preview permission, the summary and draft corrections still work; open ShareSign to view the PDF. Full page content is sent to the assistant provider only with this additional permission.

Some chat clients show the review as text instead. Use the returned ShareSign link for the full editor. Larger or unavailable page previews also keep that route available. Saving a correction leaves the agreement unsent.

Open the returned ShareSign link and review the actual document, recipients and fields. Choose Send in ShareSign when ready. Neither a saved draft nor a readiness check sends it. If the host cannot transfer your PDF attachment, upload it in ShareSign or choose a template. A chat attachment alone is not a successful ShareSign upload.

After an interrupted conversation, ask for the existing preparation. Give the known draft or operation when available. The assistant inspects the saved result and opens its current version, including later human edits. If several drafts match, choose the intended one. An uncertain earlier result is a reason to inspect, rather than create a replacement.

A saved PDF draft can remain recoverable after its temporary upload expires. An in-progress, unavailable, deleted or already sent result requires its own next step; it does not authorise an automatic replacement.

Ask for an authorised room and folder for the specific completed agreement. The assistant needs approved agreement and room reads, plus your current room-management authority, to suggest destinations. Its suggestion makes no copy.

Open the returned ShareSign record, choose Add to a data room, select the intended destination and confirm Add private copy. Cancel if the destination is wrong. ShareSign rechecks the source, permissions and allowance at confirmation. The copy remains private until separately published, retains its signed-source provenance, and a repeated placement uses the existing copy.

Grant viewer activity only if you want the assistant to receive it; results can include viewer email addresses. Ask which files people opened or what reading activity was recorded. An open is an observation, not proof of investor interest, understanding or a funding decision. Missing permission and no observed activity are different results.

If sign-in was cancelled or its separate window closed, return to the existing ShareSign connection in ChatGPT or Claude and start sign-in again. Choose the intended business and permissions in ShareSign, then return to your saved task question. Check the connected business before retrieving records.

If Claude loads a ShareSign skill but cannot find its tools, open Add files, connectors, and more, choose Connectors, and check that ShareSign is selected for the conversation. An installed plugin can have its skills available while its connector is switched off. Select the existing connector, then ask Claude to check the connected business and permissions again. This does not add permissions.

If ShareSign is absent from that menu, Open the ShareSign connector in Claude. Keep this page open with your task question. Use the existing connection when available and review the intended business and permissions if asked to connect. Your organisation may restrict connectors. Use the host's supported tool refresh or a fresh task for stale inventories. A missing tool alone does not establish a failed sign-in; use Reconnect if Claude asks. A custom MCP connection supplies tools without installing the public plugin's skills.

If your assistant offers “Check access for a ShareSign task”, use it for the work you want to do. Checking access does not reconnect your account. If an extra permission is needed, continue directly in ShareSign or choose an assistant access review. Review the business and every selected permission before approving that request. If your role or plan prevents the task, follow the ShareSign guidance instead of repeatedly reconnecting. You can also continue directly in ShareSign.

If a permission is not offered on the ShareSign consent screen, it cannot be approved in that connection. The choices depend on what the assistant requested and what your business, role and plan allow. Repeating sign-in does not add a missing choice. Continue with an available task or open ShareSign to prepare the work directly, keeping any existing draft or preparation.

If the connected business is wrong, stop before retrieving records. Follow the host's reconnect control and choose the intended business and permissions in ShareSign. More permissions and reconnecting cannot enable the plugin to sign, send or publish. Use ShareSign for those actions.

Disconnect in ShareSign, Settings, Assistants to stop future access. Identify the exact connection by its business and reference before disconnecting it. Information already received remains subject to your assistant provider's settings. If your organisation restricts plugins or account sync, ask its administrator about access.

If a conversation is interrupted, ask the assistant to recover the draft you were preparing. A saved PDF or template draft opens with your later edits kept. Review the current document before sending it. PDFs can be up to 25 MB; if your assistant cannot upload an attachment, use ShareSign’s upload screen or choose a template.

Run this in the folder where you want to use the plugin. The local scope limits the installation to that folder; the package still comes from Anthropic's public directory. Code's MCP sign-in is separate from its Claude subscription login. Use the sign-in control for the installed ShareSign server and choose your business in ShareSign.

For host-specific account and organisation controls, see Anthropic's plugin guide and Claude Code installation guide.

Live API automation comes with Pro and Business. Pro includes 50 documents a month sent this way; Business has no monthly limit. A test key works on every plan, emails nobody and counts for nothing.

Automate supported signing tasks: create documents from a PDF or template, add recipients and fields, send, manage reminders, check status and retrieve the signed PDF and audit trail. Keys are made in Settings, Developers, and each carries only the permissions you tick. Send a document from a template in one call:

curl -X POST https://sharesign.co/api/v1/templates/{template_id}/documents \
  -H "Authorization: Bearer $SHARESIGN_API_KEY" \
  -H "Idempotency-Key: order-1001" \
  -d '{ "roles": { "Tenant": { "name": "Nora Whelan", "email": "nora@example.com" } }, "send": true }'

The API reference has every endpoint, error and event.

ShareSign’s Zapier app is shared by invitation until it is listed in Zapier’s public directory. Add ShareSign to your Zapier account, then connect it with an API key: Settings, Developers has a Zapier preset that ticks exactly the permissions the app needs.

For a custom MCP client, open the setup details below for the server address, OAuth connection and manual questions. Your own integrations use separately scoped API keys. The agents section of the API reference describes each tool.