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

# Create a dedicated Gmail account for your Cora agent

> Give Cora its own Google Workspace user account so it can send, receive, and authenticate email independently on behalf of your team.

To operate like a digital teammate, Cora needs an email identity—just like any other person on your team. A dedicated Google Workspace account lets Cora send and receive messages with customers without being blocked by firewalls, log in securely via OAuth to sync with Gmail and your CRM, and act autonomously on follow-ups and escalations when needed.

<Warning>
  The Cora email account must be a full Google Workspace **user account** that can log in and authenticate independently. It cannot be a Google Group, an alias-only address, or a shared mailbox.
</Warning>

<Steps>
  <Step title="Request a new user account from your IT team">
    Ask your IT administrator to create a dedicated Google Workspace user account for Cora. Use the draft below to make the request:

    ```text Email subject theme={null}
    Request for new user account - cora@yourdomain.com
    ```

    ```text Email body theme={null}
    Hi [IT team / Admin name],

    We're working with an external vendor, Cora.ai, to launch an AI-powered onboarding assistant.

    To enable the assistant to operate independently, we need a dedicated Google Workspace user account (not a group or alias) with the following details:

    - Email address: cora@yourdomain.com
    - First name: Cora
    - Last name: Assistant
    - Secondary email: cora@cora.ai
    - Password instructions: Please send password setup instructions to cora@cora.ai so the Cora team can assist with configuration
    - Purpose: Used by our onboarding assistant to send and receive external emails on behalf of our team. Cora will only access this account to send/receive onboarding-related emails and integrate with Gmail + CRM via secure, OAuth-based authentication.
    - The account will not be used for login by individual users.

    Requirements:
    - Must be a full user account (not a Google Group or alias)
    - Must support third-party app authentication (OAuth)
    - Can be provisioned with the lowest-tier license that allows email login

    Thanks!
    ```
  </Step>

  <Step title="Share the new address with your Cora implementation team">
    Once the account is created, reply to your onboarding thread or email your Cora implementation lead with the new address. Make sure to CC [cora@cora.ai](mailto:cora@cora.ai) so the Cora team can connect the account to your workflows and begin setup.
  </Step>

  <Step title="Book a live walkthrough">
    Schedule a 15-minute session with your Cora implementation team to complete the configuration together. During this session you will:

    * Connect the Gmail and CRM integrations
    * Configure the sender display name
    * Add a branded signature and photo
    * Confirm OAuth permissions and test send capabilities
  </Step>
</Steps>