Browse documentation

Manage Teml

Manage a workspace and projects

Keep customer data separated by project and manage organization access safely.

A Teml organization is the team and billing boundary. Projects separate application data inside that organization. Choose a project before investigating or configuring anything; the current project in the header controls most dashboard queries.

Create and choose projects

Open Settings → Projects to create a project with a stable name and slug. Use separate projects when data needs a real access or lifecycle boundary. Use the environment field within one project for production, staging, and development when the same application should remain searchable as one system.

After creating a project:

  1. select it in the dashboard header;
  2. create or scope an application key with the required telemetry permissions;
  3. configure every participating SDK or collector with that key; and
  4. send a test signal before rolling out broadly.

An organization must keep at least one project. Deleting a project is destructive; verify which SDKs, alerts, API keys, dashboards, and automations refer to it first.

Invite and administer members

Member and invitation administration is available through the Teml CLI:

teml invitations create engineer@example.com --role ROLE_MEMBER
teml invitations list
teml members list
teml members set-role <user-id> ROLE_ADMIN
teml members remove <user-id> --yes

Only grant an admin role to people who need organization configuration or destructive capabilities. Removing a member does not rotate credentials they created; review and revoke unnecessary API keys separately.

Current organization roles are Owner, Admin, Member, Developer, and Viewer. Owners and admins receive organization configuration and destructive permissions. Member, Developer, and Viewer currently share the standard non-administrative product permissions; choose among them for team intent, but do not treat the label as an additional security boundary. Role changes take effect in a newly issued or refreshed session token.

Verify context before acting

Open Settings → Account to confirm the signed-in email, organization, and role. In the CLI, use teml projects list and teml projects use <slug> before a write. For automation, prefer a project-scoped key rather than relying on the operator to remember a project flag.