> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/updates-june-2024/8-june-2024.md).

# 8 June 2024

## Rich text in clause comments & descriptions

<mark style="background-color:orange;">New feature</mark> Users can now include "rich text" (with bold, italic, underline, tables, hyperlinks, etc.) in comments and descriptions, in both ClauseBuddy and Clause9.

<figure><img src="/files/qpgVEy7piAnqY6A6nDja" alt=""><figcaption></figcaption></figure>

### Changes to how comments and descriptions are shown

<mark style="background-color:purple;">Change</mark> In the Quality Library, the descriptions and comments now act somewhat differently:&#x20;

* Descriptions are displayed with a grey background, comments with a green background.&#x20;
* Users have to click on a long comment or description to expand it.

<figure><img src="/files/WNFFRhWrWrQwAXEslqS3" alt="" width="563"><figcaption></figcaption></figure>

## Curator improvements

<mark style="background-color:orange;">New feature</mark> Many improvements were made to the way curators are handled in ClauseBuddy.&#x20;

* Curators can now be assigned to a group of users. Such "group curators" automatically collect all the rights of their group members when it comes to the calculation of access bundles — essentially, if at least one member of the group has a certain access bundle right, then the group curator(s) will also automatically have such right.&#x20;
* One or more curators can be added to each group, and each group can have one or more curators.&#x20;

<figure><img src="/files/mD2XhVhfLeFwxzWTqeUl" alt=""><figcaption></figcaption></figure>

***

## Q\&A

<mark style="background-color:orange;">New feature</mark> In Clause9, users can now flag a question with "Hide for anonymous users". This causes the question to be invisible for anonymous users who are completing the Q\&A.

<figure><img src="/files/iIUQOAxpwImkhvHs8Fi8" alt="" width="375"><figcaption></figcaption></figure>

***

## Uncover export in Clause9

The documents exported by the new "uncover export" will now also contain numbers.&#x20;

In addition, the way conditions involving lists is being described in the export, is now improved.

***

## User rights

* Addition of the "Download Truffle document" right, which allows to enable/disable the possibility to download the original DOCX file that got uploaded to Truffle Hunt.
* <mark style="background-color:purple;">Change</mark> Search folders now no longer have their own access bundles, as this extra layer of configuration proved too complex for most users. Instead, search folders receive their access rights from the underlying folders. &#x20;

***

## Various bug fixes

* In several modules (e.g., proofreading), a "file is too large" error is now  shown when files above 16 MB would be uploaded.
* In certain cases, line breaks were not included when clauses would be inserted into a DOCX file from within ClauseBuddy.&#x20;
* Due to caching, it could happen that some clauses would temporarily still include old attributes that were recently deleted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://operations.clausebase.com/updates-june-2024/8-june-2024.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.