> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/settings/terms-and-conditions.md).

# Terms & Conditions

## Purpose

Terms & Conditions allow your organization to attach custom legal or operational requirements to all generated scaffold documents.

When added, these appear automatically every time a document is created, ensuring compliance and consistent communication with customers and site teams.

If left blank, no Terms & Conditions will be attached to that document type.

## Accessing Terms & Conditions

In the **side navigation**, click **Settings → Terms & Conditions**

{% hint style="info" %}
[Click here to view how to access Terms & Conditions](/settings/accessing-settings.md)
{% endhint %}

## **Open Terms & Conditions**

Click **Customer Profiles**

<div align="left" data-with-frame="true"><figure><img src="/files/ahllQYCvmxNiO5r342Mg" alt="" width="375"><figcaption></figcaption></figure></div>

***

### Terms & Conditions Dashboard

<div align="left" data-with-frame="true"><figure><img src="/files/xTa0Dta1kbmQdSXa7sSG" alt=""><figcaption></figcaption></figure></div>

This page displays four management tiles:

* **Scaffold T’s & C’s**\
  Update Terms & Conditions for scaffold documents.
* **Handover T’s & C’s**\
  These will appear on every handover certificate you generate.
* **Inspection T’s & C’s**\
  Add inspection-specific requirements and disclaimers.
* **Dismantle T’s & C’s**\
  These apply to dismantle certificates and work orders.

Click any tile to open its editor.

***

### Editing Terms & Conditions

#### Step-by-Step

* From the Terms & Conditions dashboard, click on the template you want to edit\
  (e.g., **Handover T’s & C’s**)

<div align="left" data-with-frame="true"><figure><img src="/files/BihRmPShGwOZgI40fudM" alt="" width="375"><figcaption></figcaption></figure></div>

* A text editor will open with an empty or previously saved field.

<div align="left" data-with-frame="true"><figure><img src="/files/BWcAolZRkO090t3ysr9N" alt="" width="375"><figcaption></figcaption></figure></div>

* Enter your Terms & Conditions
  * You can write paragraphs, bullet points, safety notices, or legal statements.
* Click **Update Terms** to save.

<div align="left" data-with-frame="true"><figure><img src="/files/Y30SiXDOljaXDjkXLGDf" alt="" width="173"><figcaption></figcaption></figure></div>

***

## How It Works in Practice

* Once saved, the Terms & Conditions are automatically inserted into every document of that type.
  * Handover Terms are embedded into **Handover Certificates**
  * Inspection Terms appear on **Inspection Certificates**
  * Scaffold Terms apply to **Scaffold Sheets / Documents**
  * Dismantle Terms appear on **Dismantle Certificates**

> **Tip:**\
> If a field is left blank, nothing will appear on that document type.
>
> This gives full control to customize requirements per certificate.

***

## Real Example

* If you add safety disclaimers to **Handover T’s & C’s**, every handover document will include them without having to paste or type them manually.
* If you add billing clauses to **Scaffold T’s & C’s**, they will appear each time you generate a scaffold document.

***

## Best Practices

* Keep wording clear and consistent across all document types.
* Include safety notes, liability reminders, and operational rules.
* Review these periodically to align with updated regulations or company policies.
* If your company works in multiple regions, customize terms per requirement.


---

# 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://docs.cloudscaff.com/settings/terms-and-conditions.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.
