What are Private Posts?
Private announcements that:- Only appear to logged-in team members
- Never show on public portal
- Don’t appear in embeds
- Stay within your workspace
Creating Private Posts
- Create announcement as usual
- Before publishing, toggle Private post
- Publish normally
- Only your team can see it
Private posts are great for internal release notes, team updates, or documenting decisions.
Use Cases
Internal Documentation
- Architecture decisions
- Process changes
- Team reorganizations
- Strategic pivots
Pre-Launch Communication
- Beta feature documentation
- Internal testing notes
- Early access information
- Rollout plans
Sensitive Updates
- Security fixes before public disclosure
- Customer-specific features
- Partnership announcements
- Financial updates
Visibility Rules
Who Can See Private Posts
| Role | Can View | Can Create |
|---|---|---|
| Admin | ✓ All private posts | ✓ Yes |
| Maker | ✓ All private posts | ✓ Yes |
| Contributor | ✓ Published only | ✗ No |
Where They Appear
- ✓ Announcements list (for team)
- ✓ Internal team views
- ✗ Public portal
- ✗ Embed widgets
- ✗ RSS feed
- ✗ Email subscriptions
Best Practices
Clear Titles - Mark as “[Internal]” for clarity Rich Documentation - Use full formatting since only team sees it Link Freely - Reference internal tools and documents Archive Old Posts - Keep list manageableConverting Posts
Make Private Post Public
- Edit the announcement
- Toggle off Private post
- Update and publish
- Now visible to everyone
Make Public Post Private
- Edit the announcement
- Toggle on Private post
- Update
- Removed from public view
Team Communication
Use private posts to:- Document feature decisions
- Share Sprint retrospectives
- Announce team changes
- Celebrate internal wins