Projects & KeysCopy Anchor Link

Owlpane isolates data through a three-level tenancy model. Where you create and manage keys depends on which level a credential belongs to.

• User — a person who signs in to the console at console.owlpane.com.
• Organization (your workspace) — the top-level tenant. It owns projects, and telemetry is partitioned per organization.
• Project — one per app or service. It owns the ingest keys that send telemetry.

Manage projects under Settings → Projects (/settings/projects) and workspace details under Settings → General (/settings/general).

Key prefixesCopy Anchor Link

There are exactly these two credential types. Ingest keys cannot read data back, and API tokens are not used for telemetry ingestion.

Tenant isolationCopy Anchor Link

Telemetry is partitioned per organization. A project belongs to exactly one organization, and its ingest keys only ever write into that organization's data. There is no credential that spans two organizations, so a leaked key cannot reach another tenant's telemetry — but it can still write into your own project, so rotate and revoke it promptly (see below).

Ingest keysCopy Anchor Link

Each project has its own owl_ing_ keys, sent to ingest.owlpane.com. A project can hold several keys so you can separate senders (for example one for production collectors and one for a CI environment) and rotate without downtime.

Key values are shown once at creation; Owlpane stores only a hash. If a key is lost, issue a new one and revoke the old one.

Passing an ingest keyCopy Anchor Link

Send the key with each OTLP request using either header:

• Authorization: Bearer owl_ing_...
• x-owlpane-key: owl_ing_...

See Ingest Keys & Authentication for the full set of header options.

Creating a projectCopy Anchor Link

1. Open Settings → Projects and choose New project.
2. Give it a name and pick an environment (production, staging, or development).
3. Owlpane creates the project with its first owl_ing_ key and shows connection instructions. Copy the key now — it is shown once.

A project row shows whether it is receiving data, and lists its keys with their prefix, name, creation time, and last-used time.

Rotating and revoking keysCopy Anchor Link

There is no rotate-in-place for ingest keys. To rotate safely:

1. Create a new owl_ing_ key in the project.
2. Roll the new key out across your collectors or SDK deployments.
3. Verify incoming traffic in the console.
4. Revoke the old key.

Revoking a key takes effect immediately: anything still sending data with it is refused. Rotation is deliberate and explicit — there is no automatic overlap window you can rely on, so complete the rollout before revoking.

Project settingsCopy Anchor Link

From a project you can edit:

• Name and environment — new data is filed under the new environment within about 30 seconds.
• Repository URL — used for commit links on the incident timeline.
• Session replay retention (days) — how long browser session timelines are kept for this project, up to your plan's replay-retention cap (see Audit & Retention).

Deleting a projectCopy Anchor Link

Deleting a project permanently removes all telemetry recorded for it and its keys, and anything still sending data is refused. This cannot be undone — export what you need first.

RelatedCopy Anchor Link

• API Tokens — workspace-scoped automation credentials.
• Quotas & Limits — project caps by plan.
• Quickstart — send your first telemetry.