Skip to main content
Use the Members feature to invite team members to collaborate on your chatbot. Assign different roles to control what each member can access and modify.

Member roles

SiteGPT offers four member roles with different permission levels:

Agent

Permissions:
  • View and respond to chat history
  • Access lead information
  • Cannot invite other members
  • Cannot modify chatbot settings
Best for: Customer support team members who need to handle conversations and view leads.

Manager

Permissions:
  • All Agent permissions
  • Edit chatbot settings and content
  • Manage training data and integrations
  • Invite Agents
  • Cannot invite other Managers or Admins
Best for: Team leads who need to configure the chatbot and manage support agents.

Admin

Permissions:
  • All Manager permissions
  • Invite and remove Managers and Agents
  • Invite other Admins
  • Cannot invite Super Admins
  • Cannot delete the chatbot
Best for: Department heads or project managers who need full control over team access.

Super admin

Permissions:
  • Full access to everything
  • Can delete the chatbot
  • Highest level of control
Best for: Chatbot owners or senior administrators who need complete control.
The chatbot creator is automatically assigned the Super Admin role and cannot be removed from the chatbot.

Inviting members

  1. Navigate to your chatbot dashboard
  2. Select Members from the Advanced section in the sidebar
  3. Enter the team member’s email address
  4. Select their role from the dropdown menu
  5. Click Send Invite
The invited member will receive an email with a magic link to access the chatbot. They’ll need to click the link to accept the invitation and gain access.
Members don’t need to create a separate account. They can access the chatbot using the magic link sent to their email.

Member quotas

Your plan includes a specific number of team members. The member quota applies across all chatbots you own:
  • Starter: 1 member (you)
  • Growth: 4 members
  • Scale: 10 members
  • Enterprise: Up to 1,000 members
Member quotas count unique team members across all your chatbots. If you invite the same person to multiple chatbots, they only count as one member toward your quota.

Managing members

Viewing members

The Members page displays:
  • Active members: Team members who have accepted invitations
  • Pending invitations: Invites that haven’t been accepted yet
Each member listing shows:
  • Name or email address
  • Profile picture (if set)
  • Assigned role
  • Remove/Leave button

Changing member roles

To change a member’s role:
  1. Remove the member from the chatbot
  2. Send a new invitation with the desired role
You cannot directly change a member’s role. You must remove and re-invite them with the new role.

Removing members

To remove a member:
  1. Navigate to Members in your chatbot dashboard
  2. Find the member you want to remove
  3. Click Remove next to their name
  4. Confirm the removal
Removed members immediately lose access to the chatbot and cannot view chat history, leads, or settings.

Leaving a chatbot

If you’re a member (not the owner) and want to leave a chatbot:
  1. Navigate to Members
  2. Find your own entry in the member list
  3. Click Leave
  4. Confirm you want to leave
Once you leave a chatbot, you cannot rejoin unless the owner or an admin sends you a new invitation.

Canceling pending invitations

To cancel an invitation that hasn’t been accepted:
  1. Navigate to Members
  2. Scroll to the Pending Invitations section
  3. Find the invitation you want to cancel
  4. Click Delete next to the invitation

Role permissions matrix

PermissionAgentManagerAdminSuper Admin
View chat history
Respond to chats
View leads
Edit chatbot settings
Manage training data
Configure integrations
Invite Agents
Invite Managers
Invite Admins
Remove members
Delete chatbot

Best practices

Give team members the lowest role that allows them to do their job. This reduces the risk of accidental changes to important settings.
Customer support representatives typically only need Agent access to view and respond to conversations.
Only assign Super Admin to trusted individuals who need the ability to delete the chatbot.
Periodically audit your member list and remove team members who no longer need access.
Follow up on pending invitations that haven’t been accepted after a few days. The recipient may not have received the email.

Common use cases

Customer support team

Team Structure:
- Support Manager (Manager role)
- Support Agents (Agent role)

The manager configures the chatbot and manages training data.
Agents handle customer conversations and view lead information.

Marketing and sales team

Team Structure:
- Marketing Director (Admin role)
- Content Manager (Manager role)
- Sales Representatives (Agent role)

The director manages team access and high-level strategy.
The content manager updates chatbot content and responses.
Sales reps engage with leads and track conversations.

Multi-department collaboration

Team Structure:
- IT Administrator (Super Admin role)
- Department Heads (Admin role)
- Team Leads (Manager role)
- Team Members (Agent role)

Clear hierarchy ensures proper access control across departments.

Troubleshooting

  • Check that the email address is correct
  • Ask them to check spam/junk folders
  • Resend the invitation by deleting the pending invite and creating a new one
  • Verify your email sending quota hasn’t been exceeded
You’ve reached your plan’s member quota. Options:
  • Remove inactive members to free up slots
  • Upgrade to a higher plan with more member slots
  • Contact support for custom enterprise limits
  • Remove the member from the chatbot
  • Send a new invitation with the correct role
  • Confirm they accept the new invitation
The chatbot creator (Super Admin) cannot be removed. To transfer ownership:
  • Create a new chatbot under the desired owner’s account
  • Migrate content and settings to the new chatbot
  • Delete the old chatbot if needed

Member quota across chatbots

Member quotas are calculated based on unique email addresses across all chatbots you own: Example:
  • You own 3 chatbots
  • You invite john@example.com to all 3 chatbots
  • This counts as 1 member toward your quota
Another example:
  • Human support - Configure how team members receive escalated conversations
  • Chat history - View and manage conversations
  • Leads - Access lead information collected by your chatbot
  • Profile - Manage your personal account settings
I