> ## Documentation Index
> Fetch the complete documentation index at: https://support.metaview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Atlas

> Configure the Atlas integration for your workspace.

Metaview integrates with [Atlas](https://recruitwithatlas.com/). This brings Atlas candidate and project data into Metaview for Notes, Application Review, and Sourcing.

## Connect Atlas to Metaview

In Metaview, go to **Settings** → **Integrations**, find **Atlas**, and click **Connect**. Follow the on-screen flow to authorize your Atlas account.

After saving your changes, the integration process will start. This can take up to 48 hours to complete, and you will be emailed once the integration is successful.

## Permissions

The Atlas connection is authorized through Kombo as a whole — there are no individual permissions for you to select. Metaview uses that access to match your calls to the right candidate and role, enrich candidate profiles, keep your team in sync, and write Notes and other Metaview information back to Atlas.

<Note>
  Kombo is a Metaview subprocessor. Our current subprocessor list is published in the [Trust Center](https://trust.metaview.ai/), and the terms covering this processing are set out in our [DPA](https://www.metaview.ai/data-processing-agreement). See also [Privacy and security](/account-management/privacy-and-security/overview).
</Note>

Anything under **Optional** is only used by an individual feature — without it, the core integration still works.

<Accordion title="View list of permissions">
  **Required**

  * Jobs
  * Candidates
  * Applications
  * Application stages
  * Users
  * Interviews

  **Optional**

  * Create candidates and applications
  * Add a PDF attachment to an application
  * Move or reject an application
</Accordion>

<Note>
  Atlas does not support text notes or scorecards through this integration, so Metaview neither requests nor uses that access.
</Note>

## Features

* Employees and hiring teams sync
* Enhanced candidate metadata, including name, job title, stage, location, CV, status, and rejection reason
* Add Notes to a candidate's application as a PDF attachment
* Use [Application Review](/application-review/overview) to review, progress, and reject candidates
* Use [Sourcing](/sourcing/overview) to search through your Atlas candidates
* Add sourced candidates to Atlas with their LinkedIn profile, title, and additional email addresses

## What's not supported

* **Automatic scheduling** — schedule interviews through your calendar or other scheduling tools.
* **Rejection emails** — rejecting a candidate from Metaview marks them as rejected in Atlas and stops active outreach campaigns, but it does not send an Atlas rejection email.
* **Text notes and links to Metaview notes** — Atlas does not support the text-note action these features require. Notes are added as a PDF attachment instead.
* **Direct links from Metaview to Atlas** — Atlas records do not expose a supported deep link through this integration.
* **Scorecards** — scorecard data is not available through this integration.

## Troubleshooting

Metaview will attempt to match your calls to relevant Atlas candidates and applications. Common reasons a call or candidate may not be matched include:

* The call or candidate is missing in Atlas
* Duplicate candidates or applications in Atlas
* A mismatch between the Metaview invite and the candidate's Atlas details
* Insufficient information to identify the candidate
* The meeting type is not set to **Job interview** or **Debrief**

If a call was not matched or was matched incorrectly, please [contact support](mailto:support@metaview.ai) with specific examples and the relevant Atlas candidate or application IDs.

## Disconnect your Atlas integration

In Metaview, go to **Settings** → **Integrations**, select **Atlas**, and choose **Disconnect Atlas**.

This immediately disconnects Metaview from your Atlas data. Calls already scheduled on your calendar may still go ahead. See [Disabling Metaview](/notes/capturing-calls/disabling-capture) to prevent the Notetaker from joining future calls.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.