> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/sep-2026/20260908.md).

# Notice of Updates to the Cregis Standard Terms of Service

Dear Cregis Users,

We will be updating the **Cregis Standard Terms of Service** on September 12, 2026. The terms will be automatically updated at that time; no manual action is required on your part.

To review the amendments in advance, please visit Cregis official website under “Resources > Product Manuals > [Terms and Conditions](https://support.cregis.com/terms-and-conditions/cregis-standard-terms-of-service),” for the latest version. If you have any questions regarding these updates, please do not hesitate to contact our support team.

Thank you for your continued support.

Cregis Team\
2026-09-08


---

# 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://support.cregis.com/announcement/sep-2026/20260908.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.