# Team & Permissions

VoiceHub lets you manage your team at a granular level by assigning roles, permissions, and access control for every major function.

### **Team Sections**

Navigate to Team & Users to manage the following:

* Contributors: List of active workspace members
* Users: Invite users/customers by email and assign predefined roles (admin or viewer)
* Roles: Define and customize access rules with fine-grained permissions

### **Invite Members**

1. Click + Add Member
2. Enter the email address
3. Select a role (e.g., admin or viewer)

🔐 Invited users will receive an email and must use workspace-specific login to access the platform.

### **Roles & Permissions**

Click the Roles tab to view and create custom access levels. Each role can be granted specific permissions:

**Workspace/Platform Access**

* ✅ Settings Access
* ✅ White Labeling Access
* ✅ Manage Teams
* ✅ Provider Keys Access

**Agent-Level Features**

* ✅ Call Logs User Access
* ✅ Call Logs Full Access
* ✅ Can Make Calls (VOIP)
* ✅ Widget Access
* ✅ CallStudio Access

**Campaigns & Content Access**

* ✅ Phonebook View Access
* ✅ Phonebook Write Access
* ✅ Knowledge Base View Access
* ✅ Knowledge Base Write Access
* ✅ QA Tests Access
* ✅ Analytics Access

You can mix and match permissions when creating a new role. Example roles:

* Support QA → View call logs, manage CallStudio and QA Tests
* Billing Admin → Full widget + call access, no editing permissions
* Partner Viewer → View-only access to logs and analytics

This system allows you to mirror your organization’s structure securely inside VoiceHub.

You’re now ready to deploy high-quality voice agents with VoiceHub.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dataqueue.gitbook.io/voicehub-docs/agent-design-and-usage/team-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.