Path: /docs/guides

Short workflows for everyday Orchestrator use.

Boards and tickets

See Board for the full desk. Short version:

1. Open /projects/{CODE}/board.
2. Create cards, drag between columns, open a card for detail.
3. Prefer project codes in bookmarks (GDADMIN, ORC), not database ids.

Process changes belong on Custom Workflows (/projects/{CODE}/workflow).

Switch teams without breaking the board

1. Pick another team in the sidebar.
2. If that team can access the same project, the board stays open on /projects/{CODE}/board.
3. If it cannot, you return home. Create or open a project under that team instead.

Team context stays in cookies. Do not put account ids in the URL.

Account members and roles

Role	Typical access
Owner	Full org control, billing, members
Admin	Invite members, change roles, manage projects
Manager	Project and board operations
Member	Contribute on projects

Manage roles at /admin/account/members with the correct team selected.

Sign in tips (GitHub)

• Use a verified GitHub email.
• Allow that email on OAuth apps in GitHub Settings → Emails.
• If you were invited by email, GitHub must expose the same address or use email/password once, then link GitHub later.

Agents and automation

Cursor and CLI agents should use MCP Bearer tokens, not browser cookies.

1. Create an API token in the product (Account / API tokens).
2. Put Authorization: Bearer <token> in Cursor MCP config.
3. Call tools such as ticket.list with an explicit projectCode.

Full tool list: MCP Server.

Related

• Getting Started
• Integrations
• API Reference