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

# Set defaults for new accounts

> Choose starting features, billing settings, resources and limits for new client accounts.

Open **Defaults** in the workspace navigation to configure the starting setup for new accounts. Its sections are **Features**, **Rebilling**, **Resources** and **Limits**.

## Configure the defaults

1. In **Features**, select the portal sections new client accounts should see and save.
2. In **Rebilling**, review enabled usage categories and pricing settings. Read the [billing guide](/v3/billing-guide) before configuring client prices.
3. In **Resources**, add the assistants you want new accounts to receive. Review the source assistant and the workspace before adding it.
4. In **Limits**, set the supported resource values or unlimited choices and save. Unlimited calling is pay-as-you-go, not free calling.

## What each section controls

| Section | Scope and next check |
| - | - |
| Features | The starting portal-section selection. See the [complete list of navigation switches](/v3/guides/accounts/navigation-permissions#available-switches). |
| Rebilling | Starting client billing configuration. Check the [billing explanation](/v3/billing-guide) and the actual client ledger before relying on a charge. |
| Resources | Assistants to copy into newly created accounts; their destination integrations still need review. |
| Limits | Saved resource values for new accounts. Reopen the created account's controls to confirm them; a saved value alone does not establish when every usage path will enforce it. |

These groups serve different purposes: selecting a portal section does not create an assistant, and including an assistant does not purchase or assign its phone number.

## Existing accounts require an explicit choice

Saving feature defaults normally affects new accounts. **Apply to all existing accounts** is a separate action: its confirmation warns that existing custom feature configurations will be replaced. Use it only after reviewing that effect. Removing a default resource stops future cloning; it does not remove assistants already copied to other accounts.

## Test a new account

Create or import a test account through the setup path your team uses. Check its saved features, billing settings, limits and copied assistants. Review any resource setup warnings before enabling an assistant.

A copied assistant still needs destination setup. Review its prompt, calendar, phone numbers, tools and GHL field mappings; choose destination credentials where required. No phone number is purchased by cloning. Enable and publish only after those checks, then run a test conversation.

If an assistant is absent, inspect the selected default resources and any import error. If it is disabled after copying, complete the destination setup rather than assuming the source account's connections transferred.

See [workspace setup](/v3/guides/getting-started/workspace-setup) and [permissions](/v3/guides/accounts/navigation-permissions). Reopen the test account's **Account limits** to confirm saved resource settings; verify usage behavior separately before relying on a limit.


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