LogoLogo
ClausesDatafieldsSpecial FunctionsStylingQ&AAPI
  • Welcome!
  • Getting started
    • What is Clause9?
    • Structuring your clause library
    • Structuring your clauses
    • Drafting modes in Clause9
    • Creating a questionnaire
    • Sample clauses
    • Videos
      • Concepts and datafields
      • Conditions
      • Q&As
      • Binders
      • Styling
      • Enumerations
      • Tables
      • Definitions
      • Snippets
      • Cross-references
      • Special functions
      • Examples of common clauses
      • Import clauses from MS Word
      • Grammatical conjugations
      • Action buttons
      • Alternative clauses
  • Assemble document
    • Document toolbar
    • Clause hierarchies
    • Focus Mode
    • Bulk generation of documents
    • Exporting documents
    • Assemble Document - FAQ
    • How to: Assemble Document
      • Insert images
  • Assemble Document Operations Panel
    • Operations panel
    • File pane
    • Edit pane
    • Document pane
    • Binder pane in the operations panel
    • Search pane
    • Browse pane
    • Terms pane
    • Data dashboard
    • Advanced pane
    • Styling pane
    • Miscellaneous pane
    • Visibility settings & actions menu
  • Binders
    • Binders: general
    • Styling cross-references to subdocuments
    • Global and local definition lists
    • Document and binder properties
    • Styling of a Binder versus subdocuments
    • (Un)locking documents in a binder
    • Binders - FAQ
    • How to: binders
      • Make a subdocument in a binder conditional
  • Clauses
    • Introduction to clauses
    • Clause structure
    • Grammar sheet
    • Writing conditions
    • Examples of conditions
    • Using codes instead of text fragments
    • Bold, italic and underline
    • Special codes
    • Enabled?
    • Links
    • Cross-references
    • Introduction to tables
    • Deviating table styling
    • Shrinking clauses
    • Action buttons
    • Enumerations
    • File position
    • Snippets
    • Parameters
    • Conjugations
    • Mixing data types
    • For-loops
    • Clause versioning
    • Abstract article references
    • Advanced multi-language features
    • Clauses - FAQ
    • How to: clauses
      • Create an ad-hoc clause
      • Create a library clause
      • Make a clause repeat
      • Make a paragraph within a clause conditional
      • Use a shortcut to refer to a concept
      • Insert a line break or page break
      • Creating a list with both predefined options and free input
      • Defining alternative clauses
      • Creating cross-references
      • Creating signature blocks
      • Creating advanced party introduction clauses
      • Automatically numbered annexes or schedules
      • Reuse any clause in a different context
      • Setting MS Word document properties
      • Add action buttons to clauses
      • Electronically signing documents
  • concepts
    • Introduction to concepts
    • Creating concepts
    • Concept labels
    • Links
    • Organising concepts
    • Concepts - FAQ
    • How to: concepts
      • Add predefines to a datafield
  • Datafields
    • Introduction to datafields
    • Types of datafields
    • Rules of thumb for using datafields
    • Data-expressions
    • Datafield aliases
    • Datafield labels
    • Datafield special tags
    • Datafield descriptions
    • Repeating list datafields
    • Datafield predefines
    • Datafields - FAQ
    • How to: datafields
      • Change datafield type
      • Change the datafield's name or alias
  • Definitions
    • Introduction to definitions
    • How to: definitions
      • How do definitions work?
      • Create a definition
  • Files
    • How files are organised
    • Browse files
    • File types
    • Custom styling
    • Legal comments
    • File description
    • Attributes
    • Reporting
    • File name
    • File category
    • Access rights
    • How to: files
      • Creating advanced folders
      • Naming your files
      • Shortcuts to folders or files
  • Q&A
    • About cards
    • Cards pane
    • About changes
    • Changes pane
    • Types of changes
    • Adding conditions
    • Question options
    • Copying & pasting answers
    • Comments, notes & documentation
    • Interactive Q&A inspection
    • Embedding questions into a document
    • “Changes” button
    • Batch create pane
    • Identifiers pane
    • Import pane
    • Edit clauses pane
    • Q&A options
    • Q&A - FAQ
    • How to: Q&A
      • Create predefined answers to a question
      • Add disclaimers
      • Create categories of questions
      • Modify the exported filename
      • Create a question to change the language of a document
      • Send a questionnaire to someone without a ClauseBase account
      • Create questions for repeating list datafields
      • Selecting legal entities & addresses
      • Create a questionnaire using "batch create"
      • Launch other Q&As
    • Leveraging ClauseBuddy Smart Templates in Clause9
  • Import
    • Introduction to importing clauses
    • Uploading clauses
    • Defined terms in Import mode
    • Datafields in Import mode
    • Cross-references in Import mode
    • Assigning folders
    • Conversion process
    • Exporting
    • Stashing intermediate results
    • Tips, tricks & limitations
  • Styling
    • Styling overview
    • Base styling
    • Numbering
    • Definitions styling
    • Enumerations styling
    • Locale styling
    • References styling
    • Page styling
    • Styling of a Binder versus subdocuments
    • Styling: tips and tricks
    • Advanced styling topics
    • Copying headers and footers from an MS Word file
    • How to: styling
      • Using custom fonts
      • Change bullet styling
  • Special functions
    • Introduction
    • Calculations
    • Concepts
    • Conditions
    • Conjugations
    • Content Control Elements
    • Datafields
    • Dates & durations
    • Languages
    • Lists
    • Numbers
    • References
    • Repeating (looping)
    • Special items
    • Text structure
    • Text modification
    • User
    • Q&A
  • Settings
    • Account
    • Preferences
    • Access bundles
    • Favourites
    • Saved searches
    • Saved datafields
    • Styles
    • Default styles
  • Admin
    • General
    • Users
    • User rights
    • Profiles
    • Groups
    • Styles
    • Default styles
    • Attribute models
    • Usage page
    • Custom homepage
    • Global placeholders
    • Access rights
    • How to: admin
      • Adding a new user
      • Disabling a user
      • Managing group memberships
  • Miscellaneous
    • Advanced tips & tricks
    • Typing special symbols on your keyboard
    • Shortcuts
    • Grammar style guide
    • Inserting MS Word files
    • Globo-panel
    • Creating high-quality documents
    • Excel calculations and lookups
  • Integrations
    • Overview
    • Spreadbases
    • E-signing documents
    • Drag & drop integrations
  • For developers
    • Clause9 API
    • Custom functions
    • Example custom functions
