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

# Feature Access

> Control which workspace members see each Exec feature by granting access to everyone, specific groups, or individual members.

Feature Access lets [workspace admins](/platform/admin-capabilities) decide who can see and use each part of Exec — AI Roleplays, Programs, Coaching, Certifications, Call Scoring, Coaching Analytics, Knowledge Hub, and Courses.

Use it to pilot a new product area with a single team, keep specialist tools out of the way of members who don't need them, or centrally manage who can create and assign content across the workspace.

<Note>
  Feature Access is included on the **Enterprise** plan. On Free, Starter, and Professional workspaces, opening the page shows an upgrade prompt instead. See [Plans](/platform/plans) for what each plan includes, or email [hello@exec.com](mailto:hello@exec.com) to talk through Enterprise.
</Note>

<Note>
  Workspace and group admins always see every feature. Grants only ever add access for non-admin members — they never remove access from an admin. See [Admin Capabilities](/platform/admin-capabilities).
</Note>

***

## Open Feature Access

In the left-hand navigation, open **Settings**, then click **Feature Access**. This page is visible only to workspace admins.

Feature Access has two tabs:

* **Visibility** — controls which product sections appear in the left nav for each member.
* **Permissions** — controls who can perform actions inside those sections (for example, who can create roleplays or who can see other members' calls).

***

## Visibility tab

The Visibility tab lists every product area in your plan. For each one you choose who can see it:

* **Everyone** — all workspace members see the feature. This is the default for a new workspace once the product is enabled.
* **Only selected groups and people** — only the [groups](/platform/settings-tab#groups) and members you list see the feature. Everyone else has the section hidden from their navigation.
* **Admins only** — no groups or members are granted, so only workspace and group admins see the feature.
* **Off** — the feature is turned off for the entire workspace. Turn it back on from this row.
* **Not in your plan** — the feature isn't included in your current plan. Upgrade from **Billing** to enable it.

### Grant access to a feature

<Steps>
  <Step title="Click Edit next to the feature">
    A side panel opens with the current access mode and grant list.
  </Step>

  <Step title="Choose who can see the feature">
    Select **Everyone** to open the feature to all members, or **Only selected groups and people** to restrict it.
  </Step>

  <Step title="Add groups or members">
    If you chose to restrict, search for a group or a member and add them to the grant list. You can mix and match — a feature can be granted to one full group plus a handful of individuals.
  </Step>

  <Step title="Save">
    Members gain or lose the section on their next page load.
  </Step>
</Steps>

<Note>
  A member who doesn't have visibility to a section can still take part in content that's directly assigned to them. For example, if a member isn't granted **Programs** access but an admin assigns them to a program, they can still complete their assignments — visibility hides the section from the nav, it doesn't block direct assignments.
</Note>

***

## Permissions tab

The Permissions tab controls who can take specific actions inside a feature, independently of who can see it. Typical settings:

* **AI Roleplays** — who can create scenarios (all members, workspace admins, or workspace and group admins) and who can assign scenarios.
* **Call Scoring** — who can view other members' calls. Choose between members seeing only their own calls, group admins seeing their group's calls, and workspace admins seeing every call.

Set each dropdown to the audience that should be able to perform the action. As with visibility, workspace and group admins keep their permissions regardless of what you choose here.

***

## Access Explainer

At the bottom of both tabs, the **Access Explainer** answers "can this person see this feature, and why?" without waiting for the member to sign in and check.

<Steps>
  <Step title="Pick a member or a group">
    Search by name or email.
  </Step>

  <Step title="Pick a feature">
    Choose any feature from the dropdown.
  </Step>

  <Step title="Read the verdict">
    Exec shows whether access is granted, and lists the exact reasons — for example, "granted to everyone", "granted via the SDR Outbound group", "granted directly to this member", or "assigned to a scenario, program, or course".
  </Step>
</Steps>

Use the Explainer when a member reports they can't find a section, or before rolling out a change to confirm the right people gain access.

***

## Common setups

* **Piloting a new product** — set the feature to **Only selected groups and people** and add the pilot group. Every other member sees the workspace as it was before.
* **Specialist tools** — restrict Call Scoring to your sales team while keeping AI Roleplays open to the whole company.
* **Buttoned-up workspace** — set every feature to **Only selected groups and people** and grant each product only to the teams that use it.

***

## Getting Help

**Need help?** Contact us at [hello@exec.com](mailto:hello@exec.com) for guidance on setting up Feature Access for your workspace.