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

    Forms (intake)

    Public forms that mint tasks into a target project.

    Open module/forms
    collabadmin

    Overview

    Intake forms with a public address at /f/ followed by the form slug. Each submission creates a task in the destination project, using the title field as the task title and writing the other answers into the description.


    Highlights

    The capabilities worth knowing before you dive in.

    • A public address that anyone with the link can open without an Atlas account
    • Conditional fields: a field can appear only when another field has a chosen value, and a hidden field is never required
    • A CSV download of all submissions to a form, and an approval state (pending, approved or rejected) on the task a form created, which a member other than the one who requested the approval decides; a task with no pending request cannot be decided

    Important to know

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

    • Toggle "enabled" off to stop accepting submissions. The public URL returns 404 without deleting history.
    • Required fields are enforced before a task is minted; a missing field returns 400.

    How to use it

    The primary workflow, start to finish.

    1. 1Open Forms and choose New form.
    2. 2Choose the destination project, define the fields, and mark one field as the title field.
    3. 3Copy the public address and share it, and every submission becomes a task you can triage.

    FAQ

    How do I stop a form accepting submissions without losing the responses?
    Choose Disable on the form. The public address then returns 404 while every submission already received stays exactly where it is. Deleting the form is a different action and is not required.
    What does a submission actually create?
    One task in the project the form is configured for, with the status to do and no priority, created in the name of the form owner. The field nominated as the title field becomes the task title, and the remaining answers are written into the description.
    Why was a form submission rejected with a 400?
    A required field was missing, or the title field was empty. Required fields are enforced before a task is created, so an incomplete submission is refused rather than creating a task with a gap in it.

    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