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

# Hobbes users, roles, and permissions

> Invite teammates and choose the access they need in Hobbes.

Last reviewed 2026-11-06

Give teammates the access they need to review conversations, maintain content, or administer your organization. Inviting a teammate creates access to your Hobbes organization. It is different from setting up an agent to work with your product.

Acme’s fictional administrator invites a sales teammate to review demo activity. The administrator chooses the required access and verifies that the teammate can complete the intended task in the right organization.

## Before you begin

Ask an organization administrator to send invitations. Confirm which organization the teammate should join, use their intended email address, and decide what work they need to perform.

## Choose a role

* **Viewer (read-only):** Can read organization data without making changes.
* **Member:** Can access organization data and create content. This is not permission to perform every administrative or agent-management action.
* **Admin:** Can manage organization settings and members. Administrator access is required for the agent editing, preview, and publishing controls described in the Customer Hub.

An existing **Owner** has administrator privileges. Owner is not one of the roles offered when inviting a teammate.

Choose access according to the person's responsibilities. Reading conversation results does not automatically require administrative access.

## Invite a teammate

1. Open **Settings → Members** in the intended organization.
2. Select **Invite teammates**.
3. Enter the person's **Email Address**.
4. Choose **Viewer (read-only)**, **Member**, or **Admin** under **Role**.
5. Select **Send invite**. Hobbes emails an invitation link. The link expires in 24 hours; you can resend it from the invitations list.
6. Ask the teammate to accept the invitation and check that they can access the intended organization.

If an invitation expires, resend it instead of giving the teammate someone else's account. Have an administrator review access when a person's responsibilities change.

## Success check

You're done when the invitation has been accepted, the teammate appears in the intended organization, and their access matches their responsibilities. A sent invitation alone is not confirmation that they have joined.

## Limits

Role names describe organization access, not a promise that every screen or feature is available to every role. Agent management and other administrative controls can require an administrator. Ask your administrator when a required control is unavailable.

## Summary

Confirm the organization and the access each teammate needs before inviting them or changing permissions. Verify the resulting role and ask an administrator to resolve unavailable actions.

## Related docs

* Plan the path from preparation to launch. [Implementation guide](https://docs.hihobbes.com/guides/implementation-guide.md)
* Prepare and test a visitor entry point. [Install Hobbes](https://docs.hihobbes.com/guides/install-hobbes.md)
* Review data collection, storage, and consent. [Privacy and cookies](https://docs.hihobbes.com/guides/privacy-and-cookies.md)
* Understand Agent Roles, Playbooks, and sessions. [Product concepts](https://docs.hihobbes.com/guides/hobbes-concepts.md)


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