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

Unified search

One query across tasks, wiki, projects, goals, and comments.

Open module/search
corenav

Overview

A single search surface powered by a deterministic ranker. Results come back grouped per entity type with facet filters, and the ranker upweights exact title matches, recency, and whole-word hits.


Highlights

The capabilities worth knowing before you dive in.

  • Cross-entity: task, wiki, project, goal, and comment
  • Kind filter as a query param or a facet pill
  • Deterministic ranker: the same query returns the same order every time
  • Wired into the ⌘K palette so scope prefixes (`w runbook`) hit /search under the hood

Important to know

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

  • Search is case-insensitive and substring-based today; tsvector plus BM25 is coming for large workspaces.
  • Tenant isolation is enforced through the Prisma middleware, so there is no cross-tenant leakage.

How to use it

The primary workflow, start to finish.

  1. 1Type at least 2 characters to trigger a search.
  2. 2Click a facet pill to scope the results.
  3. 3Press Enter on a hit to open it in the detail drawer on the right.

FAQ

Why is search slow on very large corpora?
The current implementation is `WHERE title contains ...`, which is fine up to roughly 100k rows per entity. A tsvector plus GIN index is next.
Can somebody in another workspace find our content through search?
No. Tenant isolation is enforced in the data layer rather than in the query that the search screen happens to send, so there is no cross-tenant result to leak.
Why did a partial word match something I did not expect?
Search is case-insensitive and matches substrings today, so a fragment can appear inside a longer word. Full text ranking is planned for large workspaces and will make matching more precise.

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