Feedback, comments and sharing

Three separate things, with three different audiences: a rating for whoever reads the run next, a comment for a named teammate, and a link for someone outside the workspace entirely.

#Feedback and scores

Rate a run or one of its spans from the trace view: thumbs up or down with an optional comment.

• Available on every plan. Members and above can review; viewers read.
• You can edit or remove your own rating.
• A paginated private feed shows every score on the trace, and the trace list carries a summary.
• Scores recorded by your code through score() sit beside human ratings, with the source recorded on each.

Scores are private to project members and follow trace and span retention. Score analytics beyond the per-prompt average are not built yet.

#Span comments Pro

A private note on one span, for the people you work with.

• Pro and Enterprise members post and edit their own comments; only the author removes one. Viewers read.
• Existing comments stay readable, and author-deletable, after a downgrade.
• Comments follow span and trace retention, and are removed with the account that wrote them.

Mentions, notifications and threaded replies are not built yet.

#Public share links Pro

The only way trace data leaves the workspace.

Lifetime

1, 7 or 30 days

Created by

Pro and Enterprise members

Revoked by

The creator or a workspace admin

Token

Hashed at rest, shown once

Create one from the trace header. Every public read rechecks the link, the trace, the project and the plan, so revoking, expiry, deletion or a plan change closes the door immediately.

What a visitor sees:

• The run and its spans, with built-in redaction reapplied and known end-user identifiers masked.
• No project navigation, no other runs.
• No scores and no comments.

Custom project redaction rules and global audit events are not built yet.

#Team and roles

Settings → Team lists members with their role, joined date and last activity, alongside invitations that are still open and the recent ones that were accepted, revoked or expired.

Every role reads everything in the workspace; the difference is what they can change.

• Projects, ingest keys, the sample project, workspace settings and team management are owner and admin only. A member who needs a new project or key has to ask.
• Owners and admins invite by email with a role — admin, member or viewer; never owner — and can resend, revoke and remove. Nobody changes their own row. An invitation link lasts 7 days, and a workspace may hold 50 open invitations at once.
• Reading the team is open to every role on every plan. Inviting needs the Pro plan and a free seat; role changes and removals stay available after a downgrade, so an oversized workspace can be brought back within its plan.
• Seats count members plus open invitations.

#Invitations

/invite/:token previews the workspace, the role and who invited you, with the address masked. It works signed in or signed out. Accepting requires a session whose verified address is the invited one, and a link used twice adds exactly one membership.

Ownership transfer, leaving a workspace and audit events for member changes are not built yet.

#Finding your way around

• Command palette — Ctrl/⌘ K: projects, pages, saved views, recent selections, theme actions, and pasting a full trace id to open it. Owners and admins also get "create project" here.
• Shortcuts — g d dashboard, g t traces, g c costs; ? opens the shortcut sheet; j/k move through a focused trace list. Shortcuts yield to typing, composition and open overlays.
• Onboarding checklist — the connection steps, with live completion from stored spans, a progress bell in the header, and owner/admin dismissal shared across the workspace. The teammate step appears only on a plan that may invite.