Get into Backlog
Move from the public site into the right signed-in browser, API, or CLI path before you go deeper into the product.
Start with the job you need to get done, then open the exact browser, API, or CLI guide when you need the concrete route, request, or command.
Updated April 3, 2026. The same manual is also available as JSON, plain text, and a sitemap.
These paths reorganize the current manual around the most common entry points without changing the underlying subject matter.
Move from the public site into the right signed-in browser, API, or CLI path before you go deeper into the product.
Use these guides when the next job is finding work, creating tasks, updating task details, or reading project plans.
Go straight to the settings, people, team, token, and shared automation pages that change how a workspace is configured and operated.
Choose the API or CLI path for auth, task creation, personal tokens, automation secret exchange, and visible agent work.
These paths keep the same subject matter but regroup it around the people most likely to need it first.
Get into the workspace, find what needs attention, and move through day-to-day work in the browser.
Go straight to workspace settings, members, teams, personal tokens, and shared automation installs from the right admin surfaces.
Choose the right auth path, confirm context, create work over REST, and operate installs or agents through the API or CLI.
Use the surface manuals when you already know whether the next step belongs in the browser, REST API, or CLI.
Get into the workspace, stay on top of work, and run day-to-day product workflows in the browser.
Authenticate cleanly, confirm workspace context, and automate work safely over the Backlog REST API.
Download the Backlog CLI, authenticate, inspect context, and run terminal-first workflows.
These are the pages readers are most likely to need early, before they branch into deeper task-specific docs.
Open the command palette from the public site or workspace shell and use it as the fastest launcher.
Search the workspace command palette across records, saved views, and runnable commands from any page in the shell.
Review the full command inventory, who can run each action, and what side effect each action has.
Start the OTP flow and send a sign-in code to the correct email address.
Enter the authenticated workspace shell and move into the right surface after sign-in.
Create a task with the right title, ownership, and optional planning context from the start.
Create a task with the right title, ownership, and optional planning context from the start.
Exchange an automation secret for an access token.
These machine-readable formats expose the same public manual in shapes that work better for scripts, agents, and external tools.
Use the root llms.txt file as the project-level agent entry point for Backlog, then branch into docs, product, pricing, or auth context.
Browse the docs hierarchy in an agent-oriented index. Use the linked /README.md routes when you need the actual docs content in raw Markdown.
Use one root-level plaintext file when you want to ingest the full public docs corpus in bulk.
Use the sitemap when you need the current public URL inventory for this manual.