Settings

The Settings page (/settings) is where you manage your project configuration, access credentials, team members, and billing. Settings are scoped to the current project unless noted otherwise.

General

The General tab contains basic project configuration.

Project name

The display name for your project. This appears in the sidebar, page titles, and any shared links. Changing the name does not affect API keys or data — it is purely cosmetic.

Default time range

Set the default time range for the Traces, Spans, and Analytics pages. When a team member opens the dashboard, this range is pre-selected. Individual users can override it, but the default is useful for establishing a team-wide baseline.

Options: Last 1 hour, Last 24 hours, Last 7 days, Last 30 days.

Data retention

In cloud mode, configure how long trace and span data is retained before automatic deletion. Retention is measured from the trace creation timestamp.

Deleted data cannot be recovered. Export data before the retention window closes if you need it long-term.

API Keys

API keys authenticate SDK and API requests to your project. Each key is a string prefixed with tw_sk_.

Creating a key

1. Navigate to Settings > API Keys and click Create key.
2. Enter a name for the key (e.g., "production", "staging", "ci-pipeline").
3. Select permissions:
   • Read — Can read traces, spans, datasets, and analytics
   • Write — Can create traces, spans, and datapoints
   • Admin — Full access including settings and team management
4. Click Create. The full key is displayed once — copy it immediately.

The key is shown only at creation time. If you lose it, revoke the old key and create a new one.

Revoking a key

Click Revoke next to any key to disable it immediately. Revoked keys return 401 Unauthorized on all requests. In-flight requests using the revoked key will fail.

Revocation is instant and irreversible. Any services using the key will stop working, so update your configuration before revoking.

Key best practices

• Use separate keys for each environment (production, staging, development).
• Use read-only keys for dashboards and monitoring tools.
• Rotate keys periodically — revoke the old key after deploying the new one.
• Never commit keys to source control. Use environment variables or a secrets manager.

Team

The Team tab manages who has access to the project. Team membership is scoped to the organization, with per-project role assignments.

Inviting members

1. Click Invite member.
2. Enter their email address.
3. Select a role:
   • Viewer — Read-only access to traces, spans, analytics, and datasets
   • Member — Can create and manage traces, datasets, and eval runs
   • Admin — Full access including settings, team management, and billing
4. Click Send invite.

The invitee receives an email with a link to join. If they don't have a Traceway account, they'll be prompted to create one. The invite expires after 7 days.

Removing members

Click the menu icon next to a team member and select Remove. They lose access immediately. Their past activity (claims, approvals, comments) remains in the system but is attributed to "removed member".

Roles

Billing

The Billing tab shows your current plan, usage, and payment details. Billing is scoped to the organization — all projects under the same org share a plan.

Plans

Usage

The usage section shows:

• Traces this month — Current count vs. plan limit
• Spans this month — Total spans created
• Storage used — Disk/object storage consumed
• Eval runs this month — Number of eval runs executed

A progress bar shows how close you are to each limit. You receive email alerts at 80% and 100% usage.

Upgrading

Click Upgrade to switch to a higher plan. The change takes effect immediately. You're billed a prorated amount for the remainder of the current billing cycle.

Payment

Add or update payment methods in the billing section. Traceway uses Stripe for payment processing. Invoices are available for download from the billing history.