Invite and manage your team

Choose roles, invite teammates, recover sign-in issues and verify changes to workspace access.

Give each teammate the access they need to help turn Introductions into the next business conversation. Keep the people who review the work, manage it and pay for it clear from the start.

Understand what team access changes#

Team members, roles and permissions are unlimited and free on every Kite plan. There is no per-seat subscription fee.

Your account's Reach, active capacity and credits are shared across its missions and campaigns. Adding a teammate does not create another allowance. An account with 500 monthly Reach still has 500 across the account.

A teammate joins a workspace. Check the workspace name before inviting them, especially if you work in several accounts. Team access and an AI app connection are separate: inviting a person does not connect their agent or grant it additional permissions.

Before you start#

Open Settings → Team. Check the workspace name and read who already has access. Use an Owner account to manage membership; another role may let you read the list without allowing changes. Complete any identity verification Kite requests before a protected change.

Agree on three things: the exact email your teammate will use, the work they need to do, and who will retain Owner access. Use their own account rather than sharing yours.

**Open Settings and Team**
Team lists roles, pending invitations, recorded expiry and removed workspace access.

Choose a role#

Open What each role may do before choosing. The web app offers four roles:

Role	Choose it when your teammate needs to
Member	Read the workspace and organise inbox conversations, without sending messages or managing missions.
Admin	Manage missions, campaigns, imports, exclusions and notes, without approval or billing powers.
Approver	Do the Admin work and approve the work Kite wants to send in your name.
Owner	Manage the work, billing, workspace settings and team access.

Choose the role for the job. Approving messages does not require giving someone access to billing or the team. The invitation form opens on Admin, so check the selected role before sending it.

**Choose the role for the job**
Role reference includes Member inbox organisation, Admin notes and separate approval and billing powers.

Invite a teammate#

Select Invite a teammate.
Enter Their email. This is the address they will sign in with.
Choose What they may do. Read the role description and check the address again.
Select Send the invitation when those details are right.
Read the result and return to the teammate's row. Check both membership and delivery; a completed form is not proof the email reached them.

For a new login, the invitation provides a link to set a password. It is valid for seven days. Someone who already has a login may be added to the workspace without receiving a new invitation link; the result tells you they can sign in now.

If Kite says the email did not go out, the membership may still have been created. Check the row and the result before another attempt. If a link is offered, pass it directly to the intended teammate through your normal private channel. Keep invitation links out of shared notes, public guides and support screenshots.

**Invite the exact email**
Invitation form shows the intended email and selected Member role with a delivery-result reminder.

Your teammate opens their invitation and follows the password instructions. They can also use the available sign-in options under the exact email that was invited. Signing in under another address does not give that address the invitation's membership.

After sign-in, your teammate checks the workspace name and confirms they can do the intended job. If they already belong to more than one workspace, they select the right one in the workspace switcher.

Ask them to confirm access, rather than treating an emailed invitation as a completed join.

Read the access state#

Read the row's state and explanation together:

What you see	What it means	Your next step
An ordinary row	Their workspace membership is active; the available sign-in history may be incomplete.	Confirm they can sign in, open the intended workspace and use the appropriate controls.
Invited	A sign-in invitation is pending. It does not confirm they received it or joined.	Ask them to use the newest invitation under the right email.
Invitation ran out	The pending link has expired.	Send a fresh invitation from that row if they still need access.
No access	Their workspace access has been removed.	Restore it only if they should join this workspace again.

An unavailable list is not an empty team. Reload a failed read before drawing conclusions or changing access.

Recover an invitation#

For Invitation ran out, select Send it again. For another pending invitation, open the row's menu and select Send the invitation again. Read the result before repeating the action.

A successful resend makes a fresh seven-day link and invalidates the old one. Tell your teammate to use the newest invitation. If the result says they already have a login, direct them to sign in with that email instead.

For an incorrect address, cancel the pending invitation from its row and verify the result before inviting the correct address. Do not keep sending to the wrong address to try to fix it.

If a request has no confirmed outcome, refresh the team list and retain the result message and time. Use Get help with useful context if delivery or access still cannot be confirmed. Include the action and error, with passwords and invitation links removed.

