Manage Team members

Open Team settings to review the Team roster. Owners and admins can manage membership. Developers and billing members can view active members but can’t change access.

Invite a member

1. Select Invite member.
2. Enter the person’s email address.
3. Choose a starting role:
   • Admin can manage members and operate Apps.
   • Developer can operate Apps but can’t manage members or billing.
   • Billing can manage billing but can’t operate Apps or manage members.
4. Select Send invite.

The owner role isn’t available in the invitation form. Ownership changes use the dedicated transfer workflow.

Send the recipient the Team invitation guide. They must use the exact email address that received the invitation.

Manage pending invitations

Owners and admins can review each pending invitation’s email, role, sent time, and expiration.

• Select Resend to send a fresh invitation. The previous invitation link becomes invalid.
• Select Revoke to prevent the invitation from being accepted.

An invitation doesn’t consume an active membership until the recipient accepts it. The Team’s membership limit is enforced when an invitation is accepted: if the Team is at its limit, the acceptance fails and the invitation isn’t consumed. Free a seat by removing a member, or contact support to raise the limit, and the recipient can then retry.

Change a member’s role

In Team members, select Change role beside an active member, choose the new role, and confirm. Grant the least access the person needs.

The owner’s role can’t be changed from the member table. Transfer ownership first if another person should become owner.

Remove a member

Select Remove beside the member and confirm the action. Access ends immediately, but the person’s previous work remains in Team history.

Removal covers Team access in one action, and leaves App-level access for you to review:

• The person’s synsmarts account continues to exist. Their memberships in other Teams are unaffected.
• Their human MCP connections for this Team are revoked in the same action.
• Machine access remains Team-owned and is unaffected, even if the removed person created it.

Caution

Removal doesn’t touch SSH users, keys, or file-transfer and database grants on the Team’s Apps. Those are App resources and stay in place. Any of them the person created become manageable by owners and admins. Review each App’s SSH page, remove what the person no longer needs, and treat the removal as complete only after that sweep.

The owner can’t be removed. The owner must transfer Team ownership first.

Leave a Team

Non-owner members can use Leave team in the Danger zone. Leaving removes your access immediately and preserves your work history. It has the same effects as being removed: your human MCP connections for the Team are revoked. Your SSH users and grants on the Team’s Apps stay in place for owners and admins to review. An owner must transfer ownership before leaving.

If the roster or invitation list doesn’t load, select Retry. Don’t assume an invitation or removal succeeded until the updated list confirms it.