Documentation

The backendup user guide

backendup pairs project tracking with built-in team chat, so this guide follows the two halves of the product: set up your organization and its workflow, then run projects, work items, and conversations in it. The API reference covers the token API your agents and scripts use.

New here

Sign up, create an organization, run your first story.

Getting started →

Setting up a team

Make the workflow match how you actually work.

Project configuration →

Running the organization

Sub-orgs, roles, invitations, outside collaborators.

Organizations & people →

Working with agents

Service accounts, GitHub evidence, AI teammates.

Integrations & AI →

Pages in this guide

Getting started From signup to a completed story: create an organization, invite a teammate, run work across a board. Organizations and people Root organizations and sub-organizations, the org chart, invitations, membership roles, and access for people outside the org. Project configuration The workflow your team actually runs: statuses and transitions, priorities, labels, work-item types, the hierarchy, and automation. Daily work Backlog, board, timeline, iterations, and the life of a work item: fields, status moves, relations, attachments. Collaboration Channels, direct messages, and the discussion attached to every work item - plus the notifications that keep up with them. Search, filters, and export Finding work across organizations, saved filters with their query grammar, and CSV export. Reports Iteration metrics: burndown, velocity, throughput, and cycle time - and how statuses count in each. Integrations and AI agents GitHub delivery evidence, service accounts and organization tokens, and working with agents on the team. Ask AI assistant The in-palette assistant: opening it from anywhere, cited answers that grow stage by stage - the guide, your work read-only, drafts you confirm - and how its pauses work. Usage limits & fair use What the free service limits - and, explicitly, what it never limits: the numbers live on this page because they are the numbers the server enforces. Account and security Your profile, password, MFA and recovery, Google and Microsoft sign-in, and the feedback you send.

Glossary

The words backendup uses on screen, in one place.

Organization
A workspace and the boundary of its data. Projects, work items, workflow settings, channels, and API tokens all belong to exactly one organization, and every page URL carries its slug.
Sub-organization
An organization nested under another one. It keeps its own members, settings, and projects, and it can be moved to a different place in the tree.
Project
The container for work: backlog, board, iterations, attachments, and its own discussion. Every project belongs to one organization.
Category
An organization-defined grouping for projects, such as Backend or Ops.
Work item
A single tracked unit of work with a status, assignee, priority, labels, children, and its own discussion thread.
Kind
The type of a work item. Organizations keep some built-in kinds (Epic, Feature, Story, Task, Subtask, Bug, Investigation, Spike, Improvement, Chore) and can add custom ones.
Container
A kind treated as a grouping shell rather than directly executable work, such as an Epic.
Status category
The semantic bucket every status maps to: To do, In progress, Done, or Cancelled. Your organization names its statuses; the category decides how the app treats them.
Transition
One allowed directed move between two statuses. People and agents must follow the transition graph of their organization when they change status.
Iteration
A time-bounded planning container inside one project: a sprint with a goal, dates, a status, and reports.
Relation
A typed link between two work items: Blocks, Relates to, Duplicates, Causes, or Solves.
Delivery link
Evidence bound to a work item: a commit, pull-request, or compare URL, attached by the GitHub integration or the token API.
Saved filter
A named, reusable query over the work items you can see - kept private or shared with the whole organization.
Discussion
A comment thread attached to a work item, project, or feedback - the same surface channels carry conversations on.
Channel
A named conversation in Collaboration: an organization-wide or team channel, or the discussion wired to a project or work item.
Service account
A machine user an organization creates so an agent or integration holds its own API token and is audited by its own name.