AtlasWork, planned itself.

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

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

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
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

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

Webhooks

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

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Module reference

Module guide

Activity

Tenant-wide audit stream: who did what, when, and where.

Open module/activity
admincompliance

Overview

Activity is the single feed of every state-changing event across the tenant: task created, project archived, PAT minted, webhook delivery failed, member invited. Every entry carries the actor (or PAT), the affected resource, and a structured diff where applicable.


Highlights

The capabilities worth knowing before you dive in.

  • Filter by actor, resource type, or PAT prefix
  • Deep links to the affected resource (task, project, or webhook)
  • Webhook deliveries are first-class events; replay from the row
  • Compliance-friendly: 90-day retention plus optional export

Important to know

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

  • Audit rows are immutable. The original record persists even after the resource is deleted.
  • PAT-attributed actions show the token prefix (atlas_pat_xxxx...) so you can trace stolen-key abuse.
  • Filtering is server-side; the URL holds your filter state for shareable links.

How to use it

The primary workflow, start to finish.

  1. 1Open it with `g a` or click Activity in the sidebar.
  2. 2Use the filter bar at the top to scope by actor, resource, or PAT.
  3. 3Click any row to open the affected resource in a drawer.

FAQ

How long are events retained?
Default retention is 90 days. Self-hosted deployments can override AUDIT_RETENTION_DAYS; events are pruned by a nightly job.
Can I subscribe to the stream?
Yes. Every audit event is also published to the webhook bus. Subscribe at /settings/webhooks with a topic of `audit.*`.
Can I tell which API token performed an action?
Yes. An action attributed to a personal access token shows the token prefix, so a suspected stolen key can be traced to its activity without exposing the token itself.

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