Views

Skopo organises work across a set of project views and workspace pages. The exact sidebar labels and available views depend on the active methodology — for example, a Scrum project shows "Sprint Board", "Product Backlog", and "Scrum Events" where a Basic project shows "Board", "Backlog", and no sprint or ceremonies view.

Project views

Dashboard

The Dashboard is the cockpit for a project. It shows methodology-specific KPI cards (total items, velocity, progress, and similar metrics), a burndown or flow chart, a portfolio or needs-attention panel, a recent-activity feed, and a team-workload breakdown. The headline and panels adapt to the active methodology. See /docs/concepts/metrics-and-insights for how metrics are computed.

Board

The Board (segment board) is a Kanban-style column view of all work items in the project. Cards are grouped by workflow column, display type icons, estimates, assignee avatars, PR badges, and blocked or dependency indicators. You can drag cards between columns to change their status and create new items directly from the column header. WIP limits, when configured, are shown in each column badge and can be set to advisory or blocking. See /docs/guides/use-the-board for step-by-step instructions.

Sprint

The Sprint view (segment sprint) is available in methodologies that support time-boxed iterations, such as Scrum and Scrumban. It shows the active sprint's name, dates, status, committed/completed/remaining point totals, and a live burndown chart. Work items are arranged in four columns — To Do, In Progress, In Review, and Done. See /docs/guides/run-a-sprint for step-by-step instructions.

Backlog

The Backlog (segment backlog) is the prioritised list of all unscheduled and planned work. In methodologies with sprint planning the view splits into a sprint-planner layout — upcoming iterations on the left and an unscheduled work rail on the right — so you can drag items between sprints. In non-iteration methodologies the view shows a single queue of unscheduled work. Clicking the estimate chip cycles the item through the Fibonacci point scale. See /docs/guides/manage-the-backlog for step-by-step instructions.

Portfolio

The Portfolio view (segment portfolio) is a hierarchical tree of outcome-level items — epics, bets, goals, or similar, depending on the methodology — with linked work items nested beneath them. Each row shows status, progress, owner, and assignee. You can create portfolio items, attach existing work items from the project, or create new work directly linked to a portfolio entry. The view is only available when the active methodology enables portfolio tracking.

Team

The Team view (segment team) shows the project workforce: people and AI agents, their roles, allocation percentages, and current status. Tabs cover the full project team roster, agent workload and assignment queue, an agent marketplace to hire pre-built agent templates, and an agent audit log of control changes. Workspace owners and project leads can add people, invite by email, and manage allocation and permissions here. See /docs/guides/manage-your-team and /docs/guides/invite-agents.

Rituals

The Rituals view (segment rituals) is a facilitated space for running the rituals your methodology defines, such as sprint planning, backlog refinement, retrospectives, or Shape Up betting tables. You select a ritual type, start a session, mark work items as selected or ready, capture participant lists, and record outcomes including decisions, action items, risks, and dependencies. Session outcomes are saved and can be discussed via the collaboration panel. See /docs/guides/run-a-ceremony.

Delivery

The Delivery view (segment delivery) connects project work to outcome goals, working agreements, quality evidence, and release decisions. Four tabs cover Goals (measurable outcome targets), Artifacts (methodology documents and durable agreements), Quality gates (policy checks with evidence and exception flows), and Releases (readiness gates and release history). A release can only be marked ready when all required gates pass. See /docs/guides/track-delivery.

Insights

The Insights view (segment insights) provides analytics across the project. It shows methodology-specific metric bundles — each metric card displays a computed value, sample size, and freshness status and can be drilled into to see contributing work items and events. Below the metric bundle, summary stat cards and status/type distribution charts give a quick breakdown of the item population. See /docs/guides/read-insights.

Operations

The Operations view (segment operations) tracks delivery risks, durable decisions, and cross-project dependencies. Three tabs — Risks, Decisions, Dependencies — each have their own list with inline status controls, probability/impact indicators, and a collaboration button for threaded discussion. High-impact open risks and active dependencies feed into Delivery view release readiness. See /docs/guides/operations.

Settings

The Settings view (segment settings) is the configuration surface for the project. See /docs/reference/settings for full details.

---

Workspace pages

Workspace pages are accessible from the workspace navigation and apply to the whole workspace rather than a single project.

Overview

The workspace Overview (home) shows a summary of the workspace and its projects. It is the landing page after selecting a workspace.

Members

The Members page lists all workspace members, their roles, and invitation status. Workspace owners can invite new members by email, change member roles, and remove members from the workspace.

Methodologies

The Methodologies page ("Methodology templates") is where workspace owners manage the methodology template library. It displays built-in and custom methodology templates with version badges. Methodology authors can create draft templates and submit them for publishing; methodology publishers can approve and activate new versions. See /docs/guides/build-a-custom-methodology.

Integrations

The Integrations page is where workspace-level external service connections are managed, including repository sync configuration and personal MCP token generation for AI assistants. See /docs/reference/mcp-codex-access for the MCP token setup.