Skip to main content
A project is the top-level container in Orbit. It brings together issues, members, roles, labels, saved filters, settings, integrations, automation, and a shared activity history. Project access is membership-based. Each member has one base tier and can also receive project-specific custom roles. See Roles and permissions for the access model and Manage members and roles for invitations and ownership.

​
Fields

  • Name — the project’s display name
  • Slug — a URL-friendly identifier generated automatically from the name when the project is created
  • Description — optional free text
  • Color — one of ten fixed colors (red, orange, yellow, green, lime, blue, sky, violet, purple, pink), used to visually distinguish projects in lists and the sidebar
The slug is generated once, from the name, at creation time. Renaming a project later does not regenerate its slug.

​
Table columns

Each project has its own configurable set of visible columns for its issue List view. You can show or hide: ID, title, status, assignee, priority, labels, updated date, start date, and end date. This preference is stored per project, so two projects can show different columns.

​
What belongs to a project

  • Issues — every issue is created inside a specific project
  • Project labels — the names, colors, and descriptions available for categorizing issues
  • Saved filters — reusable filter combinations, scoped to the project they were created in
  • Activity log — recent changes from project members, visible in the Activity view
  • Members and roles — the people who can access the project and the permissions they receive
  • Integrations — project-specific connections to Discord, Jira, GitHub, and other services

​
Creating a project

Any authenticated user can create a project. Its creator becomes the Owner with full project access. Orbit also offers guided project setup to a user who does not yet belong to a project.
Last modified on September 26, 2026