Search the right collection
Choose a workspace and ask a question against its approved sources. Document ownership, versions, and access rules determine what belongs in that collection.
Private intelligence
Atlas Desk
A private knowledge workspace for teams finding information in internal documents, checking sources, and reviewing AI-assisted actions.
Discuss Atlas Desk
PRODUCT FOCUS
Internal knowledge, with sources you can inspect.
For support, operations, research, and professional services teams whose answers depend on policies, technical documents, case records, or internal guidance. Atlas Desk centres the document, the question, and the person reviewing the answer.
- 01Internal knowledge search
- 02Answers with source references
- 03Controlled access and review
A question becomes a reviewed answer.
Check the source
Read the answer alongside its supporting passages. Follow the reference, compare conflicting material, and identify where the source does not settle the question.
Review the next action
Use the context to prepare a brief, draft a response, or propose a record update. Define which actions need approval before they reach another system.
Sources and connections.
The enquiry establishes source formats, update frequency, user permissions, model access, hosting requirements, and which actions belong in the workspace. Connection scope and access arrangements are agreed for your team.
Documents and shared knowledge
Start with a document collection, internal wiki, or shared-drive export. Agree the supported formats, update schedule, and source owner for each collection.
Records with working context
Identify the support tickets, customer records, or internal cases that an answer needs to reference. API access and permitted fields define the connection scope.
Identity and access
Map workspace membership to the people and roles using the system. Review how permissions apply to search results, citations, history, and proposed actions.
What the workflow
needs to deliver.
- A workspace organised around a defined knowledge collection
- Answers linked to supporting documents and passages
- A review path for uncertain answers and proposed actions
- Evaluation cases covering permissions, conflicting sources, and missing information
Begin with one collection and one recurring question.
Bring representative documents, a few questions your team asks repeatedly, and the people who own the sources. We can define the workspace, connection scope, and review criteria before discussing access and implementation.
- Can the reviewer find the supporting passage?
- Does the answer respect the source permissions?
- What happens when documents disagree or the answer is missing?
- Which follow-up actions need a person’s approval?
Discuss Atlas Desk.
What should we bring to an Atlas Desk enquiry?
A recurring knowledge task, representative documents, several real questions, and the access rules around those sources. Redacted examples are suitable for an initial discussion.
Can it work with our existing documents?
Document formats, source quality, ownership, and access are reviewed first. We then agree which collections and connections belong in the workspace and how changes reach the index.
What happens when an answer is uncertain?
The workflow should keep supporting passages and missing context visible so a reviewer can decide what to use. Conflicting or incomplete sources belong in the evaluation cases rather than being hidden by a confident response.
Can an answer trigger a business action?
An enquiry can include proposed actions such as preparing a case or drafting a record update. The allowed tools, approval requirements, and activity history are defined for each connection.
How are access and hosting decided?
We review the intended users, source permissions, data boundaries, model access, and hosting requirements together. The enquiry confirms the access and implementation arrangements for that scope.