Skip to main content
Run and manage investigations from Atlas in the Sixtyfour web app. Atlas appears in the sidebar once it is enabled for your organization. See Atlas Overview for access.

Start an investigation

  1. Open Atlas.
  2. Under New investigation, enter a name, company or topic to research.
  3. Optionally, attach files and set the options below.
  4. Press Enter to start. Shift+Enter adds a line.
You can attach up to 5 files: PNG, JPG, WebP or GIF images up to 20 MB each, and PDF, DOCX, XLSX or CSV documents up to 25 MB each.

Start one investigation per row

  1. Select Upload CSV. The file needs a header row, and each column becomes a field on the lead.
  2. Check the rows in CSV Preview and add an optional research direction.
  3. Select Submit All, which shows the total credits.
Each row starts its own investigation, up to 1,500 rows. Attached files aren’t available on a CSV upload.

Follow a run

An investigation opens on its graph while it runs, and on its report once it completes. The investigation’s status shows how the run is going: A blue dot in the sidebar marks a report you haven’t opened yet.

Steer a run

You can change what a live agent works on without restarting it. This needs edit access to the investigation.
  1. Open Agents and select the main agent or a subagent.
  2. Type in Send a message… and send it. Messages can be up to 4,000 characters, and queued messages appear in the timeline until the agent reads them.
To point the agents at a note, use Send to running agent on that file. To stop, use Stop latest run. Findings are kept, and you can add an agent later to carry on.

Add more research

Add Agent starts another run on the same workspace and graph, during a run or after it has finished. It needs edit access and is billed as a new run.
  1. Select Add Agent.
  2. Enter a research direction. Later agents keep it.
  3. Optionally, attach files and set the engine, budget and time limit.
  4. Select Deploy.
To follow up on one finding, select its node in the graph and use Dig deeper on this node…, which also starts a billed run.

Edit notes and findings

Notes save as you type. In the file list you can create notes and folders, and rename, move, duplicate and delete them, with undo. File history shows what changed between versions. In the graph, Add finding records something you know, and you can edit a node, connect it to another node or remove a connection. If a finding is wrong, use Retire node. The report leaves it out and later research won’t add it back. Restore node undoes it.

Read and revise the report

Atlas writes the report when a run completes. To read one sooner, use Generate early report while research is running, and Update report to bring it up to date. To change a finished report, use Revise report. Add feedback of up to 4,000 characters and up to 5 evidence files, then select Rewrite report. Later reports keep your feedback. The person who created the investigation can revise its report once research has stopped. Earlier reports lists previous versions as PDFs.

Share an investigation

Everyone on the team that owns an investigation can see it, unless the run is private. To share it further, use Share. A public link shows the investigation as it is now, so later research appears there. Public pages hide the agents and file history, and search engines don’t index them. A private run can’t be shared. To group investigations, add them to folders. Share folder… shares a folder with another team, including anything added to it later.

Export

Share → Export downloads one investigation as a Workspace ZIP, a Report PDF or a CSV. To export many, open bulk export, pick investigations by search or date, and choose a format. A bulk export covers up to 5,000 investigations. ZIP and PDF exports build in the background and stay in Recent exports for 24 hours.

Schedule recurring research

An investigation is a snapshot. An automation re-runs research on a schedule, so you catch what changes without starting over. Open Automations, create one or start from an example, and fill in: Automation runs use XHigh on a one-unit budget, billed as a normal run. A run fails if your balance is below the price of one run, or if the investigation already has a run going. An automation pauses if the person who created it loses access to its team. Automations can’t target private investigations or ones shared from another team.

Save instructions

Saved instructions apply to every run, so you don’t repeat them. Set them in Settings → Atlas, up to 5,000 characters at each level: When both are set, a run follows both.