User guide
Getting started
From an empty account to a completed story in about fifteen minutes. This is the happy path - each step links to the page that explains everything else that is possible there.
-
Create your account
Register with a username, email address, your name and a password, then click the activation link in the email we send. If a teammate already invited that email address to their organization, signing up claims the invitation automatically - it waits behind the Review invitations banner on your settings page (Account → Settings).
Or skip the form: the sign-in page offers Sign in with Google and Sign in with Microsoft. If no account exists yet for the address the provider vouches for, the button creates one and logs you straight in. With a verified address (Google always; Microsoft when your tenant asserts it) there is no activation email to wait for - otherwise the link arrives just like the form's. If an account does exist, the button links to it or logs in; it never creates a duplicate.
-
Sign in
Log in with your username or email address - or press the same provider button from step 1, if that is how you signed up. You land on Work, the page that lists every project you can see across all your organizations. If your organization enforces multi-factor authentication, you will be asked for a code - see Account and security.
-
Create an organization
Open Account → Organizations and choose Create organization. Give it a name, a URL slug, its type and a default timezone. The slug is the address your team works under (
/o/acme/…) and it cannot be changed later, so keep it short and boring. You become the organization's Owner. Everything - projects, work items, channels, settings - lives inside exactly one organization. -
Invite your teammates
On the organization's Members page choose Invite User: their email address and a role. Member is the everyday choice; External collaborator limits a person to the specific projects you pick. They receive an email, register (if they have not already) and accept. Working solo? Skip this step entirely. The roles and the outside-collaborator pattern are covered in Organizations and people.
-
Create a project
On Work, choose New project. The two fields that matter are the name and the key: the key prefixes every item reference in the project, so a project keyed
ENGproduces items namedENG-1,ENG-2… everywhere you look, link and paste. Pick the organization and a starting status; you can refine the rest later. -
File your first story
Open the project and choose New work item. Name it, set the type to Story, and describe it in markdown - formatting, lists and code fences all work. Leave the priority at the organization's default. The story appears at the top of the backlog as
ENG-1, already carrying its own discussion thread. -
Break it into tasks
Open the story and choose New child item to file a Task under it. Out of the box an Epic holds Features, Features hold Stories, and Stories hold Tasks and Subtasks - if a type is not offered as a child, your organization's hierarchy rules are why, and Project configuration shows how to change them.
-
Do the work
Assign the task to yourself on the story page. On the Board, drag its card from New to In Progress - or use the status selector on the card, which is what keyboard users (and the transition rules) prefer. Statuses the organization's transition list does not allow are disabled, not hidden, so you can always see the shape of the workflow you are moving through.
-
Talk where the work is
Every work item carries a discussion thread:
@nameyour teammates to notify them, drop files in as attachments, and keep the decision next to the thing it is about. The same threads exist for projects and for channels - see Collaboration. -
Complete it
Move the task to your organization's review or done status. A parent with Derive status from children switched on follows its children on its own: it stays in progress while any child is open and completes when every child is terminal - and reopens if a child does. Commits and pull requests can ride along as delivery evidence; Integrations and AI agents covers how.