Team & Members
Invite members and control page-level access to your AlonChat projects
Team & Members#
Add members to a project and control which dashboard pages each person can see and manage.
Accessing Members#
- Go to your project dashboard
- Click Settings in the sidebar
- Select Members
The page shows seats in use, such as 3 / 5 seats, or unlimited when the plan has no cap. Those
numbers come from the current plan. Compare the allowance in project Settings → Plans.
Who you can invite#
Open Invite members, enter an email, pick one access type, and click Invite. Only owners and admins can send invitations.
| Access | Who it's for |
|---|---|
| Inbox Responder | Activity inbox and live handover only. No tickets, CRM, or settings |
| Support Agent | Inbox, tickets, human review, and CRM. No settings or billing |
| Admin | Dashboard pages, with Plans, Billing, and Audit Logs view-only. Cannot delete the project or become Primary Owner |
| Owner | Full access, including billing changes and project deletion. Only an owner can send this invite |
There is no Editor or Viewer role.
The invitee gets an email with the project name, who invited them, and a link to accept. They need an AlonChat account if they do not have one. Each invitation expires 24 hours after it is sent. Pending invitations shows the time left.
| Action | What it does |
|---|---|
| Resend | Sends the invitation email again |
| Cancel | Revokes the invitation |
Access shapes on the Members list#
After someone joins, their badge can stay on the invite type or match a tighter shape. Open Customize role access from the member menu to change pages. A shape appears when the page levels match it.
| Shape | What they can open |
|---|---|
| Owner | Every page, including billing changes and project deletion |
| Admin | Every page they can open. Plans, Billing, and Audit Logs stay at View |
| General Staff | View access to Test, Activity, Ticketing, Human Review, CRM, Analytics, AI Assistant, Sources, and Source Health |
| Support Agent | Manage Activity, Ticketing, Human Review, and CRM |
| Inbox Responder | Manage Activity only |
| Analyst | View CRM and manage Analytics |
| Tickets Only | Manage Ticketing only. No inbox, CRM, analytics, or setup pages |
| Custom Role | A mix that does not match a shape above |
Project General settings, including the project name and Delete Project, are owner-only even when another page says General.
Primary Owner#
A project always has one Primary Owner. Other people can also be Owners. Make primary owner moves the billing and default owner record to that person. Both of you remain owners.
Page-level access#
Customize role access sets each dashboard page to one of three levels, up to what that role allows. Members cannot be given Actions, Outbound, Deploy, agent Settings, or project settings. Admins cannot be raised above View on Plans, Billing, and Audit Logs.
| Level | Meaning |
|---|---|
| Hidden | The page is not visible to this member |
| View | The member can see the page but not make changes |
| Manage | The member can see and edit the page |
The page names on that screen are Test, Activity, Ticketing, Human Review, AI Assistant, CRM, Outbound, Sources, Source Health, Analytics, Actions, Deploy, Settings, General, Members, Queues, Plans, Billing, and Audit Logs. Queues is the project Teams page. Actions is the Agent Studio area for Tools, Procedures, and Workflows. Sources and Source Health are the Agent Studio knowledge pages.
Access is project-wide but page-level: a member can reach every agent in the project, but only through the pages their access allows.
Ticket access#
The Members list has a Ticket access switch. Turn it on so that member can be assigned tickets. Owners and admins already have management access, and their switch stays on. Other members show Available, Paused, or Off. This switch does not change how many project seats the plan includes.
Managing members#
| Action | Where |
|---|---|
| Change role | Member menu. Switches Owner, Admin, or Member |
| Customize role access | Member menu. Sets Hidden, View, or Manage per page |
| Ticket access | The switch on the member row |
| Remove | Member menu, then confirm |
Changes apply when they are saved. Removed members lose access immediately and need a new invitation to rejoin. Sources and other project data they created stay in the project.
Seat limits#
Do not assume a published seat count. The Members page shows this project's usage. Project Settings → Plans shows the allowance you can buy. Need more seats? Change the plan there, or contact sales@alonchat.com.
Audit Logs#
When your plan includes them, open Settings → Audit Logs to see who changed project settings or membership, and when.
Best Practices#
- Give each person the smallest invite type that covers the job, then tighten pages with Customize role access
- Review the Members list when people change roles
- Remove access when people leave
- Turn on Ticket access only for people who work tickets
Frequently Asked Questions#
Can I transfer ownership?#
Yes. Use Make primary owner on another owner's menu. They become the billing owner, and you remain an owner. Contact support if you cannot complete the transfer.
Who can access billing?#
Owners can manage Billing. Admins can view it. Members cannot be given the Billing page.
Can I restrict access to specific agents?#
Not at the agent level. Access is project-wide. Hide the pages a member should not use.
What happens when I remove someone?#
They lose access immediately. Data they created, such as sources and Q&A pairs, remains in the project.