Set up and use the QorusDocs connector for Claude

The QorusDocs connector brings AI-powered proposal and pursuit management into Claude. Bid, proposal, and sales teams can work with live pursuit data, approved answer content, and company knowledge in the same conversation where they are already thinking and drafting — with nothing copied and pasted between systems.

This article explains what the connector can do, what it can access, how authentication and permissions work, and how to connect. It is written for both end users and the IT administrators who review connectors before approving them for their organization.

What you can do with the connector

• Track your pipeline — ask which pursuits are due this week, what stage a bid is at, who is assigned, and what is outstanding.
• Answer RFP and security questionnaire questions — answers are drafted from your organization's approved QorusDocs answer library, with the source content behind every answer.
• Search company content — find the case studies, boilerplate, past proposals, and reference material your hub already curates.
• Work with pursuit documents — summarize, compare, and pull key points from the documents attached to a named pursuit.
• Review adoption and activity — see usage and activity across your teams, scoped to what you are entitled to see.

Answers are grounded in your organization's own approved content rather than a general-purpose model's recollection, and the connector will state plainly when nothing relevant was found.

Prerequisites

• An active QorusDocs subscription and a QorusDocs user account on your organization's hub. There is no self-serve or trial path without an account — contact your QorusDocs administrator, or visit qorusdocs.com, if your organization is not yet subscribed.
• A Claude plan that supports connectors (see Anthropic's documentation for current plan requirements).
• No administrator role is needed to connect. Your QorusDocs or Claude administrator is only involved if your organization restricts which connectors members may enable.

Authentication

• Connection uses OAuth 2.0 with dynamic client registration. There are no API keys, tokens, or URLs for users to enter, and no configuration is needed on the QorusDocs side before connecting.
• Users sign in with their existing QorusDocs credentials, including Microsoft Entra single sign-on where your organization uses it. The connector never sees or stores passwords — sign-in happens on the QorusDocs (or your identity provider's) hosted login page.
• Access can be revoked at any time by disconnecting the connector in Claude's settings.

Data access and permissions

The connector is read-only. It retrieves and summarizes your QorusDocs data and never creates, edits, or deletes it.

Every request runs as the signed-in QorusDocs user and honors existing hub, team, pursuit, and content permissions. The connector cannot surface anything that user cannot already see in QorusDocs. There is no service account or elevated access path.

Some tools are resolved per hub from what that hub has published, so the exact tool list a user sees reflects their organization's QorusDocs configuration.

Connect QorusDocs to Claude

1. In Claude, go to Settings > Connectors.
2. Find QorusDocs in the connector directory and select Connect.
3. A QorusDocs sign-in page opens. Sign in with your normal QorusDocs credentials (or your organization's single sign-on).
4. Review and accept the consent prompt listing the requested scopes.

Once connected, QorusDocs tools are available in your Claude conversations.

Using the connector

Some QorusDocs tools are long-running: they start a job and Claude retrieves the result when it is ready, typically within 10–60 seconds. Claude handles this automatically — a short wait after asking a question is expected behavior.

Example prompts:

• "What pursuits are due this week?"
• "Summarize the documents in the Acme Corp pursuit."
• "Answer these RFP questions from our knowledge base: …"
• "Summarize our pursuit pipeline."
• "Show QorusDocs user activity for the last 30 days."

As with any AI assistant, Claude can make mistakes. Verify important answers against the source content the connector cites before sending them to a client.

Disconnect the connector

In Claude, go to Settings > Connectors, find QorusDocs, and select Disconnect. This revokes the connector's access immediately. You can reconnect at any time.

Frequently asked questions

Can the connector change or delete data in QorusDocs?
No. The connector is read-only. It cannot create, edit, or delete pursuits, answers, documents, or any other QorusDocs data.

Can a user see data through Claude that they can't see in QorusDocs?
No. Every tool call executes as the signed-in user and is filtered by that user's hub, team, pursuit, and content permissions.

Does QorusDocs need any setup before our users can connect?
No. Authorization uses OAuth 2.0 with dynamic client registration, so no client IDs, secrets, or server URLs need to be provisioned or exchanged.

Does the connector support single sign-on?
Yes. Users sign in through your existing QorusDocs login flow, including Microsoft Entra SSO where configured.

How do we control who in our organization can use the connector?
A QorusDocs license is required, so only your QorusDocs users can connect. In addition, Claude organization administrators can restrict which connectors members may enable through Claude's own admin controls.

Does the connector handle personal health data?
No.

Support

• Help and support requests: QorusDocs Help Center
• Privacy policy: qorusdocs.com/privacy-policy