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

# Set up your workspace

> Your first hour as a Parker admin: connect Salesforce, set up Parker's instructions and limits, and add the knowledge and rules your team needs.

<Info>
  **Admins only.** Only workspace admins can change these settings. If you're not an admin, you can still see them, but you can't edit them.
</Info>

Work through this checklist once, in order, and your team can start asking Parker real questions.

## Before you begin

* You need the **admin** role in your Parker workspace. See [Manage members and roles](/admin/members).
* Have a Salesforce login that can authorize connected apps for your org.
* All of these settings live in one place. To open it, select **Settings** at the foot of the sidebar.

## Your first-hour checklist

<Steps>
  <Step title="Connect Salesforce">
    Go to **Settings** > **Connections** and select **Salesforce**. Connect your Salesforce login and approve access. See [Connect Salesforce](/admin/connect-salesforce).
  </Step>

  <Step title="Add your team">
    People join your workspace through Parker support. See [Manage members and roles](/admin/members).
  </Step>

  <Step title="Write Parker's instructions">
    Go to **Settings** > **Agent** > **Instructions**. Describe what Parker does for your team, and pick a tone. See [Write Parker's instructions](/admin/agent-instructions).
  </Step>

  <Step title="Decide how much Parker does on its own">
    Go to **Settings** > **Agent** > **Autonomy**. **Review** means every reply is a draft for a person to check. Stay on it until you trust what Parker writes. See [Set Parker's autonomy](/admin/autonomy).
  </Step>

  <Step title="Choose what Parker starts by itself">
    Go to **Settings** > **Agent** > **Proactive** to turn nudges, scheduled work, and deep analysis on or off. See [Control proactive work](/admin/proactive).
  </Step>

  <Step title="Add knowledge">
    Go to **Settings** > **Knowledge**. Upload your playbooks and product documents, add your help center, and upload spreadsheets Parker can query. See [Add knowledge](/admin/knowledge).
  </Step>

  <Step title="Add house rules">
    Go to **Settings** > **Rules** and add the rules Parker must always follow, such as "Never quote a discount above 10%". See [Set house rules](/admin/rules).
  </Step>

  <Step title="Set up your brand">
    Go to **Settings** > **Branding** to add your logos, colors, and fonts for the reports and pages Parker creates. See [Branding](/admin/branding).
  </Step>

  <Step title="Check compliance">
    Go to **Settings** > **Compliance** and add the regulations your business answers to. See [Compliance](/admin/compliance).
  </Step>

  <Step title="Optional: connect other apps and channels">
    Add apps such as Linear, Notion, or Asana under **Settings** > **Connections**. To use Teams, connect your tenant under **Settings** > **Channels**. See [Connections and apps](/admin/connections-and-apps) and [Channels](/admin/channels).
  </Step>
</Steps>

## Check it worked

Open a new chat and ask Parker a question about your own Salesforce data. If Parker answers with your records, Salesforce is connected for you.

<Prompt description="Confirms Parker can read your Salesforce data">Show me my five biggest open opportunities.</Prompt>
<Prompt description="Confirms Parker can find your uploaded knowledge">What does our pricing guide say about multi-year discounts?</Prompt>

## What to tell your team

Send your team the [Quickstart](/quickstart). Each person connects their own Salesforce login and mailbox under **Settings** > **Connections**.

## Related

<CardGroup cols={2}>
  <Card title="Connect Salesforce" href="/admin/connect-salesforce" icon="cloud">
    Connect Salesforce and choose how Parker works in it.
  </Card>

  <Card title="Write Parker's instructions" href="/admin/agent-instructions" icon="bot">
    Identity, instructions, and voice.
  </Card>

  <Card title="Settings reference" href="/reference/settings" icon="settings">
    Every setting in one table.
  </Card>

  <Card title="Permissions" href="/reference/permissions" icon="shield">
    What admins and members can each change.
  </Card>
</CardGroup>


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