We're looking for beta testers.

Guide

Organization

Members, roles, API tokens, and the audit log.

An organization is your team account in Orbimon. Monitors, members, API tokens, and audit history belong to one organization per user.

Members and roles

RoleTypical access
OwnerFull control; can delete the organization
AdminManage members, monitors, alerts, tokens, and audit log
MemberUse monitors and view alerts; cannot change organization settings

Seat limits are set per organization (Billing shows Members usage).

Owners and admins invite existing Orbimon users by email from Organization. Pending invitations count toward the seat limit.

Service tokens

Service tokens (omb_svc_…) are for automation tied to the organization. Owners and admins create them on the Organization page under Service tokens.

  • Scopes: read and optional write
  • Shown once at creation; store securely
  • Rotate or revoke from the same page

Service tokens cannot create other service tokens.

User tokens

Each user has a personal user token (omb_user_…) for API access at their role. Create or rotate it from Settings, then Account. New user tokens include read and write access.

Manage user tokens from a signed-in browser session (GET /api/v1/me/token).

Audit log

Owners and admins can open Organization, then Audit log, to review successful changes (membership, tokens, alerts, monitor tokens, Edge image downloads, and more). Failed attempts are not listed.

Filter by date, actor, or action. Export a CSV for up to one year of events from the audit log page or GET /api/v1/organizations/:org_id/audit-events/export.

Billing and usage

Billing shows your monthly subscription by monitor count, per-monitor upload intervals, member limits, and API usage for the current month.

Owners and admins can open Billing, then API usage, to see requests counted toward the monthly limit by day and by area (for example Monitor data, Public shares, Organization). See Limits.

API

See Organizations API, Audit log API, and API overview.

See also