Manage Team settings

Open Team settings from the Team switcher. Owners and admins can change the Team name and avatar. Other roles see those settings read-only.

Rename the Team

1. In Team name, edit the current name.
2. Select Save name.

The name is required and can contain up to 255 characters. synsmarts may update the Team’s URL to match the new name and then move you to the canonical URL. Existing Team links continue working.

Change the Team avatar

Use Team avatar to upload, replace, or remove the image shown in the Team switcher and Team surfaces. If no image is set, synsmarts uses initials from the Team name.

MCP access is a separate Team page, not part of Team settings. See Connect an MCP client for human Claude Code and Codex connections and MCP reference for machine access.

Leave the Team

Non-owner members can select Leave team in the Danger zone. Confirming removes access immediately. Previous activity remains part of the Team’s history, and an owner or admin can invite you again later.

Leaving revokes your human MCP connections and their tokens. Team-owned access for agents, bots, and service accounts is unchanged, even if you originally created it.

Owners can’t leave an ownerless Team. Transfer ownership to an active admin first.

Archive the Team

Only the owner can archive a Team.

1. Confirm that the Team has no active Apps. Move or deprovision them first.
2. Select Archive team in the Danger zone.
3. Review the impact and confirm.

Archiving isn’t deletion. The Team disappears from the active switcher, but its members, history, and billing records are preserved. Active and pending MCP connections and machine credentials are revoked. The owner can restore access later from account settings.

Restoring returns the Team to the switcher, and memberships resume as they were. The revoked MCP connections stay revoked: each person or machine client authorizes a replacement connection after the restore. A client still holding an old credential sees authorization errors rather than a disconnected state until it re-authorizes. An archived Team also can’t receive a transferred App until it’s restored.

If archiving is rejected, check for active Apps before retrying. Don’t deprovision an App solely to bypass the guard unless retiring that App is the intended action.