Public Board for Internal Teams: When It Makes Sense
"Public" doesn't always mean the entire internet. Some teams use public boards internally — visible to the company but not to external users. This approach works well for cross-team collaboration, internal tooling, and shared services.
When Internal Public Boards Make Sense
A board visible to your entire company serves teams that handle requests from colleagues:
- Platform and infrastructure teams — Other teams request tooling improvements, new environments, or integrations
- IT and operations — Employees request software, access, or process changes
- Design systems teams — Product teams request new components or pattern updates
- Data teams — Business teams request reports, dashboards, or data exports
In each case, a Linear board shared across the company provides visibility and structure.
The Problem with Internal Requests Today
Without a board, internal requests arrive through:
- Slack messages that get buried
- Email threads with unclear ownership
- Meeting notes that no one follows up on
- Verbal requests in hallway conversations
The requesting team doesn't know the status. The receiving team can't show their workload. Both sides are frustrated.
How an Internal Board Helps
A public board for internal teams provides:
- Request submissions — Teams submit structured requests instead of Slack messages
- Visibility into the queue — Requesters see where their item sits relative to others
- Voting — Multiple teams voting on the same request shows shared need
- Status tracking — Requesters get updates without asking
- Workload visibility — The receiving team can show their capacity and priorities
Setting It Up
Use a public Linear board with access limited to your company:
- Create a Linear project for internal requests
- Connect it to a public board
- Share the link internally (not on your public website)
- Enable submissions and voting
- Triage incoming requests in your normal Linear workflow
The board URL is accessible to anyone with the link, so treat it as internal-only by sharing it through internal channels.
Scaling Internal Services
As your company grows, internal service teams face the same scaling challenges as customer-facing teams. A public board scales request management without adding coordinators. Teams self-serve by checking the board instead of asking for status.