Overview
Invitations are sent by email with a role and optional preassigned bots. The available roles and manageable members depend on the inviter's own role.
- Invite only roles below the inviter's management boundary.
- Give a new member the correct bot scope at acceptance.
- Resend or revoke a pending invitation when necessary.
Before you start
- Open the workspace in which the member, bot assignments, and shifts should live.
- Confirm your current role allows the team action you intend to perform.
- Use an active chatter membership before creating or editing a chatter schedule.
Step by step
- Open Team, select Members or Invitations, and choose Invite member.
- Enter the member's email and choose one of the roles available to your current role.
- Assign the bots the member should access, or leave the scope empty intentionally for later setup.
- Send the invitation and confirm it appears as pending in Invitations.
- After acceptance, open the member row and verify active status, role, and assigned bots.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Invitation hierarchy | Owners can invite Admins, Team Leaders, and Chatters; Admins can invite Team Leaders and Chatters; Team Leaders can invite Chatters. |
| Preassignment | Bots selected on the invitation become the starting scope when the invitation is accepted. |
| Pending controls | A permitted manager can resend or revoke an invitation that has not been accepted. |
| Active scope | Role and assigned bots are both evaluated when the member opens team and messaging surfaces. |
Verify the result
- The invitation email and role match the intended person.
- The pending invitation lists the intended bot assignments.
- The accepted member can reach only the expected bot scope.
Troubleshooting
| If you see this | What to check |
|---|---|
| A team action is missing | Review the Roles matrix and confirm your role can manage the target member and action. |
| A chatter cannot find a bot | Check the chatter membership is active and that the bot is assigned in Team. |
| A shift is classified unexpectedly | Compare the clock-in time, workspace timezone, and scheduled slot shown for that day. |
Best practice
Grant the smallest bot scope and role needed for the job, then verify access with the member before live coverage begins.