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 Terms and Conditions page has Active and Archived tabs and columns for Name and Required / Optional, in that order. Rows on the Active tab can be dragged to reorder them, controlling their order in documents. + Add A Term or Condition appears in the header. Click a row to edit it, or select rows to use bulk Delete on the Active tab or Restore on the Archived tab.

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 on the Active tab to reorder them. Click + Add A Term or Condition to create a new term. Removing a term archives it, and it can be restored from the Archived tab.

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 Add a Term or Condition or Edit Term or Condition form contains Name, a Required or Optional toggle showing Required or Optional, and a rich text editor labeled Content (Supports Markdown). The editor provides formatting controls for the term content. Save and Cancel appear in the header, with Save and Add Another when creating a term.

When ready, press Save 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: The page is titled with your account’s label for Terms and Conditions. Each term appears as its own row with the term name, an Included / Excluded toggle with an information icon beside it, and below that an always-open text editor holding the term’s content for this project. When a term is excluded, its editor is grayed out and cannot be edited. Save appears in the header only while the project is in the building status.

With appropriate permissions, you can:

• Override the content of any term on a per-project basis. Edit the text in the term’s editor, then click Save.
• Include or exclude any individual term for that project. Flipping the Included / Excluded toggle takes effect right away and does not need Save.

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

The editor below is used on the current client page and on business unit and vendor pages with the Site Navigation V2 beta enabled. Open the Terms & Conditions tab to see active account-level terms with account-level content unless overridden.

If the tab shows a list instead, click a term to edit it, then click Submit to save or Back to cancel. Use Skip T&C or Restore T&C beside a term to change its inclusion. To clear an override and go back to the account-level content, hover over the term and click the X (Remove special T&C); Restore T&C only restores inclusion.

On this screen: The Edit Client, Edit Business Unit, and Edit Vendor pages have a Terms & Conditions tab, which appears only when your account includes Terms & Conditions. The tab lists active account-level terms in order. Each term shows its name, an Included / Excluded toggle, and an always-open text editor with the term’s content (the editor is grayed out when the term is excluded). Cancel and Save appear in the header. If the account has no standard terms, the tab reads “No standard Terms & Conditions are defined for this account.”

To change a term for this client, business unit, or vendor, edit its text directly in the editor. To remove a term entirely, switch its toggle to Excluded. To bring it back, switch it to Included. Until you change a term, it shows the account-level content.

Click Save to apply your changes. ScopeStack confirms with a message such as “Saved 2 change(s),” or “No changes to save.” if nothing changed. Cancel leaves the page without saving.

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.