Skip to content

Briefs and notes

Writing strategy notes, campaign briefs and content pillars, how every save becomes a new immutable version, and what marking a note "client" actually means.

Updated

Notes hold the thinking behind the work: strategy notes, campaign briefs, content pillars and meeting records. They live in a workspace and are not attached to a campaign or a content item.

Every save is a new version, and earlier versions are never overwritten. The version number is on the list, and the history is on the note.

Visibility is the other thing to get right. A note is internal by default, meaning only people with workspace access can read it. Marking one "client" makes it readable outside your organisation, and that is why changing it is a decision the product treats as a disclosure rather than a formatting choice.

BEFORE YOU START

  • The "create" permission to write a note, and "edit" to save a new version or change its visibility.
  • Access to the workspace.
  • Nothing else to read them. Several roles reach this page without being able to write: approver, publisher, analyst, community manager, client reviewer, billing admin and read-only.

STEPS

  1. Open Notes for the workspace, or go to /app/workspaces/{workspace}/notes.
  2. Type a title and add the note. The form starts on brief, and note, pillar and meeting are the other three types.
  3. Open the note to write the body.
  4. Set its visibility: internal, or client if it is safe to share externally.
  5. Save. The version number goes up by one and the previous version is kept.
  6. Follow the comments link on a note to discuss it with the team.

WHAT YOU SHOULD SEE

The note listed with its type, its visibility and its version, and the editor showing every earlier version.

WHAT THIS WILL NOT DO

  • It will not overwrite history. Nothing you save replaces what was there.
  • It will not attach a note to a campaign or a content item. Notes belong to a workspace and nothing else.
  • It will not let a viewer write. Where you lack the edit permission the editor shows why and drops the save button rather than failing when you press it.
  • It will not share a client note by itself. Marking it client makes it readable by somebody holding a review link; it does not send it anywhere.

IF IT DOES NOT WORK

  • "create permission required." and "edit permission required." are the refusals. Note that the edit check happens before the note is looked up, so a refusal tells you nothing about which notes exist.
  • "You do not have access to this workspace."
  • "That note could not be added, so nothing was created." is precise: nothing was half-made. What you typed is still in the form.
  • On mobile, "The request did not complete, so it is not known whether that note was saved. Reload to check." means check before saving again.

COMMON QUESTIONS

Can I restore an old version?

The versions are all kept and readable. Copy from the one you want and save it as a new version.

What is the difference between a note and a comment?

A note is a document. A comment is a remark about a record, including about a note.

  • Commenting on work

    Leaving threaded comments on a note, a content item or a task, mentioning teammates, and the difference between an internal comment and one a client can read.

  • Tracking tasks

    Keeping a workspace's tasks on a board or in a table, working a checklist, and which task fields exist behind the API but have no control in the product.

  • Grounding content in sources

    Adding a webpage or your own notes so generations can cite them instead of inventing a claim.