Terms & Conditions

ScopeStack lets you build a complete set of Terms and Conditions and control how they appear on each project.

Creating Terms and Conditions

Create Terms and Conditions in Settings to make them available on new projects. Creating a new term does not affect previously created projects.

Go to Settings > Content > Terms and Conditions.

On this screen: The Settings page for Terms and Conditions shows a list of all terms configured for the account, displayed in the order they will appear in documents. Each row shows the term name. A drag handle on the left of each row allows reordering. A ”+ Terms and Conditions” button appears at the bottom or top of the list to create a new term.

Here you can see the full list of terms in your account, displayed in the order they will appear in documents. Drag and drop terms to reorder them. Click + Terms and Conditions to create a new term.

Give your term a name and add its content. The name can be used in your document template to target a specific location for that term.

Required vs. Optional Terms

Each term can be designated as Required or Optional:

• Required: The term is automatically included in every new project and included in document output by default.
• Optional: The term is added to the project in an excluded state. It will not appear in generated documents unless a user manually includes it on a per-project basis.

Terms are assigned to a project when it is created. You can override inclusion on a per-project basis at any time.

Inserting Plain Text vs. Formatted Text

Terms and Conditions can be inserted into documents in two ways, both using merge fields:

• Plain Text: Works like any other “each” item. Use the content key under each terms_and_conditions item in your merge data to access the plain text version.
• Formatted Text: Allows you to insert terms with markdown formatting applied, similar to text blocks. Use the formatted_content key to access this version.

For example, prefixing a term heading with ## in the formatted text version will render it in the H2 style defined in your document template. With the plain text method, markdown syntax appears as literal characters.

On this screen: The term creation or editing form shows a Name field at the top, followed by a rich text editor for the term content. The editor uses the unified toolbar with bold, italic, list, and other formatting controls. A Submit button saves the term.

When ready, press Submit to save.

Terms and Conditions in a Project

Within a project, you can see all terms present on that project — generally the terms that existed when the project was created.

On this screen: Within a project, the Terms and Conditions section lists all terms that were applied at project creation. Each row shows the term name and an included/excluded status indicator. Users with appropriate permissions can click any term to override its content for this project, or toggle its inclusion state.

With appropriate permissions, you can:

• Override the content of any term on a per-project basis
• Include or exclude any individual term for that project

Terms set to Optional in Settings are excluded by default and must be manually included on each project.

Client, Business Unit, and Vendor-Specific Term Overrides

On a per-Client, per-Business Unit, and per-Vendor basis, you can create specific term language or remove a term from your work statement entirely.

Order of Application

Terms are applied to projects in this order, and each step overwrites the one before it. The last to apply wins:

1. Standard terms for the account are applied first
2. Business Unit conditions are applied next
3. Client conditions are applied after that
4. Vendor conditions are applied last, for each active vendor quote on the project

So a vendor condition overrides a client condition, which overrides a business unit condition, which overrides the account standard.

Accessing Override Settings

• Clients: Go to Settings > Users & Groups > Clients and click the client you want to modify. If the client isn’t listed, create a project for them first, or click + Add Client.
• Business Units: Go to Settings > Users & Groups > Business Units
• Vendors: Go to Settings > Users & Groups > Vendors and open the vendor’s Terms & Conditions tab

Modifying Terms for a Client, Business Unit, or Vendor

Once you’ve opened the element you want to modify, click the Terms & Conditions tab. You’ll see the complete list of terms. Unless overridden, these will be the account-level terms.

On this screen: The Terms and Conditions tab on a Client, Business Unit, or Vendor detail page shows the complete list of account-level terms. Each term name is a clickable link that opens an inline editor to override its content for this entity. A “Skip T&C” button next to each term removes it entirely for this entity. Skipped terms show a “Restore T&C” option to reinstate them. Overridden terms display an X in their context menu to revert to the account default.

To modify a specific term, click it to open a text editor where you can change its content for this client, business unit, or vendor. To remove a term entirely, click Skip T&C. Once skipped, you can restore the term at any time by clicking Restore T&C.

To clear an override you’ve created, hover over it and click the X in the context menu. This reverts that term to the account-level default.

When finished, press Submit. Press Back at any time to cancel.

Permissions

Two permissions control access to Terms and Conditions:

• Project Terms and Conditions (projects.terms_and_conditions): Controls whether a user can view, include/exclude, and override terms on a project.
• Settings Terms and Conditions (settings.terms_and_conditions): Controls whether a user can create, edit, and delete terms in Settings > Content > Terms and Conditions.