Skip to main content


The following is an overview of the Settings Screen within the Dataset Management UI in Nexus.

🏗️ Public Preview Release 🚧

This documentation, as well as the Settings screen itself, is currently in public preview.

This page and its accompanying documentation will see updates as we continue to update our functionality. Check back soon!


The Settings Screen provides an interface for managing such items as your dataset's collaborators and API keys that enable application integration.


The Settings Screen makes it possible for other human and machine identities to both access (and possibly update) your dataset.

When setting individuals as collaborators, it is possible to give them either read-only or read-write roles. The same is true when generating API keys for programmatic interface access to your dataset.

Please be careful when managing your dataset's settings!

A view of the Settings Screen for an example dataset


The Collaborators tab of the Settings UI allows you to view and manage the identities that have access to your dataset. You can add collaborators by their username or email and assign them roles (aka policy groups) that exist for your dataset.


By default, each dataset will start with a ReadAllRole that allows read-only access to data in your dataset.

More nuanced roles can be created (e.g. that only have read-access to particular classes or even to particular properties on particular classes) via the Policy Management UI or directly through transactions that establish Policies and PolicyGroups. You can see some examples of those in our Cookbook, here.

When you add a collaborator to your dataset, your dataset will appear for that user in their main dashboard of datasets. They will be able to visit your dataset with limited access (collaborators cannot, for example, create or update policies or policy groups, nor can they manage settings for your dataset).

For example, if we add a collaborator with the default ReadAllRole, that user will be able to access your dataset and query your data (either directly or through the Notebooks UI), but they cannot issue transactions to insert, update, or delete anything in your dataset.


If you do not add a role to a collaborator, they will have full read-write access to your dataset.

A collaborator without an assigned role will effectively be a superuser for your dataset.

The modal for adding a collaborator to your dataset

API Keys

The API Keys tab of the Settings UI allows you to view and manage the API keys that have been generated for your dataset. You can generate new API keys, delete existing ones, and manage the roles (aka policy groups) that are associated with each key.

Creating API keys for your dataset allows 3rd-party clients (e.g. applications, scripts, etc.) to query and/or transact against your dataset programmatically. For example, you can use an API key to access your dataset from a Jupyter Notebook or to integrate your dataset with a custom application.

Generating an API Key

To generate an API key...

  1. (Optional) Provide a name for your new API key. Giving your API key a name will make it easier in the future to update permissions associated with that key, or to delete it entirely.
  2. (Optional) Provide a role (or roles) for your new API key.

    NOTE: if you do not provide a limited role (e.g. ReadOnlyRole) for the API key, then it will have full permissions to read-write all data in your dataset.

  3. Click the Generate key button.

Your API key will be generated and displayed in the UI. You can copy the key to your clipboard by clicking the Copy button.


The Generated API Key will only be shown to you once. If you lose it, you will need to generate a new one.

The UI for generating a new API key

Using an API Key

Once you have generated and copied your API key from the steps described above, you can use it to programmatically issue any query or transaction against your dataset.

We effectively need to just track three things:

  1. The Fluree API URL for all Fluree-hosted datasets. This is visible at the top of our API Keys screen, but it is consistent across all datasets:[ query | transact | history ]
  2. The API Key that we generated above. We will use this as the Authorization header of our HTTP request (e.g. Authorization: 7G5ka...vtlq5g).
  3. The Fluree Identifier for our dataset. Keep in mind that this is Fluree's own identifier for your dataset. My account & dataset name may be fluree/docs, but I will notice in my Query Editor and Notebooks that Fluree identifies my dataset as fluree-jld/387028092977716.

For example, let's take the following query from our Quick Start Guide Notebook:

"from": "fluree-jld/387028092977716",
"where": {
"@id": "?id",
"@type": "Yeti"
"select": { "?id": ["@type", "age", "name", "verified"] }

I can now issue this query externally from the UI, for example with the following curl command:

curl --location '' \
--header 'Content-Type: application/json' \
--header 'Authorization: 7G5ka...vtlq5g' \
--data '{
"from": "fluree-jld/387028092977716",
"where": {
"@id": "?id",
"@type": "Yeti"
"select": { "?id": ["@type", "age", "name", "verified"] }