* [Query library](queries/query-library.md)

**Query Library** lets you store, reuse and share queries across your workspace. Create and run queries in query library, and call them from any Openblocks app.

The main function of the query **** library is to create and manage reusable queries:

* Writing queries based on data sources, with the ability to define **Inputs** variables.\

<figure><img src="../.gitbook/assets/query library 1.png" alt=""><figcaption></figcaption></figure>

* Importing and triggering queries from query library in apps and modules.\

<figure><img src="../.gitbook/assets/query library 2.png" alt=""><figcaption></figcaption></figure>

* Referencing different versions of queries.\

<figure><img src="../.gitbook/assets/query library 3.png" alt=""><figcaption></figcaption></figure>

1. Click **+ New** and select a data source.

<figure><img src="../.gitbook/assets/query library 4.png" alt=""><figcaption></figcaption></figure>

<figure><img src="../.gitbook/assets/query library 5.png" alt=""><figcaption></figcaption></figure>

2. Rename the query on demand.

3. Write code and click ▶ **Run** to get results. The results will display in the bottom pane of the window.

<figure><img src="../.gitbook/assets/query library 6.png" alt=""><figcaption></figcaption></figure>

There are cases where you want to pass dynamic parameters to a query. Openblocks supports that by introducing input configuration of a query.

Click **Add** in the **Inputs** tab in the right pane to add input parameters. Reference them using `{{}}` in the query, then you can input test values to test execution of the query.

<figure><img src="../.gitbook/assets/query library 7.png" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

You can only reference variables instead of writing JavaScript code in `{{}}`.

{% endhint %}

To edit the name and description of the input variables, click `...` and select **Edit** or directly click the title of the variable.

<figure><img src="../.gitbook/assets/query library 8.png" alt=""><figcaption></figcaption></figure>

Queries may be updated on demand. You can make an adjustment to a query to a newer version and at the same time maintain the older version. Such version management is achievable in query library. Click `···` in the top right corner to publish different versions of queries, and you can view and restore history versions.

<figure><img src="../.gitbook/assets/query library 9.png" alt=""><figcaption></figcaption></figure>

When you finish writing a version of the query, you can publish it. Click `···` > **Publish**. Use [semantic versioning](https://semver.org/) (also known as SemVer) to name your version.

<figure><img src="../.gitbook/assets/query library 10.png" alt=""><figcaption></figcaption></figure>

To view and restore the history versions, go to `···` > **History version**.

You can restore your current draft to a history version by selecting the target version from the history version list and clicking **Restore this version**. Click **Exit** to return to edit mode.

<figure><img src="../.gitbook/assets/query library 11.png" alt=""><figcaption></figcaption></figure>

1. In an app or module, Click **+ New** in the **Query editor** in the bottom pane, then select **Import from Query Library**.

<figure><img src="../.gitbook/assets/query library 12.png" alt=""><figcaption></figcaption></figure>

2. Select a query from the library from the dropdown list, choose your desired version and pass in corresponding input parameters.

<figure><img src="../.gitbook/assets/query library 13.png" alt=""><figcaption></figcaption></figure>

<figure><img src="../.gitbook/assets/query library 14.png" alt=""><figcaption></figcaption></figure>

3. For other settings, see [query-basics.md](query-basics.md "mention").

Workspace **Admin** and members of **Developers** group have access to the **Query Library** and have read and write permissions to all queries in the library.

Openblocks implements [Role-based Access Control](https://en.wikipedia.org/wiki/Role-based\_access\_control) (RBAC) by assigning a set of permissions to different roles. These permissions determine the actions users can take on resources, including apps, modules, queries, data sources, and folders.&#x20;