organizations & teams

Everything in pngr is scoped to an organization — monitors, channels, rules, incidents, tokens, and audit history all belong to one org. Every user belongs to at least one org and can belong to several.

your default org

Signing up creates a default org automatically. Rename it from /settings/general (name, slug, logo), or create more orgs as you need them. The active org lives in the sidebar switcher; switching changes which org's data every page shows. The active org is remembered across sessions.

inviting teammates

From /team, the members, invitations, and roles & permissions tabs cover team management:

• Invite by email — pick a role and send an invite link. Invitations expire in 7 days; resend or cancel them from the invitations tab.
• Change a member's role or remove a member from the members tab.
• Transfer ownership to another member, or leave an org. The owner can't leave until they transfer ownership first.

Invitees land on an accept-invite page that ties the invitation to their account (existing or newly registered).

deleting an org

Deleting an org is owner-only and lives under /settings/danger-zone. It soft-deletes — monitors and data are archived, not immediately purged.

audit log

Every meaningful change is recorded in the org's audit log (/settings/audit-log): who did what, to which resource, and when, with the action, resource type/id, actor, and a details payload. System-driven changes show with no user. A stack apply writes one entry per changed resource plus a batch entry with the file checksum.