Publishing a meeting's records
The organiser sends each decision, task and blocker to an organisation, engagement, opportunity or contact page; Pulse suggests destinations and anywhere the organiser may read is one.
It is the organiser's act
Reading a meeting does not grant publishing. Seeing the suggested destinations and sending a record are the meeting organiser's; a workspace admin can too, even on a restricted meeting.
How it works
Pulse suggests destinations
An organisation, engagement, opportunity or contact; often several. Suggestions are built with the reader's own eyes and leak nothing.
You choose
From the shortlist or anywhere else you may read; search is right there.
The record lands
On each destination's page and in the team's work stream, once per destination; republishing never duplicates, even after an edit.
Not every kind publishes
Only records with a twin in the platform, decision, task, blocker, idea, risk, potential and comment, publish. A kind without a twin is refused rather than approximated.
Read this next
- MeetingsThe names a meeting recognisesEvery transcript page is matched against your contacts, organisations, opportunities, engagements and services; when a name is ambiguous, Pulse asks.
- Contacts & engagementsNotes, replies and decisionsThe three things you write into a feed, and how they differ in practice.
- MeetingsWho can see a meetingA meeting is private for its whole life. Access is granted one person at a time.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.