Settings
Workspace settings in the TestRelic Console — general details, members, workspaces, sign-in and API key policy, webhooks, the audit log, and data retention and privacy.
Settings (console.testrelic.ai/settings) has seven tabs: General, Members, Workspaces, Security and SSO, Webhooks, Audit log and Data and privacy. Everyone can view them; only Owners and Admins can change them (any member can create a workspace).
General
| Field | Rules |
|---|---|
| Workspace name | 2–64 characters. |
| Description (optional) | Up to 200 characters. |
Click Save changes. Details shows the Workspace ID (copy it: "Use the workspace ID when you contact support."), the region, when the workspace was created, and your role.
Members and Workspaces
Inviting people, accepting invitations, roles, ownership and creating workspaces are covered in Workspaces and members.
Security and SSO
Sign-in
Members sign in with their TestRelic account, the same login as the TestRelic platform. Manage password and two-factor opens that account.
Session length
How long members stay signed in to the Console before signing in again:
| Option | Behaviour |
|---|---|
| 12 hours | Default. Extends while you're active. |
| 8 hours, 4 hours | Counted from sign-in. |
| 1 hour | Strictest. Counted from sign-in. |
Members see "<Workspace> asks members to sign in again every N hours."
Invite domains
Allowed email domains: up to 20, for example example.com. Only addresses at these domains can be invited. Leave it empty to allow any address. Existing members aren't affected.
API key policy
Applies to keys created from now on; existing keys keep their settings.
| Option | Values |
|---|---|
| Maximum key lifetime | No limit (keys can be non-expiring), or Must expire within 365 / 90 / 30 days |
| Require an IP allowlist on full-access keys | On or off |
Click Save security settings. See API keys for what happens when a key breaks the policy.
Single sign-on and enforced two-factor
Coming soon: sign-in through your identity provider (Okta, Microsoft Entra ID, Google Workspace) over SAML or OIDC, with two-factor required for every member. Request SSO records your interest; we'll reach out when it's available.
Webhooks
Send workspace events to your own endpoint. See Webhooks.
Audit log
Every change in the workspace, "Kept for 400 days". Each entry has the time, who did it (an email, or System for automatic events), the event and a detail line. Export CSV downloads up to 5,000 entries with the columns time,actor,event,detail.
| Area | Events |
|---|---|
| API keys | api_key.created, api_key.updated, api_key.revoked |
| Billing | billing.topup_started, billing.topup, billing.auto_topup, billing.topup_failed, billing.auto_topup_failed, billing.coupon_redeemed, billing.profile_created, billing.profile_updated, billing.settings_updated, billing.spend_alert |
| Members | member.invited, member.invite_resent, member.role_changed, member.invite_revoked, member.removed, member.joined |
| Workspace | org.created, org.updated, org.security_updated, logs.purged |
| MCP | mcp.tool_enabled, mcp.tool_disabled |
| Webhooks | webhook.created, webhook.updated, webhook.enabled, webhook.disabled, webhook.secret_rotated, webhook.deleted |
| Other | waitlist.joined |
Data and privacy
Data region
The workspace's region, set when it was created. "Request logs, usage and billing records stay in this region. Inference runs in US data centres." Today every workspace is in N. Virginia (us-east-1); Dublin and Mumbai are coming soon. A workspace's region can't be changed.
Request logs
| Setting | Options |
|---|---|
| Request log retention | 30 days (default), 7 days, or Zero retention ("Request logs are off. Usage and billing still count every call."). |
| Store request and response bodies | On by default, up to 16 KB each. Off keeps only time, task, status, latency, cost and key. |
Zero retention also turns off Playground history.
Delete request logs
Delete all request logs permanently deletes every stored request log after you confirm. Usage, billing and the audit log aren't affected, and the deletion is recorded in the audit log (logs.purged).
Webhooks
Send TestRelic Console events — top-ups, spend alerts, key, member and MCP tool changes — to your own HTTPS endpoint, test it, rotate its signing secret and watch its deliveries.
Deployments
Dedicated Ostra deployments are coming soon to the TestRelic Console; today every request runs on the shared serverless service, and Enterprise customers can run Ostra in their own environment by arrangement.