A pin holds a task or a comment at the top of its parent list so anyone opening the onboarding sees it before anything else. Pins are workspace-wide. Everyone sees the same set.
These two surface similar UI (a star, a pin icon) but solve different problems. Pick the right one.
Rule of thumb: pin when the team needs to see something. Favorite when you need fast access.
Open the onboarding, hover the task row, click ⋯ > Pin to top. The task gets a 📌 marker and jumps above all unpinned tasks in that onboarding’s task list. The pin survives task completion (a pinned, completed task stays at the top until you unpin or archive it).
Open the customer or onboarding, scroll to the comment, click the ⋯ > Pin comment. Pinned comments render in a “Pinned” strip at the top of the comments section, separate from the normal chronological thread.
Each onboarding allows up to 3 pinned tasks. Each customer allows up to 3 pinned comments. The cap exists to keep the “look at this” signal meaningful. If you try to add a 4th pin, Pivotal prompts you to unpin one first.
Workspaces with more than ~50 active onboardings should treat pins as a 1-week tool: pin the blocker, resolve it, unpin. Avoid pinning long-running reminders. They lose signal over time and people scroll past them.
Hover the pinned row and click the 📌 icon, or open ⋯ > Unpin. Unpinning a task returns it to its natural sort position (usually by due_date). Unpinning a comment returns it to its chronological slot in the thread.
Any teammate with edit access to the parent record. Read-only roles see the pin icons but cannot toggle them. The audit log records each pin and unpin with actor and timestamp, viewable from Audit log.
Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.