> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/features/documents/glossary.md).

# Glossary

The **glossary** helps you keep key business **terms** centralized and common across the organization.

All users can view Glossary terms in the Docs tab, and additionally can filter to Glossary terms under All Documents.

<figure><img src="https://3470314135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MgAiVthA_yg9UXKuhyY%2Fuploads%2Fgit-blob-34cbae17025b48d1bbdd03c2520cf5e91d05044b%2FScreenshot%202023-09-13%20at%2012.47.38%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

Data Managers and Admins can see and create new glossary terms directly in the UI by clicking on **Create New Doc > Glossary** in the left navigation, or can upload a CSV to create and update terms in bulk.

<figure><img src="https://3470314135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MgAiVthA_yg9UXKuhyY%2Fuploads%2Fgit-blob-2735ae778e48fab7b935d33e4ddd23a619a0e91d%2FScreenshot%202023-09-13%20at%2012.54.11%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

When creating and updating Glossary terms via CSV upload, note the expected format is

* Columns in the CSV:
  * **parent\_guid** - The guid of the parent document for this glossary term, which is used to set the hierarchy of documents. If empty, the glossary term will be created at the top level with no nesting.
  * **guid** - The guid of the glossary term. If no guid is given in an import, a new term will be created. If the guid is present, that term will be updated.
  * **name** - The name of the glossary term.
  * **description** - The description of the glossary term, in markdown format. Note: this does not support @ mentions format within Select Star.
  * **business\_owner** - The business owner of the term. For users this is the user email, for teams this is the team name.If no owner is given when creating a new term, the user performing the upload will be set as the owner.
  * **technical\_owner** - The technical owner of the term. For users this is the user email, for teams this is the team name.If no owner is given when creating a new term, the user performing the upload will be set as the owner.
  * **tags** - The tags associated with the glossary term, as a comma separated list.

Stakeholders can also use the [Discussion](/features/discussion.md) tab to ask questions or make comments about the glossary term.

The owners will be notified of any comments. By default, both the Business and Technical Owner of a glossary term are set to the person who created it. [Data Managers and Admins](/user-management/user-roles.md) can change the Owners as needed, and even apply [Tags](/features/tags.md) by clicking the 🏷 icon next to the title.

Useful links:

* Glossary terms API documentation: <https://api.production.selectstar.com/docs/#tag/terms>


---

# 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.selectstar.com/features/documents/glossary.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.