Why Teams?
Teams organize shared designs and membership separately from your personal chat sessions. Available management, project and AI actions depend on current permissions and entitlement, not membership alone.
Quick Start
- Open Teams at buildwithtrace.com/dashboard/teams.
- Select the intended team, or use Create Team if your account is eligible.
- Open its Projects tab for shared designs.
- Use the offered membership/settings controls to invite collaborators.
- In Trace desktop, use Workspaces to add or open a permitted cloud project and check its checked-out branch.
Use the team picker inside the team's page to change teams. Selecting a web team does not switch the native editor's open project.
Plans and Pricing
Check current pricing, the team's billing screen and checkout for available plans, seats and allowance. Team access, paid-seat entitlement and project capabilities are separate. Membership does not guarantee unlimited AI, an automatic plan change or a particular fallback subscription.
Roles and Permissions
Owner, Admin and Member describe team roles. The current server permissions determine which controls you can use. A role label is not a universal grant to edit, Push, merge, manage billing or change another member.
Project-specific access can differ from team-management access. A reviewer may read a project without authoring or publication permission. Native working-copy authority and supported client capabilities also apply.
Changing Roles
Open the intended team, find the member and use the offered role controls. If a role change is unavailable, ask an authorized team manager rather than assume your role should permit it. Use a supported ownership-transfer flow or contact support; do not delete and recreate the team to transfer ownership.
Access Levels
Read the access shown for the team member and individual project. View-only does not grant authoring or publication. Full access still depends on the project's permissions, current account entitlement and supported host. Neither label bypasses native review or gives the AI permission to merge.
Invite Policy
The team's invite policy can restrict who sends invitations. Check Settings and the permissions of the signed-in account; do not infer invitation rights from the presence of a member list.
Inviting Members
- Open the intended team's membership page.
- Enter the invitee's email and select an offered role.
- Review any seat or billing notice, then choose Send Invite.
- The invitee signs in using the invited email and accepts the invitation.
How Invites Work
Use the current valid invitation. If it expired, was revoked or targets a different email, ask an authorized manager to check or resend it. Review pending invitations before sending another; an email delivery delay does not establish that no invitation exists.
Seat Limits
Use the seat limit and pricing shown in the current team account. If a limit blocks an invitation, ask the billing manager to review capacity. Do not remove a collaborator merely to bypass an unexplained entitlement error.
Team projects and personal sessions
The dashboard's Teams page is /dashboard/teams. A selected team's projects
live at /dashboard/t/{teamId}/projects; the team in that URL is authoritative.
Personal chat sessions live separately at /dashboard/sessions. Team Projects
lists shared designs, not everyone's personal conversations.
Add a separate saved copy through Add a saved project.
Review included content, especially the shared .trace/context.md.
Personal .trace/rules.md and earlier source chats/history are not silently
shared. Save and Commit remain local; Push publishes to the checked-out branch.
Workspaces collaboration is branch/revision synchronization, not live co-editing.
Billing
Use the team's offered Billing controls to inspect seats, invoices, payment methods and subscription status. Review checkout before accepting a change. Do not assume that membership changes immediately update an invoice or cancel a subscription.
What Happens to Members' Plans
After joining or leaving a team, inspect your current account access and Billing. Personal subscriptions, purchased credits, team coverage and fallback behavior must not be inferred from a role change.
Leaving a Team
Use Leave Team when offered and review the access/billing consequences. Preserve work you are authorized to keep before leaving. An owner may need a supported ownership transfer first; ask support if the control is unavailable. Team content does not become personal content simply because you leave.
Removing Members
An authorized manager can select the member and use the removal control. Review the consequences before confirming. Permission loss can block future project operations; it does not prove an earlier uncertain Push or merge had no effect. Use original-operation recovery.
Deleting a Team
A deletion response is not proof of complete data erasure or successful billing cancellation. Confirm those outcomes through the appropriate account/support path.
Troubleshooting
- Wrong team or unavailable project: return to Teams and choose a team you can access. An old URL does not grant permission.
- Invitation missing: check the email address, pending invite and spam folder.
- Access or billing disagrees after joining: refresh the current account view and ask support; do not assume a guaranteed propagation time.
- Cloud project will not open: preserve the confirmed addition and recover its Open/Pull operation rather than add another copy.