> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/integrations/ccc-rightfind.md).

# CCC RightFind

Connect CCC RightFind to view and filter full-text usage rights.

**Copyright Clearance Center (CCC) RightFind** shows your full-text **Usage Rights**. Nested Knowledge has worked with CCC to be able to display rights information from your CCC license into our platform. Use it before you process, print, or share a full text. It shows whether your license permits **Print**, **Digital Use**, **AI/ML Use**, and **Reactive Sharing**. See [Usage Rights.](/account-management/organization-management/organization-settings/usage-rights.md)

The **AI/ML Use** right tells you whether your license permits **Nested Knowledge** AI tools to process a full text. For regulated evidence work, filter records by usage rights before processing them.

The integration is available to organizations with a **CCC RightFind** license. It covers usage rights only. It doesn't retrieve full texts. Use [Full Text Import](/review-workflow/screening/full-text-import.md) to retrieve full texts.

{% hint style="info" %}
**Usage Rights is broader than RightFind.** **RightFind** is a source of usage-rights data. Additional sources may become available.
{% endhint %}

### Connect RightFind

1. In **Organization Management → Integrations**, find **RightFind**.
2. Enter your **Username**, **Password**, and **Country**.
3. Select **Save**.

If you need help, email <support@nested-knowledge.com>.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FWQcyk45z9DgCILUfgOU7%2Fintegrations.png?alt=media&amp;token=69cce72f-06d5-4803-ac66-8360f48031fa" alt="The RightFind integration settings, with fields for username, password, and country."><figcaption><p>Enter your CCC RightFind credentials in the integration settings.</p></figcaption></figure>

### View Usage Rights

After you connect **RightFind**, usage rights become available for your records. On a study, select **R** in the record header. It appears alongside **Abstract**, **Full Text**, and **Supplements**. The panel shows the rights for the full text and its source:

* **Print**—permission to print the article.
* **Digital Use**—permission to use the article digitally.
* **AI/ML Use**—permission to process the article with AI/ML tools, including **Nested Knowledge** AI features.
* **Reactive Sharing**—permission to share the article on request.

Each right is marked **Grant (***✓***)**, **Deny (X)**, or **Unknown (?)**.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F3Drrnm4PQ9gBA4zw2sZR%2FScreenshot%202026-08-04%20at%2016.57.24.png?alt=media&amp;token=e9848b0f-a03f-4246-bfd6-ba6311476a58" alt="A record&#x27;s Usage Rights panel, showing Print, Digital Use, AI/ML Use, and Reactive Sharing statuses."><figcaption><p>Review usage rights for a record from its header.</p></figcaption></figure>

### Filter Records By Usage Rights

In [Study Inspector](/review-workflow/study-inspector.md), use **Usage Rights** to filter records by a right and status. Select a usage, such as **AI/ML Use**, then select **Grant**, **Deny**, or **Unknown**. This identifies records your license permits you to process with an AI tool.

Use **Usage Rights Ineligibility** to filter directly to records that aren't eligible for a selected use.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nested-knowledge.com/integrations/ccc-rightfind.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.