How to get there: Open any post → look at the meta panel on the right → toggle the Internal switch.
Internal posts let admins track work, ideas, or sensitive issues inside ProductLift without exposing them to end users. An internal post is fully hidden from browse pages, search, direct URLs, RSS feeds, and the API for anyone who is not an admin.
What "internal" hides
When a post is marked internal:
- It is hidden from board listings, kanban columns, and saved queries for non-admins.
- Its detail URL returns "not found" for non-admins, even the user who originally submitted it.
- It does not appear in search results or RSS feeds.
- Its custom field values, comments, and votes are hidden along with it.
- It is excluded from public statistics (vote counts, segment totals).
Admins always see internal posts. They are visually marked with an "Internal" badge so you don't accidentally treat them as public.
Marking a post internal
- Open the post.
- Find the Internal row in the meta panel (right-hand side on desktop, above the content on mobile).
- Toggle the switch to Yes.
A toast confirms the change. You can flip it back at any time, the post becomes visible again immediately according to the normal visibility rules (board, status, moderation).
When to use internal posts
Good fits:
- Tracking a competitor or sensitive bug while you investigate.
- Capturing an idea you want to discuss internally before exposing it for votes.
- Holding a draft of a changelog entry until it is ready (combine with Scheduled Publishing).
- Logging internal action items linked to a public post via Post Linking and Relationships.
Less good fits:
- Hiding a single field from end users. Custom field values follow post visibility, so an internal post hides everything. If you only want to hide one piece of data, use a tag with restricted visibility or an internal comment.
- Replacing moderation. Posts pending moderation are already hidden from end users, you don't need to mark them internal as well.
Internal vs other privacy settings
| Setting |
What it hides |
Who can still see |
| Internal post |
The entire post and all its data |
Admins only |
| Internal comment |
A single comment on a public post |
Admins only |
Unpublished post (is_published = false) |
The post until you publish it |
Admins, and the author |
| Private portal |
Everything on the portal |
Logged-in members of the portal |
Use the lightest tool that solves your problem. Most teams reach for internal posts only for genuinely sensitive items.