/
Projects
Projects are the primary way to organize work in Project Feed. Each project has its own feed, tasks, files, and settings — giving your team a dedicated space for every initiative, product, or area of work.
How Projects Work
A project is a container for posts, tasks, and files that share a common purpose. When you create a post, you assign it to a project (or leave it as “General”). Tasks belong to a project, and all media uploaded within a project’s posts appears in its Files tab.
Projects can be public (visible to all workspace members) or private (visible only to invited members). Each project gets its own URL slug, color, optional header image, and external links.
Browsing Projects
Click Projects in the sidebar to see all projects in your workspace. Each row shows the project color, name, description, contributor avatars, post count, and creation date. Private projects display a lock icon next to the name.
Archived projects are hidden by default. Toggle the Archivedbutton in the toolbar to reveal them — they appear at reduced opacity with an “Archived” badge.
Creating a Project
Click the New Project button in the top-right corner of the projects page. By default, any workspace member can create projects. Owners and admins can restrict this to admins only in workspace settings.
- 1.
Name & URL
Give the project a name. A URL slug is auto-generated from the name (lowercase, alphanumeric, dashes only). You can customize the slug before creating. The project will be accessible at
/your-org/projects/the-slug. - 2.
Description
Add an optional description to help teammates understand the project’s purpose. This appears in the projects listing and in the project header.
- 3.
Choose a Color
Pick from eight preset colors. The color appears as a dot in the projects list, in the project header, and on post cards across the feed.
- 4.
Set Visibility
Choose Public (all workspace members can view and post) or Private (only invited members have access). When set to private, a member picker appears so you can add initial members.
Inside a Project
Click any project to open its dedicated page. The project page has four tabs: Feed, Tasks, Files, and Settings (admin only). The active tab is stored in the URL, so you can bookmark or share a specific view.
Feed Tab
The default view. Shows all posts belonging to this project in reverse chronological order, grouped by date. A quick post composer sits at the top, pre-selected to this project. You can filter by author, tags, or date range.
Tasks Tab
A full task management view scoped to this project. Includes the same list, board, and timeline views as the workspace-level tasks page, but filtered to this project only. Creating a task here automatically assigns it to the project. See the Tasks documentation for details.
Files Tab
A media gallery of all files uploaded to posts in this project. Files are displayed in a responsive grid and can be filtered by type: images, videos, audio, 3D models, animations, and sprite sheets. Click any file to open it in the lightbox viewer. Empty file types are hidden from the filter chips automatically.
Settings Tab
Only visible to workspace owners and admins. Provides full control over the project’s configuration — see the Project Settings section below for details.
Header Image
Projects can have an optional header image that appears as a banner at the top of the project page. The banner starts at full height and collapses as you scroll, with the project name and links overlaid on a gradient.
Upload a header image from the Settings tab. Supported formats are PNG, JPEG, GIF, and WebP. Images are automatically optimized to AVIF format (max 1920×1080, under 500 KB) for fast loading.
Project Links
Add up to five external links to a project — repositories, documentation, design files, communication channels, or any URL. Links appear as pill buttons in the project header, giving teammates quick access to related tools.
Each link has a type (which determines the icon), a label, and a URL. Links can be reordered by drag and drop in the settings editor.
Website
Your project's homepage or landing page.
GitHub
Source code repository.
Discord
Community or team server.
Docs
Documentation site.
Twitter / X
Social media presence.
Figma
Design files and prototypes.
Notion
Wiki or knowledge base.
Linear
Issue tracker.
Slack
Team communication channel.
Custom
Any other link with a custom label.
Project Colors
Every project has a color that identifies it across the interface — in the projects list, the project header, post cards, and task views. Choose from eight presets when creating or editing a project.
Blue
Green
Amber
Red
Purple
Pink
Cyan
Orange
Visibility & Access
Projects are either public or private. Visibility can be changed at any time from the project’s Settings tab.
- Public Projects
- All workspace members can view and contribute. No member management needed — everyone has access automatically.
- Private Projects
- Only explicitly added members can view and contribute. A lock icon appears next to the project name throughout the interface. Members can be added during creation or later in settings.
Member Roles
Private projects use three roles to control access. The project creator is automatically assigned as an admin. Roles can be changed at any time by a project admin.
Admin
Full access to project settings, members, and danger zone actions like archiving and deleting.
Editor
Can create and edit posts, tasks, and files within the project. Cannot change settings or manage members.
Viewer
Read-only access. Can view posts, tasks, and files but cannot create or edit content.
Project Settings
The Settings tab (visible to workspace owners and admins) gives you full control over the project. Settings are organized into sections.
- Project Details
- Edit the project name, description, and color. Changes are saved individually per field.
- Header Image
- Upload, replace, or remove the banner image. Drag and drop or click to upload. Images are auto-optimized to AVIF format with compression stats shown after upload.
- Project Links
- Add up to five external links with type, label, and URL. Drag to reorder. Links appear as pills in the project header.
- Visibility
- Toggle between public and private. Switching to private lets you manage individual members and roles.
- Members
- Add or remove members (private projects only). Change roles inline — choose between Admin, Editor, and Viewer.
- Tags
- Create project-scoped tags with a name, optional description, and one of 14 colors. Tags can be promoted to organization-level tags to make them available across all projects.
Posts & Projects
Every post in Project Feed belongs to either a specific project or the “General” category. When composing a post from a project’s feed tab, the project is pre-selected and the project picker is hidden. When composing from the main feed, you choose which project the post belongs to.
Post cards across the feed display a colored dot and the project name, so you can always tell which project a post belongs to at a glance.
Archiving Projects
When a project is no longer active, archive it instead of deleting it. Archived projects are hidden from the default view but all posts, tasks, and files are preserved. You can unarchive a project at any time to bring it back.
Archive a project from the three-dot menu on the projects listing page, or from the Danger Zone section in project settings.
Deleting Projects
Deleting a project is permanent and cannot be undone. All posts, comments, tasks, and media within the project will be permanently removed. Before confirming, you’ll see a count of everything that will be deleted and must type the project name to confirm.
Tip: Consider archiving instead of deleting. Archived projects preserve all content and can be restored later.
Tips & Best Practices
One Project Per Initiative
Create a project for each product, feature, or area of work. Avoid lumping unrelated work into a single project — it makes filtering and tracking harder as the team grows.
Use Header Images
A header image gives each project a visual identity and helps teammates quickly recognize which project they’re in. Use a product screenshot, logo, or brand graphic.
Add External Links
Link to your GitHub repo, Figma files, documentation, or team channel. Having these links in the project header saves teammates from hunting for URLs in chat history.
Use Tags for Categorization
Create project-scoped tags for recurring themes like “bug”, “design”, or “research”. Promote frequently used tags to organization level so they’re available everywhere.
Archive, Don’t Delete
When a project wraps up, archive it. The content stays searchable and accessible for future reference, and you can always unarchive if work resumes.
Use Private Projects Sparingly
Default to public projects for transparency. Use private projects only when the content is genuinely sensitive — HR matters, security work, or pre-announcement features.