Organizations & Team Members

Everything in HelpJet lives inside an organization: your bots, your team, your usage allowance, and your billing. This article explains what an organization is, how to bring teammates into it, and what the two organization roles let people do.

What an organization is

An organization is your workspace and your billing unit, rolled into one:

• Every bot belongs to exactly one organization.
• All bots in an organization draw from one shared pool of interactions.
• The organization holds the plan, payment method, and add-ons — see Plans & Pricing.
• Team members are invited into the organization, not into individual bots.

You can belong to more than one organization — for example, an agency managing bots for several clients — and each one keeps its own bots, members, and billing.

The organization switcher

Your active organization is shown at the top of the sidebar, with your role underneath the name. The dashboard, Usage, and Billing pages all scope to whichever organization is active.

To change it:

1. Click the organization badge at the top of the sidebar.
2. The Switch organization dialog opens, listing every organization you belong to and your role in each.
3. Click the one you want. The dashboard reloads in that organization's context.

You'll also find a small (Switch organization) link next to the organization name on the Billing and Usage pages, so you can re-scope without leaving the page.

Organization roles: admin vs. member

Every member has one of two roles:

A few consequences worth knowing:

• Only admins can create new bots.
• Only admins can upgrade, downgrade, or change payment details — members see a note directing them to an admin on the Billing page.
• Admins automatically appear on every bot's permissions list with admin-level access. Members appear only where they've been granted access.

Inviting a team member

Invitations are managed from the Users page. Open the user menu at the bottom of the sidebar and choose Users.

The page shows a card for each organization you belong to, with its member list: name, email, role, and join date. If you're an admin of that organization, you'll see an Invite User button.

1. Click Invite User.
2. In the Invite User to Organization dialog, enter the person's Email Address.
3. Pick a Role — Member or Admin. The dialog reminds you: admins can create bots and manage users; members require explicit permission to access bots.
4. Click Send Invitation.

The invitee receives an email invitation. Once they accept and sign in, they appear in the member list.

Changing a member's role

Admins can change any member's role from the same Users page. Find the member in the table and use the role selector in the Actions column to switch between Member and Admin.

Promoting someone to admin immediately gives them automatic access to every bot in the organization, plus billing control. Demoting them to member removes that automatic bot access — any explicit per-bot permissions they held stay in place.

How this connects to bot access

Organization roles answer "who runs the workspace." Access to an individual bot is a separate, finer-grained layer with its own roles (owner, admin, editor, viewer), managed per bot. Bot Permissions covers how the two layers interact.

Common questions

Can a member see the organization's usage or billing?

Members can view the Usage page for the active organization. They can't change billing — upgrade buttons and payment settings are admin-only.

What happens to someone's bots if they leave?

Bots belong to the organization, not the person. Removing a member (or their access) never deletes a bot or its training data.

Which organization gets billed when I use a bot?

Always the organization the bot belongs to. Interactions are metered on the bot, and each bot has a fixed home organization — it doesn't matter which organization you happen to have active in the switcher.

Can I rename my organization or move a bot between organizations?

Not from the dashboard today. Contact support from inside HelpJet and we can help.