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

    On call

    Who is covering, when it changes, and where the holes are.

    Open module/on-call
    service-opsadmin

    Overview

    On call answers three questions in the order somebody actually asks them. Who is covering right now, which is what a responder needs at three in the morning and needs as one name. When it changes over the coming fortnight, which is what a manager reads on a Tuesday to see the shape of the cover. And where the holes are, because an uncovered rotation is the one thing this screen exists to make impossible to miss. Configuration is deliberately not between those three: schedules, layers, escalation policies and alert sources live behind one door at the bottom, on a quieter surface, so the live page stays readable under pressure.


    Highlights

    The capabilities worth knowing before you dive in.

    • Who is on call now, at the top, as a name rather than a rota to interpret
    • A fortnight band showing every handover, so the shape of the cover is visible at a glance
    • Uncovered stretches drawn in the band, with the ability to put somebody on from the lane where the hole is
    • An override, for arranging cover when a colleague cannot answer
    • Schedules, layers, escalation policies and alert sources behind one door, away from the live view

    Important to know

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

    • Two actions stay on the live page because they are response rather than configuration: covering a hole, and arranging an override. Everything else is configuration and is deliberately one step away.
    • The band covers fourteen days. It is a preview of what the schedule produces, not a separate record you can edit directly.
    • An override changes who answers for a period. It does not change the underlying rotation, which resumes afterwards.
    • Everything is scoped to your workspace, including the cached answer. Switching workspace never shows the previous one's rota.
    • The list of people who can be put on call depends on your permissions. If it could not be read, the screen says so rather than showing an empty picker.

    How to use it

    The primary workflow, start to finish.

    1. 1Open On call. The name at the top is who is covering right now.
    2. 2Read the fortnight band underneath for the handovers ahead.
    3. 3If a stretch is uncovered, put somebody on from the lane where the hole is drawn.
    4. 4Add an override when a colleague cannot answer for a period. The rotation resumes after it.
    5. 5Open the configuration door at the bottom to change schedules, layers, escalation policies or alert sources.

    FAQ

    Why is configuration hidden at the bottom?
    Because the live page is read under pressure. A responder at three in the morning needs one name, not a creation form, so configuration sits behind one door on a quieter surface.
    Does an override change the rotation?
    No. It changes who answers for a period. The underlying rotation resumes when the override ends.
    How far ahead does the band go?
    Fourteen days. It is a preview of what the schedule produces, so changing the schedule changes the band.
    Why can I not see everybody in the picker?
    Listing workspace members needs permission. If the list could not be read, the screen says so rather than leaving you looking at an empty picker and guessing.
    I switched workspace. Is this the right rota?
    Yes. Every cached answer here is scoped to the workspace, because answering who is on call with another workspace's rota is the worst wrong answer this product could give.

    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