> 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/install-and-manage-integrations.md).
# Install and manage integrations
Learn how to connect and manage integrations across your organization.
Nested Knowledge connects to third-party services. They expand your literature search, retrieve full texts, provide citation context, and show available article rights. This page explains how integrations work and how to connect and manage credential-based integrations.
### How Integrations Work
Integrations are set up once at the organization level. They are then available in every nest the organization owns. Enable an integration once, and everyone working in those nests can use it.
They come in two kinds:
* **Automatic:** Available in every nest without setup. **Article Galaxy** and **scite** work this way.
* **Credential-based:** An **Organization Owner** or **Admin** connects these integrations in **Organization Management → Integrations**, using provider credentials or a provider license. **Embase** and **RightFind** work this way.
### Connect A Credential-Based Integration
To connect a credential-based integration, an **Organization Owner** or **Admin**:
1. In **Organization Management → Integrations**, select the provider's panel.
2. Enter your credentials.
3. Select **Save**.
Each panel includes a **Need help with credentials?** link. Select it for the provider's credential guidance.
What each panel asks for differs by provider:
* **Embase:** Enter an Elsevier **API Key** and **Institutional Token**. **Embase** is then available when you build or run automatic searches. See [Embase integration](/integrations/embase-integration.md).
* **RightFind:** Enter a **Username**, **Password**, and **Country**. **RightFind** reports usage rights for each record, including whether your license permits **AI/ML Use** for a full text. See [RightFind integration](/integrations/ccc-rightfind.md).
The Integrations page shows connection panels for Embase and RightFind.
### Integrations That Need No Setup
Some integrations are built into every nest and require no action from you. **Article Galaxy** retrieves full-text PDFs from a record's **Full Text** tab. This process is manual and per-study. This includes paywalled articles your organization is licensed to access. **scite** adds citation context to each record. It shows how a study has been cited, not only its citation count.
### Manage Or Remove An Integration
To update a credential-based integration:
1. In **Organization Management → Integrations**, select the provider's panel.
2. Enter the updated credentials.
3. Select **Save**.
Only an **Organization Owner** or **Admin** can update credentials. Changes apply across every nest the organization owns.
To stop using a credential-based integration, clear its saved credentials from the provider's panel.
Automatic integrations can't be turned off in **Organization Management → Integrations**. They operate per record and don't use a saved connection.
---
# 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/install-and-manage-integrations.md?ask=&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.
