> ## Documentation Index
> Fetch the complete documentation index at: https://talent.docs.mercor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mercor Expert Email

> Learn how Mercor Expert emails operate, when their use is appropriate, and the procedures for transitioning from legacy emails.

## Overview

Mercor provides expert email addresses to facilitate secure access to project resources. These email addresses are designated for accessing project-mandated tools, documents, and communications.

<Danger>
  Effective from February 12, 2026, Pacific Time, all experts engaged in active projects will be granted access to the @mercor.expert email via their Okta accounts. \
  \
  Experts who previously had access to the @c-mercor.com email will retain access to both email addresses for a transitional period to facilitate content migration. 
</Danger>

<Note>
  Mercor is introducing a new Okta-managed email system for experts: **@mercor.expert**.\
  This page explains what it is and how it works.
</Note>

***

## What Is the Mercor Expert Email?

The **Mercor Expert Email** (`@mercor.expert`) represents a newly established Google Workspace account designated for experts working Mercor projects.

It is utilized to securely access:

* Google Docs, Sheets, and Drive;
* Facilitate project-related internal communications;
* Access tools that necessitate identity verification.

This system is intended to gradually supersede the legacy **@c-mercor.com** email address.

### Important: Contractor Email and Okta Are Different

<Tip>
  Your @mercor.expert email is **not authorized for Otka login. Access to Okta** is limited to your personal email address associated with your work.mercor.com account.
</Tip>

### Key Distinction

| Purpose                   | Email Used       |
| ------------------------- | ---------------- |
| Log in to work.mercor.com | Personal email   |
| Log in to Okta            | Personal email   |
| Access Google Workspace   | Managed via Okta |

Your expert email is a project resource account and does not function as an Okta login credential.

***

## What Is Changing and What Is Remaining Unchanged

<Columns cols={2}>
  <Card title="What’s New" icon="sparkles">
    • New anonymized @mercor.expert email\
    • Access managed through Okta\
    • Secure Google Workspace access
  </Card>

  <Card title="What’s Not Changing" icon="shield-check">
    • You still log into Okta with your personal email\
    \
    • Slack, Insightful, Stripe, Feather, and other tools are unaffected
  </Card>
</Columns>

***

## Your New Email Address

Your new email **will not include your actual name**.

Instead, it is an **anonymized, randomly generated address** composed of scientific or nature-related terminology, for instance:

`ruther.tianguan@mercor.expert`

<Note>
  This is anticipated and deliberate. \
  The anonymized format safeguards your identity while maintaining consistent access across various tools.
</Note>

You may verify that this email address is yours by:

* Reviewing your **Slack profile**
* Accessing the **Google Workspace application in Okta**

***

## How to Access Your Mercor Expert Email

<Steps>
  <Step title="1. Sign in to Okta">
    Please visit [https://c-mercor.okta.com](https://c-mercor.okta.com) and log in using your **personal email** address, which should be the same as the one utilized on work.mercor.com.
  </Step>

  <Step title="2. Open Google Workspace">
    Upon logging in, select the **Google Workspace** icon to access Gmail, Drive, Docs, and Calendar.
  </Step>

  <Step title="3. Verify if prompted">
    If requested to verify an unfamiliar email address, please accept it — this pertains to your new @mercor.expert account.
  </Step>
</Steps>

***

## What You Should Do

<Columns cols={2}>
  <Card title="Access Your New Account" icon="check-circle">
    Confirm you can open Google Workspace through Okta.
  </Card>

  <Card title="Move Personal Materials Only" icon="arrow-right-arrow-left">
    Transfer drafts, notes, or personal files you created — **not project-provided materials**.
  </Card>

  <Card title="Create New Work Here" icon="folder">
    Create new Mercor-related documents directly in your @mercor.expert Google Drive.
  </Card>

  <Card title="Keep Old Access Temporarily" icon="clock">
    Legacy access persists throughout the transition period.
  </Card>
</Columns>

<Warning>
  Please refrain from downloading or copying project materials provided by Mercor.\
  These will be redistributed to your new account automatically if necessary.
</Warning>

***

## Transition & Deprecation

* Access via **@c-mercor.com** will be deprecated after a transition period.
* A **clear sunset date** will be announced at least **one week in advance**.
* Once deprecated, old access methods will be disabled.

***

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Do all experts need to use the Mercor Expert Email?">
    Yes, commencing on February 12, 2026, all experts will be granted access to their new mercor.expert email addresses. 
  </Accordion>

  <Accordion title="Why is my email name strange or unfamiliar?">
    All @mercor.expert email addresses are anonymized to ensure privacy and security. The displayed name does not correspond to your actual identity.
  </Accordion>

  <Accordion title="Can I change my Mercor Expert email name?">
    Email addresses are generated by the system and cannot be customized.
  </Accordion>

  <Accordion title="Can I send emails externally using this account?">
    Not at this time. Mercor Expert emails are currently restricted to send to and from @mercor.com addresses.
  </Accordion>

  <Accordion title="Will this affect Slack, Insightful, Feather or any other tool?">
    Slack, Insightful, Feather, or any other tool is unaffected and will continue to use existing identifiers. \
    \
    Even if you can see the expert email on your Slack profile, you will use your personal email to sign in to Okta, then access Slack through Okta. 
  </Accordion>

  <Accordion title="Should I use this email for all Mercor work going forward?">
    Yes. Kindly proceed to generate new Mercor-related materials within this workspace henceforth.
  </Accordion>

  <Accordion title="Can I keep using my @c-mercor.com account for now?">
    No, please start using your expert email and transfer all your important content from your previous c-mercor email. 
  </Accordion>

  <Accordion title="What will happen to the files in my @c-mercor.com Google Drive?">
    It is necessary to transfer any personal drafts, notes, or self-created materials to your @mercor.expert account. **Please refrain from** transferring client-provided materials, as these will be redistributed by Mercor if deemed necessary.
  </Accordion>

  <Accordion title="Can I migrate bookmarks, Chrome profiles, or extensions?">
    Yes. If you have utilized Chrome with your previous @c-mercor.com account, it is advisable to consider exporting and importing bookmarks or establishing a new profile under your @mercor.expert email for the purpose of maintaining organized work.
  </Accordion>

  <Accordion title="What happens if I miss the transition deadline?">
    Once the sunset date is announced, access to previous emails, including those associated with @c-mercor.com, will be revoked. Kindly ensure that you complete your transition prior to this date to prevent loss of important files or access.
  </Accordion>

  <Accordion title="How long will I have access to my @mercor.expert email?">
    As long as you maintain at least one active contract with Mercor, your expert email account will continue to be operational.
  </Accordion>
</AccordionGroup>

***

## Related Pages

<Columns cols={3}>
  <Card title="Okta Access" icon="lock" href="/how-to/okta-access">
    Learn how Okta manages your access to Mercor tools.
  </Card>

  <Card title="Expert Email" icon="envelope" href="/working/expert-email">
    Learn how your @mercor.expert email works and how to access it.
  </Card>

  <Card title="Getting Started" icon="briefcase" href="/working/getting-started">
    Understand which tools your project requires.
  </Card>
</Columns>