Teams

If you’re using Traces in a team, this is the quickest path:

1. create an organization,
2. invite teammates,
3. publish traces for your org,
4. switch namespaces in the TUI.

This page walks through those first-team workflows.

1) Creating an Organization

Every team workspace in Traces is an organization namespace.

1. Open the web app and sign in.
2. Go to Organizations (/settings/organizations).
3. Click New organization.
4. Pick a name and confirm an available slug.
5. Save.

When the org is created, you become its admin and your active namespace switches there automatically.

Prefer the CLI? Use:

traces org new "Acme"

See CLI Reference for the full command docs, including --json output.

You can also create org namespaces via API:

POST /v1/namespaces
{
  "slug": "acme",
  "displayName": "Acme Engineering",
  "type": "org"
}

2) Inviting Team Members

As an org admin, open your org settings and members page:

1. Navigate to your org profile (/your-org).
2. Open Settings → Members.
3. In Pending Invites, click Create Invite.
4. Pick usage limits (unlimited, 1, 5, 10, 25) and generate a link.
5. Share the invite link with teammates:

https://traces.com/invite/<code>

Teammates can accept the invite via that link.

If you prefer the CLI, org admins can also create invite codes with:

traces acme invite code --email jane@example.com --max-uses 1
# or
traces org invite acme code --json

See CLI Reference for the full invite-code command docs and flags.

• Invite links expire in 7 days.
• Non-admin members can only see existing members and cannot create invite links.
• If the link is expired/revoked/used up, generate a new one.

3) Publishing Traces for Your Team

Publishing is namespace-scoped: a trace lives in the currently active namespace.

In the TUI

• Open the TUI (traces with no command).
• On the trace list, select a row and press space.
  • If the trace is unpublished, this publishes it.
  • If it is already published, this opens the unpublish flow.

For org namespaces, Traces defaults new shares to private. For personal namespaces, it defaults to direct.

If you need explicit visibility:

traces share --trace-id <external-trace-id> --visibility public
# or
traces share --trace-id <external-trace-id> --visibility private
# or
traces share --trace-id <external-trace-id> --visibility direct

Visibility meanings:

• private: only members of the active namespace can view.
• direct: hidden from public discovery, visible to members and anyone with the direct link.
• public: appears in public discover/feed surfaces.

Best practice for teams

When you want a trace to be visible to the org for collaboration, keep it private by default.

4) Switching Namespaces in the TUI

Use the TUI namespace switcher to move between personal and org workspaces quickly.

1. In the list or detail view, press n.
2. Use j / k (or arrows) to move through the namespace list.
3. Press return to switch.
4. Press escape or n to close the switcher.

After a successful switch, the TUI reloads traces and updates ownership context for publish/unpublish actions.

Tip: if you want repo-specific defaults, you can also use .tracesrc (for example namespace = @acme) so the CLI auto-selects a namespace when run in that directory.

Next up:

• Adding Members
• Privacy Settings