Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
PlanningRoadmapBacklogPrioritiesBoardsOwnershipBlockers
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Ownership

Ownership shows who is responsible for moving work forward and who needs visibility.

Ownership fields

Ownership fields answer different questions. Owner shows accountability, assignees show who is doing the work, and reviewer shows who needs to make a decision or approve the next step.

FieldMeaning
OwnerThe person accountable for moving the work forward.
AssigneesPeople doing or contributing to the work.
ReviewerThe person who needs to review the work.
ReporterThe person who reported the bug, issue, or request.
TeamsThe teams responsible for the work or needing visibility.

Plan with ownership

Plans are stronger when every active item has an accountable person. Ownership fields support board grouping, unassigned work review, triage, standup prep, and blocker review.

The assignee filter on initiatives includes Unassigned, which helps isolate roadmap work that has not been assigned to anyone yet.

When work moves between people, update the owner or assignees instead of leaving the change buried in comments. Status tells the team where the work is; ownership tells them who can move it.

For formal access boundaries, see Permissions.


PreviousBoardsNextBlockers

Backlog

Hold ideas, bugs, and feature requests until they are clarified, prioritized, or declined.

Blockers

Make stuck work visible with the dependency, decision, or missing input attached.

Boards

Coordinate team work across people and statuses in one planning view.

Priorities

Explain what happens next and why one item deserves attention before another.

  • Ownership fields
  • Plan with ownership
  • Back to top