> 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-may-2024/25-may-2024.md).

# 25 May 2024

## On-the-fly-provisioning (OTFP)

<mark style="background-color:orange;">New feature</mark> If SSO is enabled, administrators can now configure OTFP. If enabled, this will cause a user to be automatically created in the ClauseBase-platform when a user is authenticated by the customer's SSO server and then gets sent to Clause9/ClauseBuddy.&#x20;

The default profile and group(s) of which such new user must be part, can be configured by the administrator.&#x20;

<figure><img src="https://1414353930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc1g6bv00az2hAVxclF4w%2Fuploads%2FeibDhWJSBnX6YzSXZ2Nl%2Fimage.png?alt=media&amp;token=4b746d78-65d0-4b5f-8cf5-a9d3b545e97b" alt="" width="285"><figcaption></figcaption></figure>

***

## Various improvements to ClauseBuddy

* The "ClauseBase" style scheme will now only be shown in ClauseBuddy for documents created with  Clause9.
* The **"Taxonomies" system** (which allows folders to be tagged with predefined taxonomies) is  phased out, because users were not actively applying any taxonomies.&#x20;
* The **Truffle Hunt "Manage" tab** is now hidden when users are not curators and do not have any upload/editing rights for any of the Truffle Hunt baskets.&#x20;
* Improve the position of the **"animal" icons** (icons that allow users to take their currenty query from one search module to another, e.g. from a search in the Quality Library to a search in Truffle baskets).&#x20;


---

# 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://operations.clausebase.com/updates-may-2024/25-may-2024.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.