Conversation reference¶

The rules the guides to a project's conversation share, in one place.

Who can write¶

Role	Writes in a project's conversation
Owner, administrator, billing role	Yes
Any branch or project role, viewers included	Yes
Auditor	No. An auditor who also holds a branch or project role writes through that role.

A note or comment changes no survey data, so a viewer can answer a colleague who asked them something.

Place	What it shows
The project page's Project notes	Only notes about the whole project
The map's Conversation panel	Every thread in the project, including those on files and map objects
A map object's Conversation tab	The threads about that object
A file's Threads	The threads about that file

Limit	Value
Names in one note or comment, teams included	20
People one note or comment can tell	300
People one sender can tell in an hour	300
People an organisation can tell in a day	5,000
Characters in one note or comment	10,000

Where	Who is told	The card's reason line
A project with people assigned to it, under About this project or as its lead, contributors and viewers	Those people, if they can take part in its conversation. Colleagues who reach the project only through their branch or organisation role are not told.	The people assigned to this project and its members.
A project with nobody assigned	Everyone in your organisation who can take part in its conversation	Nobody is assigned to this project, so @All notifies everyone in the organisation who can take part.
A thread visible to the client	The above, and the client's reviewers who can read the thread, listed with their company, for example Client · Kestrel Builders	This conversation is visible to the client, so its reviewers are included.
A private group	Everyone in the group now	None; the heading reads, for example, Everyone in Harbour site team (5)
A direct conversation	@All is not offered	None

You are never told by your own @All. A client reviewer is never told by an organisation-wide @All and cannot use it.