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
    Still loading. Try again in a moment.Still loading. Try again in a moment.Still loading. Try again in a moment.
    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
    • Client portal domains

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Module reference

    Module guide

    Planning

    Cycles, initiatives and portfolios: the three ways work is grouped above the project.

    Open module/planning
    planningpm

    Overview

    Planning holds the three groupings that sit above an individual project. A cycle is a named time box with a start and an end date, such as a sprint or a month. An initiative is a named stream of work that can include tasks from several projects, and its card shows how many tasks are linked. A portfolio is a bucket of projects, so a programme or a department can be read as one health score on the Portfolios page. They are on one screen because they are the same decision viewed three ways.


    Highlights

    The capabilities worth knowing before you dive in.

    • Cycles with a start and an end date, for sprints, months or any time box the team works to
    • Initiatives that gather tasks from several projects into one stream, with a task count on the card
    • Portfolios that group projects, so a programme reads as one health picture rather than a list
    • Edit any cycle, initiative or portfolio with the pencil beside it, without leaving the page
    • Link and unlink projects from a portfolio directly on this page

    Important to know

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

    • A project can be linked to several portfolios, and unlinking it never deletes the project or its tasks.
    • Deleting a cycle, an initiative or a portfolio removes the grouping. The tasks and projects it referred to survive.
    • A cycle is only its name and dates. Changing them does not move or reschedule any task.
    • These three groupings are shared across the whole workspace rather than personal. What you create here is what your colleagues see.

    How to use it

    The primary workflow, start to finish.

    1. 1Open Planning from the sidebar. The three groupings are on one page.
    2. 2Create a cycle and give it a start and an end date, so the team has a shared time box.
    3. 3Create an initiative for a stream of work that crosses projects. Tasks are linked to an initiative through the API, and the card shows the count.
    4. 4Create a portfolio and link the projects that belong to it.
    5. 5Rename anything with the pencil beside it. Cycle dates can be edited the same way.

    FAQ

    What is the difference between an initiative and a portfolio?
    An initiative groups tasks by theme, and its card shows how many tasks are linked. A portfolio groups projects, and the Portfolios page scores it from the health of those projects. A project can sit in several portfolios.
    Does a cycle move my tasks?
    No. A cycle is a named time box. Changing its dates does not reschedule any task.
    If I delete a portfolio, do I lose the projects?
    No. Deleting a portfolio removes the grouping only. Every project and every task inside it is untouched and still reachable from Projects.
    Can two people see different planning groupings?
    No. Cycles, initiatives and portfolios belong to the workspace, so everybody with access sees the same set.

    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?
    About this page

    On this page

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