Projects: team workspaces with channels and tabs
How Projects work in Pindown: team workspaces inspired by Discord (sidebar, channels) and Obsidian (a growing vault)—with tabs for pins, pages, pinboards, showcases, canvases, and pitches.
A Project is where you keep one piece of work together—the docs, boards, decks, and conversations that belong to the same client, launch, or team effort.
Instead of jumping between a Page here, a Pinboard there, and chat somewhere else, you open /projects, pick a project, and work inside channels. Each channel is a dedicated area for that part of the work.
Pages are for reading. Pinboards are for scanning. Pitch and Showcase are for presenting. Projects are the home base—where your team lands, finds the right tab, and stays in context.
The layout takes inspiration from Discord and Obsidian:
- Discord — a sidebar of projects (like servers), channels inside each one, and optional categories to group them
- Obsidian — a vault you keep building: notes and assets in one place, linked and reusable instead of scattered files
In Pindown, channels are not limited to chat. A content channel holds pins, pages, pinboards, showcases, and your other formats—so the Discord-style structure meets the Obsidian-style habit of growing one workspace over time.
What a Project is
A Project combines:
- A project home — one workspace per job (a client account, product launch, internal program) with members and settings
- Channels — separate areas inside the project:
- Categories — group channels (Planning, Delivery, Client, Research) so bigger projects stay easy to browse
- The same pins everywhere — attach workspace assets to a tab; update a pin once and every tab that uses it stays current
Think of a Project as the folder above formats: the Page, Pinboard, or Pitch still does its job; the Project gives it team access, structure, and one link to share.
When to use a Project
- Client workspaces — briefs, dashboards, decks, and discussion for one account
- Launches — roadmap Page, status Pinboard, teaser Showcase, and team chat in one place
- Internal team hubs — research, ops, or enablement with a channel per topic
- Cross-functional work — design, product, and stakeholders see the same pins without copy-pasting into Slack
- When one format is not enough — you need a Page and a Pinboard and a place to talk about both
Project vs Page vs Pinboard vs Pitch
| Format | Scope | Best for |
|---|---|---|
| Project | Multi-channel team workspace | Clients, launches, ongoing team work |
| Page | One readable document | Specs, memos, compiled briefs |
| Pinboard | One grid of pins | Review, monitoring, comparison |
| Pitch | Tabbed narrative deck | Live meetings, fundraising, sales depth |
| Showcase | Quick swipe slides | Teasers, highlights, email links |
Rule of thumb: use a Page or Pinboard when you know the one deliverable you need. Use a Project when the team needs several formats and conversation under one roof.
Getting started
- Open /projects and create a project—name it after the client, launch, or team effort (not a single doc).
- Add channels: a content channel for docs and dashboards, chat for quick messages, forum for longer threads.
- Inside a content channel, create tabs and attach pins, pages, pinboards, or showcases—or create new ones from the tab.
- Invite teammates from project settings (view vs edit).
- Draft pins from /home, then attach them to the project tab that needs them.
Frequently asked questions
How is a Project different from a Pinboard or Page?
A Page or Pinboard is one format. A Project is the workspace that holds many of them—plus chat and forum—organized by channel and tab.
Can one tab hold a whole Page or Pinboard?
Yes. A tab can attach individual pins or an entire Page, Pinboard, Showcase, canvas, or Pitch—same idea as Pitch tabs, but inside a team project.
Do I need a Project for every pin?
No. Standalone pins, pages, and pinboards work fine on their own. Create a Project when people, channels, or multiple formats belong to the same job.
Can I share a Project externally?
Share paths exist for project previews; use project settings and roles to control access. For a one-off public link, a shared Page or pin is often simpler.
Where should I start if I'm new?
Read the Quickstart, build a few pins from /home, then create a project and attach your first Page or Pinboard to a content tab.