Setup guide for admins

Check the workspace is readyCopy Anchor Link

• Docshark roles. Everyone who will connect needs a role in the workspace that includes Docshark. An app can only ever do what its person can do in Docshark, area by area (see Access).
• Mako is on. Apps reach Docshark through Mako, which is on for every workspace unless the owner turned it off. The owner controls it in Settings › Mako. While it is off, no app can use the workspace, and people who try are told to ask the owner.
• Nothing to install, no keys to hand out. There is no API key, client secret or IP list to manage. Each person signs in with OAuth on Docshark's own page.

Add Docshark for your AI app's organisationCopy Anchor Link

Do this once if your company uses Claude Team or Enterprise, or ChatGPT Business, Enterprise or Edu. On personal plans, people add Docshark themselves (Connect your app).

Claude Team and EnterpriseCopy Anchor Link

On these plans only an Owner adds a custom connector (on Enterprise, also anyone whose custom role can manage the organisation's connectors). Members then connect it with their own account.

1. As an owner, open Claude's Organization settings → Connectors.
2. Press Add, choose Custom, and choose Web if Claude asks for the type.
3. Name it docshark and paste https://dashboard.doc-shark.com/mcp. Leave the advanced OAuth fields empty; Docshark registers Claude on its own. Save.
4. Optional: open Docshark in the organisation's connectors and set how each tool is approved for members: Always allow, ask members to confirm every call, or Block a tool. Confirming every call is the careful choice for tools that send, share or change.
5. Tell your team: Docshark now appears under Customize → Connectors for each member. Each presses Connect and then Allow Claude on Docshark's page.

Claude's own guide: custom connectors.

ChatGPT Business, Enterprise and EduCopy Anchor Link

Custom MCP servers in a company workspace go through ChatGPT's developer mode.

1. As a workspace owner or admin, open Workspace settings → Permissions & roles and turn on developer mode (custom MCP connectors). On Business, each admin turns it on for themselves; on Enterprise and Edu you can grant it to chosen people with roles.
2. Add Docshark as a custom MCP server with the address above and OAuth sign-in, test it, then publish it to the workspace and choose who can use it.
3. Each person then connects it and presses Allow ChatGPT on Docshark's page.

OpenAI's own guide: developer mode and MCP apps. OpenAI renames these settings from time to time.

Editors and coding agentsCopy Anchor Link

Cursor, VS Code, Claude Code, Codex, Gemini CLI, Windsurf, OpenCode and Devin keep servers per person, in a file or a command. Share Connect your app, or the Let your AI agent set it up prompt from Settings → Connectors. For a shared repository, claude mcp add --scope project writes Docshark into the project's .mcp.json for everyone who opens it; each person still signs in as themselves.

Decide what apps may doCopy Anchor Link

Each person chooses an app's access on Docshark's Allow page, and can never grant more than their own role allows.

• Recommended is pre-selected: documents, signatures, rooms and forms can be read and changed; workspace settings (branding, plan, team) stay read-only.
• Read only suits people who only ask questions.
• Choose per area sets each of the nine areas to Off, Read, or Read & change.

To limit what apps can do across the company, limit the Docshark role: an app is checked against the person's current permissions on every call, so a role change applies to every app that person connected, at once. In Claude, the organisation's tool approvals (step 2) add a second layer on top.

Watch and end connectionsCopy Anchor Link

Open Settings → Connectors in Docshark. People who can manage the Docshark team see every connection in the workspace under Your connected apps: the app, the person, when it was connected and last used, and its access.

• Disconnect ends a connection at once: its next call is refused and its sign-in can't be renewed.
• Each person can also change the access of their own connections, or press Disconnect all my apps.
• An app Docshark can prove (Claude, ChatGPT) shows its logo. An app that named itself shows a plug and the name it gave.
• Each person gets an email from Docshark when they connect a new app, so a connection nobody expected is noticed.

Offboarding and lifetimesCopy Anchor Link

• Someone leaves or loses their Docshark role. Their connections stop on the next call. There is nothing extra to revoke, but you can disconnect them in Settings → Connectors to tidy the list.
• How long a sign-in lasts. An app's access pass lasts one hour and is renewed quietly. However often it is renewed, a sign-in ends 90 days after the person pressed Allow, and they press Allow again.
• Turning it off for everyone. The owner turns Mako off in Settings › Mako. Every app stops on its next call, and nobody can connect until it is back on.