---
title: "Query Library"
slug: "query-library"
updated: 2026-03-04T17:04:51Z
published: 2026-03-04T17:04:51Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Query Library

**Query libraries** package queries for quick access throughout your database.

The query library eliminates the need to build custom filters and exports every time a new query is constructed. Custom exports and filters can be built in the library and made accessible to end users within Configurable Joins queries.

## Creating a query library

To create a query library:

1. Go to **Queries / Reports.**
2. Select **Query Library**.
3. Select **New Library.**
4. Configure the following settings:
  - **Name**: Provide a name for this particular library.
  - **Type**: This defaults to **Configurable Joins.**
  - **Category**: Select the category (such as **Records**) where this library should be available.
  - **Base**: Select the base (such as **Person**, **Companies** and **Foundations**, or **Application**) where this library should appear.
5. Select **Save**. You are redirected to the query builder interface.
6. Add [exports](/v1/docs/adding-and-configuring-exports), [subquery exports](/v1/docs/subquery-exports-outputs), filters, [subquery filters](/v1/docs/subquery-filters), and [joins](/v1/docs/joins) as needed.

## Sharing query libraries

By default, your new query library isn’t accessible by anyone else. You can share the exports, filters, and joins in the library with other users, permissions, and roles by using the library's **Sharing Permissions**.

To share a query library:

1. In the query library, select **Sharing Permissions**.
2. Select **Add Grantee**.
3. Select the appropriate **Type**:
  - **User**: Search for and select individual users who should have access to the library.
  - **Permission:** Select a permission that the user will use to access the library (the user should already have the desired permission).
  - **Role**: Select an existing role. User accounts that have that role will be able to access the library.
4. Select the appropriate permissions as follows:
  - **Display/Run Query**: Selecting this option allows library access to users whose permissions are granted under **Type**.
  - **Edit Query**: Allows the users to access and modify this particular library item.
5. Select **Save**.

## Accessing query libraries

Libraries display the appropriate exports, filters, and joins when the base of any query matches the base of the library. This includes when main query joins have been added to the base of a query.

For example, if a library was created on a **Person** base, and a user starts a new query on an **Application** or **Gift** base, the library elements will not immediately appear. If a join is added from **Application**to **Person** or from **Gift**to **Person**, the Person-based library elements appear. If a new query is started on a **Person** base, the Person-based library items are available immediately.

To access the query libraries, proceed as follows:

1. [Create a new query](/v1/docs/query-elements).
2. Set the *Type* to **Configurable Joins**.
3. Select the appropriate **Category** and **Base** for the desired query.
4. Start building the query as desired.

When adding exports, filters, and joins, a new group of **Library Exports** appears at the top of the query part dialog, displaying the appropriate user-accessible elements from the library.

#### What if my query already has joins?

Should there already be existing joins in a query, users have the option to reference the existing pathways or the pathways described within the query library. Slate automatically deduplicates extraneous joins as necessary.

#### Don’t see your library exports, filters, or joins?

Make sure the appropriate checkbox is selected at the top of the ‘Insert Query Part’ pop-up! These boxes can be used to turn on or off the display of Library query parts.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(274).png)