Organizations
Your organization is your account in Hexcovery. It is the boundary for everything: all the metrics, logs, and traces you send, every dashboard and saved query, your API keys, and your billing all belong to one organization. An organization maps one-to-one to a tenant — the unit Hexcovery uses to keep customers' data fully separate.
What an organization owns
- All telemetry — every data point you send is tagged with your organization and is only ever visible to your organization.
- Users and teams — the people who can sign in, and how they're grouped. See Users, teams & roles.
- API keys — the org-scoped credentials used by the agent, CI/CD, and the public API. See API keys.
- Dashboards, saved queries, and alerts — built and shared within the organization.
- Billing and usage — usage is measured per organization (ingested GB).
Organization settings
Admins can edit the organization's identity and configuration. The core fields are:
| Field | Description |
|---|---|
| Name | The display name of your organization. |
| Slug | A short, URL-friendly identifier for the organization. |
| The contact email for the organization. |
These are managed from the Organization Settings page (admin only). Additional configuration — such as the AI provider and application error-rate thresholds — is covered in Organization settings.
Data isolation
Every record Hexcovery stores carries your organization's tenant identity, and that identity is enforced at every layer:
- On ingest — the agent or OTLP client authenticates with an organization-scoped API key, which determines the organization the data lands in.
- In storage — data is partitioned by tenant; one organization's data is never co-mingled with another's.
- On query — every query is automatically scoped to your organization. You cannot query another organization's data, and the scope is applied for you (you never have to add it by hand).
For the full picture of how isolation is enforced, see Multi-tenancy.
Joining an organization
Users belong to exactly one organization. To bring people in:
- An admin invites a user by email from the organization's user management. The invited person receives an invitation and joins the organization with the role the admin assigned.
See Users, teams & roles for the full invite-and-join flow and what each role can do.