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

# Set enterprise and team role defaults

> Set starting permissions for Admins, Members, and Agents, customize exceptions, and reset users to inherited defaults.

Use role defaults when people with the same team role should start with the same permissions. Set a shared starting point across an enterprise, then customize a team or an individual member when needed.

<Note>
  These are overridable defaults for **Admin**, **Member**, and **Agent** team roles. Enterprise workspace permissions and access granted through portfolio membership are managed separately. Products and features must still be enabled for the team.
</Note>

## Understand which settings apply

Permissions inherit in this order, with more specific saved settings taking precedence:

| Level                | Applies to                                   |
| -------------------- | -------------------------------------------- |
| Avoca role defaults  | The starting permissions for each role       |
| Enterprise defaults  | That team role across the enterprise's teams |
| Team defaults        | That role on one team                        |
| Individual overrides | One team member                              |

For example, an enterprise can turn **View Calls** off for Members, and a team can turn it on for its Members. A member on that team inherits access unless their individual permissions explicitly turn it off.

Changing a default affects existing members who inherit that permission as well as future members. Existing saved individual customizations remain in place. Some members may have a complete set of saved permissions from earlier edits; changing defaults will not replace those saved values.

## Set defaults for an enterprise

You need an enterprise **Admin** role with **Manage Members** permission and access to the enterprise's Members page.

1. Select the enterprise workspace and open **Members**.
2. Select **Team role defaults**.
3. Choose **Admin**, **Member**, or **Agent**.
4. Change the permissions that should apply to that role across the enterprise's teams.
5. Review the changes and select **Save Changes**.

Team and individual overrides continue to take precedence over these defaults.

## Customize defaults for one team

You need **Edit Permissions** and access to the team's Members page. You can edit defaults for roles at or below your own: Admins can edit all three roles, Members can edit Member and Agent defaults, and Agents can edit Agent defaults when granted **Edit Permissions**.

1. Select the team and open **Settings → Business Info → Members → Team Members**.
2. Select **Role defaults** and choose a role.
3. Change the permissions that should differ for this team.
4. Select **Save Changes**.

Permissions without a custom setting continue to inherit the enterprise's defaults, or Avoca's role defaults when no enterprise setting applies. In the editor, **Custom** marks an explicit choice at the level you are editing; **Inherited** marks a value supplied by its defaults.

To remove all custom settings for the selected role at that level, select **Use inherited defaults**, review the resulting permissions, and select **Save Changes**. At the team level this restores enterprise or Avoca defaults; at the enterprise level it restores Avoca defaults. Select **Cancel** to discard the draft.

## Customize or reset an individual member

Use individual overrides for exceptions to the team's role defaults. An authorized member can open **Edit Permissions** for another member at or below their own role. Permissions can also be customized while preparing an invitation.

To return an existing member to their current role defaults:

1. Open **Team Members** and select **Edit Permissions** for that person.
2. Select **Reset to role defaults**.
3. Review the resulting permissions. This clears all of that member's individual overrides, so access can increase or decrease.
4. Select **Save Changes** to apply the reset, or **Cancel** to keep the existing settings.

After a saved reset, the member follows the current team and enterprise defaults. Future default changes continue to apply to permissions without individual overrides.

## Check the result

Ask the affected member to refresh the dashboard and confirm the pages and actions they need. Viewing a page and editing its settings can require separate permissions.

* **A default change did not affect someone:** check their individual overrides and any team defaults that take precedence. Reset only if they should follow the role defaults.
* **The defaults button or a role is unavailable:** confirm the selected workspace, your permission-management access, and your role. The available controls depend on your access.
* **Saving reports that role defaults changed:** another administrator saved changes after you opened the editor. Reopen it, review the latest defaults, and apply your changes again.
* **A page is still unavailable:** check the team's products and features as well as permissions. See [Understand access and feature visibility](/getting-started/access-and-visibility).

For invitations and SSO, see [Manage members, employee contacts, and SSO](/business-info/members-and-sso). For the starting Coach permissions, see [Invite managers and agents to Coach](/coach/access).