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

# Set up a new Default workspace

> Admin guide to setting up a new Default workspace: connect your CRM and conferencing tools, create a routing policy and a queue, and invite your team.

Setting up a new Default workspace is an admin task in 4 parts: connect your shared tools, create
a routing policy, create a queue, and invite your team.

After your team joins, each member finishes their own setup with
[Member onboarding](https://docs.os.default.com/member-onboarding.md).

> [!NOTE]
>
> This guide moves between **Settings** and **Routing** in the sidebar on the left of the app.
>
> The steps here need admin access.

## 1. Connect your shared tools

Connect the workspace-level tools first. Routing and scheduling then have data to work with.

**1. Open the Connections page**

Select **Settings** in the sidebar. Then select **Connections** under
**Workspace Settings**.

**2. Connect your CRM**

Select **Connect** on Salesforce or HubSpot. Default then reads and writes records and
triggers automation when records change.

Salesforce needs the Default managed package installed in your org first. See
[Salesforce](https://docs.os.default.com/settings/connections/salesforce.md).

**3. Connect Zoom**

Select **Connect** on Zoom. You connect Zoom once for the whole workspace, and booked
meetings can then include a Zoom link. Google Meet and Microsoft Teams work differently: they
use each member's own Google Calendar or Outlook Calendar connection.

For example, connect your company's Salesforce org and Zoom. Each member connects their own
calendar during [Member onboarding](https://docs.os.default.com/member-onboarding.md), not here.

See [Connections](https://docs.os.default.com/settings/connections.md) for the full provider list.

## 2. Create a routing policy

A routing policy holds the rules a queue runs: the distribution rule, the tiebreaker, and
crediting behavior. Policies are reusable, so 1 policy can drive many queues.

**1. Open Policies**

In the sidebar, select **Routing**. Then open the section menu at the top of the page and
select **Policies**.

**2. Create the policy**

Select **Create new**.

**3. Set the general options**

On the **General** tab, name the policy. Under **Assignment Units**, choose whether it
routes **Meetings**, **Objects**, or both.

**4. Choose the assignment rules**

On the **Assignment** tab, choose a distribution rule and a tiebreaker. The distribution
rules are **Take turns equally**, **Most available calendar time**, and
**Least recent assignment**.

For example, create `Inbound Demo Policy` that routes both meetings and objects. It takes
turns equally, also called round robin, and breaks ties by recency.

See [Policies](https://docs.os.default.com/policies.md) for every rule and option.

## 3. Create your first queue

A queue is a named group of people that points at a policy. The routing engine scores the
queue's active members and picks who gets each lead or meeting.

**1. Open Queues**

In the sidebar, select **Routing**. Then open the section menu at the top of the page and
select **Queues**.

**2. Create the queue**

Select **Create new**, then **New queue**.

**3. Name it and pick a policy**

Give the queue a name. Choose the policy you just created.

**4. Add members**

Add members to the queue.

**5. Check that the queue is on**

In the queues list, the queue's **Status** toggle is on. New queues start on.

For example, create `West AE Round Robin`, point it at `Inbound Demo Policy`, and add 3 account
executives.

See [Queues](https://docs.os.default.com/queues.md) for managing members, weights, and calibration.

## 4. Invite your team

**1. Open the Users page**

Select **Settings** in the sidebar. Then select **Users** under **Workspace Settings**.

**2. Invite your teammates**

Select **Invite People**. Enter each teammate's email address.

**3. Send the invitation**

Select **Send**. Or use **Copy link** to share the invitation through Slack or
another channel.

**4. Finish the invitations**

Select **Done**. New members appear in the table after they accept.

For example, invite `newrep@acme.com`, send the email, and add them to your queue from step 3.

> [!TIP]
>
> Your workspace now has a routing policy and a queue. To send leads to the queue, add a
> **Round-Robin** node to a [workflow](https://docs.os.default.com/workflows/steps-routing-scheduling.md), or add the queue as a
> host on a Team [event](https://docs.os.default.com/events.md). Each member now finishes their personal setup.

## Next steps

> [card] [Member onboarding](https://docs.os.default.com/member-onboarding.md)
>
> Send this to each teammate to set up their profile, availability, and booking link.

> [card] [Routing](https://docs.os.default.com/queues.md)
>
> Manage queues, members, and routing policies.

> [card] [All settings](https://docs.os.default.com/settings.md)
>
> Everything you can configure for yourself and your workspace.


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