Notes and activity

Notes

Open the person's profile in Entity and scroll to Notes & activity. It shows a "Team-only — never shown to the contact" label right on the panel, because that is exactly what it is: a comment thread staff can write about a person, never surfaced to that person even where they have their own login (a contractor viewing their own profile does not get the panel at all — the page withholds it rather than showing an empty box).

Type in the composer at the bottom — it always prompts "Add the first note…", even once the thread already holds others — and press Post, or ⌘/Ctrl+Enter. The toolbar supports bold, italic, underline, a bullet list and links. Pasted text always comes in as plain text — formatting has to be applied again from the toolbar, so a note can never carry styling copied in from somewhere else by accident.

If the person already had a note under the old single-note field, it still shows — pinned as the first row, labelled "Legacy note", with no timestamp because none was ever recorded for it. It is read-only: new notes go through the thread below it.

Older activity loads on demand: a Show earlier activity button appears once there's more before what's currently shown.

Ratings and polls

The composer has a segmented Entry type control — Comment, Rating, Poll — next to the toolbar. A rating asks what is being rated and a 1-to-5 star score. A poll asks a question and 2 to 8 options; anyone who can see the thread can vote, and the tallies update on the row. Both post into the same thread as an ordinary note, in order with everything else.

Mentions

Typing @ in a note opens a picker of people who can see the thread — every non-contractor member of the org, since contractor accounts are excluded from the audience entirely. Selecting someone sends them an in-app notification with a link straight back to the note. A mention names a person for that notification; it does not create any link or reference to a record elsewhere in the app.

The activity timeline

Interleaved with notes, in the same thread, are system rows the app writes on its own: profile-link updates, rate-card approvals and declines, being added to, removed from, put back on, RSVPing to, or checking in at a gig, group membership changes, and outbound-email events (sent, bounced, marked as spam). Each renders as one plain-language line — for example "Registered for Summer Gala as guest" — naming what happened and, where relevant, who did it, but never the values that changed on a field. At the top of the merged history, a synthesized "Created" row marks how the person first entered the directory (added manually, from a gig registration, from a roster quick-add, or by an import).

This is deliberately not a full edit history. Ordinary field edits on a person's record are not logged here or anywhere else — the timeline exists to answer "what happened with this person," not to audit every change to their data.