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

    Analytics

    The whole workspace in numbers, from a strip of headlines down to one module.

    Open module/analytics
    analyticspm

    Overview

    Analytics is the overview of the workspace read as numbers. The page has a strip of headline figures meant to be understood in a glance, a funnel, and a grid of module cards for the reader who wants to know why a headline moved. The detailed PDF Studio, connector and activity reports are pages under Analytics in the sidebar. The date range, the refresh, the CSV export and a role lens are on the header, and the lens narrows the module cards to those that matter for a role, because a founder, a delivery lead and an operations manager are looking at the same workspace for different reasons. Where a figure could not be read, the screen says Unavailable in readable terms rather than showing zero.


    Highlights

    The capabilities worth knowing before you dive in.

    • A headline strip summarising the platform, readable without interpretation
    • A grid with one card for each module area, for the question the headline raises
    • A date range on the header (7, 30 or 90 days), applied to the overview figures and the module cards
    • A role lens (Founder, Engineering, Sales, Operations, Finance or People) that narrows the module cards to those that matter for that role
    • CSV export of the overview figures and the module cards that are showing
    • A figure that could not be read says Unavailable rather than showing zero

    Important to know

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

    • Analytics reads and never writes. Nothing here changes a task, a project or a record.
    • Numbers respect permissions, so two people can legitimately see different totals for the same range.
    • A figure shown as unavailable is a figure that could not be read, which is not the same as zero. The screen keeps the two apart on purpose.
    • The date range applies to the overview figures and the module cards. A card that looks wrong is often a range that is wider or narrower than you expected.

    How to use it

    The primary workflow, start to finish.

    1. 1Open Analytics and set the date range you care about.
    2. 2Read the headline strip first. It is designed to be understood without study.
    3. 3Choose the role lens that matches why you are here. The module grid then shows the cards for that role.
    4. 4Read the module grid when a headline raises a question, and open the PDF Studio, connector and activity reports from Analytics in the sidebar.
    5. 5Export the overview and the module cards as a CSV file if the numbers need to leave Atlas.

    FAQ

    Is zero the same as unavailable?
    No, and the screen keeps them apart deliberately. Zero means nothing happened. Unavailable means the figure could not be read, and no conclusion should be drawn from it.
    Why do my numbers differ from a colleague's?
    Because analytics respects permissions. You each see the totals for the data you are allowed to see, over whichever range each of you has set.
    What does the role lens change?
    Which module cards are shown. Founder shows every card. The other lenses show only the cards relevant to that role, and the count above the grid says how many of the total are showing.
    Can I get the underlying rows?
    No. The CSV export holds the figures on the overview and the module cards that are showing, not the underlying records. Open the module that owns a number to see its records.

    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