Powered by GitBook
On this page
  • Creating a clause hierarchy
  • How to use a clause hierarchy
  • Selecting a clause hierarchy
  • Lock / unlock
  • Editing clause hierarchies
Export as PDF
  1. Assemble document

Clause hierarchies

PreviousDocument toolbarNextFocus Mode

Last updated 7 months ago

A clause hierarchy is a file type that contains a set of clauses in a fixed structure. Clause hierarchies can come in handy when you want one clause with its different levels of subclauses to be available in your clause library as one set. Users can then insert the hierarchy with one single click instead of having to find each individual clause and inserting each one separately.

Except for the special locking & unlocking mechanisms , a clause hierarchy acts like any regular set of clauses when it comes to numbering, cross-references, layout, and so on.

Clause hierarchies can even be nested within other clause hierarchies, any level deep. They can therefore constitute an interesting alternative to using subdocuments, e.g. because subdocuments inherently start on a new page and restart their numbering by default (except if Restart numbering is turned off in the page styling).

Creating a clause hierarchy

A clause hierarchy can be created by selecting a clause in the Assemble Document mode that has at least one clause as its “child” – i.e. at least one subclause. Click the button in the and select Hierarchy of clauses > Save hierarchy as separate library clause. Choose the location where you want to save the hierarchy and give it an appropriate file name.

The end result is that you created a library clause (or, rather, a hierarchy of clauses) and that your current selection will be replaced by a reference to that library clause.

Within Browse files, you can see that hierarchies have a special icon, to indicate that they're actually a stack of clauses bundled together.

How to use a clause hierarchy

Clause hierarchies can be inserted in a document in the same way normal clauses are, i.e. by going to the or and inserting it by clicking . When selecting the hierarchy in the browse pane, a user can also choose to only add one clause that is part of the hierarchy.

After inserting the hierarchy in a document, it will be easily recognisable as a clause hierarchy by the frame surrounding the hierarchy and the lock symbol.

Selecting a clause hierarchy

The frame around the hierarchy can be clicked to select the clause hierarchy. When selected, the clause hierarchy can be moved in its entirety using the arrow buttons in the document toolbar. Make sure you have actually selected the entire hierarchy and not just the parent clause inside the hierarchy.

Lock / unlock

Clause hierarchies – when first inserted – are locked. The fact that the hierarchy is “locked” means the structure of the hierarchy cannot be changed. That means the relative positions of the clauses part of the hierarchy cannot be changed. While changes can still be made to the content and other properties of any library clause, ad hoc clauses cannot be changed. This is due to the fact that the ad hoc clause is tied to the hierarchy itself, while a library clause exists independent of the hierarchy.

After unlocking, ad hoc clauses can be edited and the structure of the clauses inside the hierarchy can be freely changed.

Similar to documents in a binder, clause hierarchies the structure of which has been edited (after unlocking) will no longer be ‘tied’ to the original clause hierarchy and will therefore not include any changes made to the original copy.

Editing clause hierarchies

You can edit an existing clause hierarchy as follows:

  • First unlock the hierarchy by clicking on the lock-icon.

  • Make relevant changes to the structure (e.g., by adding/removing clauses, changing their order or indentation etc.).

  • Select the top-clause again.

  • You will notice that the hierarchy gets its lock-icon again after the save.

Note that Clause9 will not automatically update existing instances of the clause hierarchies in currently opened documents. You will therefore have to close & reopen documents and Q&As that make use of the clause hierarchy that was updated.

To show that it is locked, a clause hierarchy will contain a lock symbol on the frame surrounding it. To unlock the clause hierarchy, click the lock symbol itself: .

For technical details on how the unlocking internally works, see the .

Click on the button in the and select Hierarchy of clauses > Save updated clause hierarchy

discussion forum
Document Toolbar
Search pane
Browse pane
described below
Document Toolbar
Example of how a clause hierarchy looks when it is first inserted into a document.
This is how the hierarchy looks when it is selected.
In this case, only the parent clause inside the hierarchy has been selected and not the hierarchy itself.