AtlasWork, planned itself.

    The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

    • Overview
    • PDF tools
    • Diagram tools
    • People & HR
    • Integrations
    • Marketplace
    • Pricing

    Resources

    • Guides
    • Glossary
    • Compare
    • Docs
    • API reference
    • Support
    • Changelog
    • Status

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
    PrivacyTermsSecurityStatus

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • Necessaryalways on
    • Analyticsopt-in
    • Marketingopt-in
    • Preferencesopt-in
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

    • REST API guide
    • Authentication
    • API reference
    • MCP (AI agents)
    • MCP tools reference
    • SDKs
    • Quick actions
    • Changelog

    Webhooks

    • Overview
    • Quickstart
    • Events
    • Payloads and headers
    • Security and signing
    • Delivery and retries
    • Managing via API

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Module reference

    Module guide

    Tasks

    The atomic unit of work in Atlas.

    Open module/my-work
    corework

    Overview

    A task carries everything a unit of work needs: title, description, priority, status, due and start dates, estimates, assignees, labels, attachments, threaded comments, dependencies, subtasks, custom links, recurrence, reminders, and approval state. Every view in Atlas renders tasks one way or another, so the task is the one object worth learning first.


    Highlights

    The capabilities worth knowing before you dive in.

    • Subtasks with auto-propagating parent status
    • Custom tenant-defined relation kinds (blocks, derives from, enables, or whatever your team calls it)
    • Recurrence via a simple enum or RRULE-style custom rules
    • Approval workflow (PENDING to APPROVED or REJECTED)
    • Deterministic my-day scoring picks your Today's Focus without an LLM

    Important to know

    Limits, permissions, and sharp edges to keep in mind.

    • Status values are lowercase strings (todo, in_progress, done, blocked). Custom swimlanes add their own keys.
    • Versions are an opt-in optimistic lock. If you PATCH with a stale version, the API returns 409.
    • Archived is not the same as deleted. Archive hides a task from default views; delete moves the task to Trash, where it can be restored for 30 days. Deleting also offers an undo for a few seconds straight afterwards.

    How to use it

    The primary workflow, start to finish.

    1. 1Press ⌘K and type the task title to create it or jump to it.
    2. 2Press New task to open the composer. The description is a rich text field: type - for a bullet, 1. for a numbered list, [ ] for a checkbox, and / for commands. The formatting bar above it does the same by hand.
    3. 3Add subtasks in the composer before you save. Type a subtask, press Enter for the next one, and reorder them with the arrows. They are created with the task.
    4. 4Open the detail drawer to set priority, add comments, link subtasks, and attach files.
    5. 5Assign a recurrence rule so the task spawns a follow-up every time you mark it done.

    FAQ

    Why does my parent task auto-close when I mark the last subtask done?
    Atlas propagates parent status forward. When every subtask reaches a "done" status, the parent closes automatically. The reverse never happens: marking a subtask back to todo never re-opens a closed parent. You can always reopen the parent manually.
    Can I block a task with multiple others?
    Yes. Use the Dependencies section for the canonical BLOCKS, DUPLICATES, and RELATES set, or the Links section for custom tenant-authored relations (Settings > Relation kinds).
    How do I see tasks I'm blocked on right now?
    Open the Views page, group by status, and look at the "blocked" swimlane, or run a Cmd-K scope search: `t blocked`.

    Automate this module

    Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
    All modules
    Was this page helpful?

    On this page

    • Overview
    • Highlights
    • Important to know
    • How to use it
    • FAQ