Overview
Create public, customers-only or internal updates with categories, periods, attachments and controlled publishing.
Problem
Stakeholders need current project progress while internal and customer-facing information may have different visibility requirements.
Solution
ProjectBoard stores update visibility as part of the content model and exposes published content through project timelines, customer update feeds and registered public update pages.
How it works
Authors write and preview an update, choose visibility and notification policy, attach supporting files, and publish immediately or through the scheduled queue.
Who is this for
Project Manager
Operations
Customer Experience
Expected outcomes
- One project timeline for progress communications
- Consistent visibility controls on update content
- Reusable published-update events for workspace workflows
Key metrics
Updates published from one source
40 %
95 %
Time to publish a stakeholder update
45 minutes
10 minutes
Updates with explicit visibility
50 %
100 %
Gallery
Security impact
- Project update body, visibility, category, period, attachments and publishing metadata · PII: workspace project data and optional trusted analytics identity context
Compliance
- RouteGuard and update permissions for authoring
- Visibility enforcement in customer/public presentation paths
Availability & next steps
Starter
Pro
Business
Enterprise