Agreements
The templates agreements with accounts are made from: data processing agreements, NDAs, consent to support from other countries, or anything else you have accounts sign. They are under Settings → Agreements, in the Workspace group.
Who can use it
| Who | Can |
|---|---|
| Service Delivery Manager | Create, change and archive templates (agreement.manage). |
| Account Manager | Pick from the templates when adding an agreement to an account (agreement.write); not change them. |
| Administrator | Everything. |
A new template
New template offers three starters and a blank page:
| Starter | For |
|---|---|
| Data processing agreement | GDPR article 28: the purpose, the kinds of personal data, whose, where, and the processor's duties. |
| Non-disclosure agreement | Both sides keep what they share confidential, for a number of years. Valid for 36 months. |
| Support from other countries | The account agrees that staff in more countries may handle its requests. Valid for 12 months. |
| Blank | Your own text and fields. |
[!WARNING] The starters are a starting point, not legal advice. Have whoever handles your contracts check the text before anyone signs it.
Editing a template
| Field | What it is |
|---|---|
| Name | The template's name, which is also each agreement's title. Unique. |
| Valid for | Months from signing; agreements expire after. Empty: until withdrawn. Each agreement can set its own date instead. |
| Description | Shown when someone picks the template. |
| Fields | What is filled in when the agreement is added to an account (below). |
| Text | The agreement, in Markdown, with {{key}} where a field goes. Preview shows it as it will read, with each field by its label. |
Fields
Each field has a Label, a Key (lower-case letters, digits and _, used in the text as {{key}}), a type, and
whether it's Required:
| Type | Is filled in with |
|---|---|
| Text | One line. |
| Long text | A few lines. |
| Date | A date. |
| Number | A number. |
| Choice | One of the options you list. |
{{account}} (the account's name) and {{organization}} (your organization's) are filled in for you, and can't be
field keys. The text can only use fields that exist. An empty optional field leaves no blank paragraph.
Versions and archiving
Changing the text or fields makes a new version; the list shows it (v2). Agreements made before keep the text they
were made with, and say which version.
Archive takes a template out of the list offered for new agreements; agreements made from it stay as they are. Show archived lists them, and Restore brings one back. Templates aren't deleted, so every agreement can say where it came from.
Creating, changing, archiving and restoring templates are in the audit log.