Project Activity
Activity is the shared timeline for a project. It combines authored updates and comments with automatic changes to dates, status, staffing, and ownership.
Project managers, account managers, and workspace members with allocated hours on the project can post updates and manage conversations. Any workspace member can post comments and replies. Comment and reply authors can edit or delete their own messages.
Use an Update for a formal delivery check-in. It records project health and can include a title, message, mentions, and images. Use a Comment for lightweight project-wide conversation that should not change health. Replies keep follow-up discussion attached to the relevant update or comment.
Health Statuses
| Status | Meaning |
|---|---|
On Track | Delivery is progressing as expected. |
Needs Attention | Something needs review, a decision, or a small adjustment. |
Understaffed | The project needs more capacity, a PM, or missing capability coverage. |
Off Track | A material issue needs immediate attention. |
Posting an Update
Post an update when:
- A weekly status review happens.
- A project health value changes.
- Dates or staffing change materially.
- A risk becomes visible.
- A decision needs to be recorded for the team.
Good updates are short and specific: what changed, what it means, and what action is needed.
Project managers, account managers, and workspace members with allocated hours on the project can post updates.
The composer keeps separate browser-session drafts for updates and comments by project and user. Switching between Update and Comment, or refreshing the page in the same browser session, restores the unsent draft.
Comments and Replies
Any workspace member can post a project comment. Use comments when the message applies to the project broadly but does not need a health status. Any workspace member can also reply to an update or comment when the conversation depends on that message. Comments and replies must include text, a mention, or an image; blank messages are not saved.
Activity conversations are one level deep: replies cannot have replies of their own. Select Add reply or the reply count to reveal a conversation. The timeline initially loads the latest 10 replies for each visible post; use View earlier replies to load older replies in pages of 25.
Project managers, account managers, and members with allocated hours can resolve a conversation when it no longer needs attention and reopen it later. A reply from one of those project participants reopens a resolved conversation automatically. Comment and reply authors can edit or delete their own messages; project updates remain an immutable health record. Deleting a top-level comment also deletes its replies.
The actions menu can copy a direct link or the complete conversation as Markdown. Use Command/Control+Enter to post from an editor. In a reply editor, add Option/Alt to post and resolve the conversation.
Project Activity comments are separate from assignment comments. Assignment comments stay attached to a workload assignment and keep their existing recipients and notification settings.
Notifications
When a new update is posted, Supervisible can notify subscribed users in Inbox, email, and Slack DM. Project channel notifications can also post selected events to a mapped Slack channel. Comment and reply notifications are not delivered yet.
The project notification bell lets each user choose which events they personally want for that project:
- Project updates.
- Date changes.
- Status changes.
- Health that needs attention.
The user's global notification preferences decide whether those selected project events arrive in Inbox, email, or Slack DM.
Update Reminders
Users who can manage the project can set an update reminder schedule from the project notification bell. Schedules can be weekly, every two weeks, or monthly, with a local time and time zone.
Scheduled update reminders go to the project manager and open the project Activity page ready to compose. They run only while the project is Active; draft, planned, completed, and cancelled projects keep the schedule but pause reminders until the project becomes active again.
Target date reminders are separate from update schedules and personal subscriptions. For every Active project, Supervisible includes organization owners, admins, and managers plus the project manager and effective account manager at 30 days before, 15 days before, the target date, 7 days overdue, and 30 days overdue. Each stage is sent once for a target date, and the lifecycle stops after the final overdue reminder.
Inbox, email, and available Slack DM delivery begin enabled for these accountable roles. Each person can turn any method off under Target date reminders, while mapped project Slack channels can enable or disable the shared reminder separately. Opening the reminder takes you to the project so you can change the target date, update its status, or review staffing.
Recent History
Activity automatically loads older authored posts and system events as you scroll, without numbered pages. Replies load independently inside each conversation. Existing links to the former /updates route remain supported, while new links use /activity.