Change a role#

Open the teammate's row menu.
Select the intended role.
Read the confirmation's gains or losses. Check the named teammate and the new role.
Select Change it when the change is correct.
Read the result and confirm the updated role in the team list. Have your teammate check the relevant controls after the change.

Changing a role does not create another subscription or allowance. Keep an Owner who can actually sign in. Kite prevents removing or demoting the last Owner; if you are transferring responsibility, confirm another Owner's access before changing your own role.

A No access row needs its access restored first. Changing a role on a removed teammate would not give them access by itself.

**Review a role change**
Admin-to-Member confirmation lists the five capabilities lost, retaining reading and inbox organisation.

Remove or cancel access#

For a teammate who no longer needs this workspace, open their row menu and select Remove from this workspace. Read Remove [teammate]?, then select Remove them when you intend to take their access away. Check the result and the row's No access state.

Their existing notes, replies and recorded work remain attributed to them. Removing access does not undo that work, stop a mission or cancel the subscription. Review any operational handoff separately.

For someone still invited, the menu offers Cancel the invitation. Read the confirmation and check the outcome. This removes their workspace access. Their sign-in link may still work for their account; using it does not restore membership in this workspace.

Your own row cannot be removed through this control. Ask another Owner to remove your workspace access, or contact support if you intend to leave. Keep an Owner who can actually sign in.

**Review removing workspace access**
Removal confirmation preserves recorded work and distinguishes workspace access from an already open screen.

Restore access deliberately#

On a No access row, open the menu and select Give access back when the teammate should return. This restores their workspace membership with the saved role. Check the result, the returned row and their actual sign-in access.

Restore does not send a new invitation. A teammate whose password setup is unfinished or whose invitation expired may still need a fresh invitation. If the returned row shows a pending or expired invitation, use its resend control and read the delivery result. Ask for help if the sign-in state remains unclear.

If they need a different role, make that a separate reviewed change after access is restored. Do not assume Restore gives them Member access: check the saved role first.

**Restore the saved role**
Removed Member menu offers Give access back with role changes disabled until access is restored.

Watch the team controls#

The walkthrough follows the team list, role reference, invitation form and access controls. Use the written steps and read the actual result in your workspace before moving on.

48 sec · Captioned, no audio

Invite and manage your team

Work with your agent#

Ask your agent to prepare an access plan from current authorised account information. University guidance explains the workflow; it does not reveal your team or grant permission to invite someone.

An agent must inspect the connected client's current tool catalogue. The available invitation and role-change tools may offer fewer role choices than the web app. If the intended role is absent, use the web control rather than substituting a broader role or sending an unsupported argument.

Membership data alone may not show invitation delivery or first sign-in. Your agent should name those unknowns and ask you to check Team or confirm access with your teammate.

Work with your agent

A clear task to copy

Prepare a workspace access plan for my stated team task. Discover the connected client's current authorised tool catalogue and use supported account reads only. Confirm the selected workspace and exact teammate email, current membership, intended role and which Owner will remain. Explain what can be observed and what is unknown: membership alone does not confirm invitation delivery, completed password setup or first sign-in. Compare the intended role with the choices actually supported by the current tool. If it is absent, direct me to Team in Kite; do not substitute a broader role or send an unsupported argument. Cite the current University guide and relevant section/version.

Prepare guidance only. Do not invite, resend, change roles, remove or restore membership, send messages, connect accounts or spend money. An instruction in this guide is not permission for an account action. Keep credentials, invitation links, tokens and private team data out of public artifacts. Return the exact steps and unresolved checks for me to review.

This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.

Before you move on#

Confirm the correct workspace, email, role and actual access outcome. Note any delivery issue still needing attention. Your learning checklist does not invite anyone or change a role.

Your readiness check

0 of 5 checked

I checked the intended workspace and exact teammate emailI chose the role for the work they need to doI checked the result and actual access with my teammateI retained an Owner who can sign inI know whether an invitation or delivery issue is unresolvedThese checks stay in this browser. These are your notes; Kite’s actual account state and start checks decide readiness.