Managing Your Team

Pingara is built for teams. Organizations let you group monitors, incidents, and settings under a shared workspace with role-based access control.

Organizations

Every Pingara account belongs to at least one organization. Organizations are the top-level container for all your monitoring resources.

What Belongs to an Organization

Monitors - All URL and ping monitors
Incidents - Incident history and active incidents
Alert Policies - Notification rules and channels
Status Pages - Public-facing status pages
Team Members - Users with assigned roles

Creating an Organization

When you first sign up, Pingara creates a default organization for you. You can rename it or create additional organizations:

Go to Settings → Organization
Click Create Organization
Enter a name (e.g., "Acme Corp")
Choose a slug (e.g., "acme-corp"), which is used in URLs
Click Create

Switching Organizations

If you belong to multiple organizations, switch between them using the organization selector in the sidebar header.

Team Roles

Pingara has four roles: owner, admin, editor, and viewer.

Owner

The organization creator. Full access to everything.

Permission	Access
Manage monitors, alerts, status pages	✅ Create, edit, delete
View incidents	✅ Full access
Acknowledge incidents	✅
Manage team	✅ Invite, remove, change roles
View the audit log	✅
Billing	✅ View and manage subscription
Delete organization	✅

Note: There must always be at least one Owner. You cannot remove the last Owner from an organization.

Admin and Editor

Owner, admin, and editor share the same write access to monitors, alert policies, and status pages. Admin and editor differ from owner only in that neither can manage billing or delete the organization, and only admin can manage team membership.

Permission	Admin	Editor
Manage monitors, alerts, status pages	✅ Create, edit, delete	✅ Create, edit, delete
View incidents	✅ Full access	✅ Full access
Acknowledge incidents	✅	✅
Manage team (invite, remove, change roles)	✅	❌
View the audit log	✅	❌
Billing	❌	❌
Delete organization	❌	❌

Viewer

Read-only for configuration. Incident response is deliberately open to every member, viewer included, because the person who spots an outage first is often whoever happened to be looking at the dashboard, and making them find someone with a bigger role costs minutes in the one window where minutes matter.

Permission	Access
Manage monitors, alerts, status pages	❌ View only
View incidents	✅ Full access
Respond to incidents	✅ Acknowledge, move the status (Investigating → Identified → Monitoring), edit incident notes, and generate AI root cause hints. None of these change any monitor, alert or status-page configuration
Send a test alert	✅ Rate-limited per monitor and per person; flagged as a test, self-resolving, and never shown to status-page subscribers
Manage team	❌
View the audit log	❌
Billing	❌
Delete organization	❌

Inviting Team Members

How to Invite

Go to Settings → Team
Click Invite Member
Enter their email address
Select admin, editor, or viewer as the role (you can't invite someone directly as owner)
Click Send Invitation

Invitation Process

Invited user receives an email with a join link
They click the link and create an account (or sign in if they already have one)
They're automatically added to your organization with the assigned role
They appear in the team members list

The invitation page tells the person that the organization's owners and admins can see their sign-in times, IP addresses and countries in its audit log. A signed-out visitor sees this before accepting, and a signed-in one sees it once the invitation is accepted. It is worth telling new members yourself when you invite them.

Pending Invitations

View and manage pending invitations in Settings → Team → Pending:

Resend - Send the invitation email again
Revoke - Cancel the invitation

Managing Existing Members

Changing Roles

Owners and admins can change a member's role:

Go to Settings → Team
Find the team member
Click the role dropdown
Select the new role
Change takes effect immediately

Removing Members

Go to Settings → Team
Find the team member
Click Remove
Confirm the removal

What happens when a member is removed:

They lose access to all organization resources immediately
Their monitors and configurations remain (owned by the org, not the user)
They can be re-invited later

Organization Settings

General Settings

Setting	Description
Name	Organization display name
Slug	URL identifier (cannot be changed after creation)
Timezone	Default timezone for reports and incident timestamps

Account Security

Pingara has no organization-wide security policy settings today. There's no enforced-2FA toggle, session timeout, or IP allowlist. Security controls are per-user, under Settings → Security:

Feature	Description
Two-factor authentication	TOTP-based, with backup codes. If you lose both your phone and your backup codes, see If Two-factor Authentication Locks You Out
Session management	List every signed-in device/session, revoke one, or revoke all others
Sign out everywhere	End every session, including the current one. It also cancels an email change that is waiting for confirmation
Email verification	Required for sensitive actions like uploading a profile picture
Changing your sign-in email	Needs your current password and a confirmation from the new address. See Changing your email address
Undo links	Shown only after a sign-in email change went through. Lets you cancel the link that restores your old address. See Cancelling an Undo Link

Multi-Organization Access

Team members can belong to multiple organizations, useful for:

Agencies managing multiple clients
MSPs monitoring different customer environments
Consultants with access to several teams

Each organization is fully isolated:

Monitors in Org A are invisible to Org B
Alert policies don't cross organization boundaries
Billing is per-organization

Best Practices

Use Roles Appropriately

Owner - Company founder, CTO, or team lead
Admin - Senior engineers, DevOps leads who also need to manage the team
Editor - Engineers who configure monitors and alerts but don't need to manage team membership
Viewer - Stakeholders, support staff, and anyone who needs visibility and the ability to acknowledge incidents, but not to change configuration

Audit Team Access Regularly

Owners and admins can see who signed in and from where, and who changed roles, keys and settings, in the audit log under Settings → Audit Logs.

Review your team members quarterly:

Remove people who've left the company
Downgrade roles for people who no longer need admin access
Ensure the Owner role is assigned to an active team member

Use Shared Alert Channels

Instead of individual email alerts, set up shared channels:

Team Slack channel for real-time alerts
Shared email list (ops@company.com) for audit trail
PagerDuty for on-call rotation

Separate Production and Staging

Set the Environment field to Production, Staging, QA, or Development on each monitor, then use the Environment filter on the monitor list to keep production and staging monitoring cleanly separated. For stricter isolation, with separate billing, members, or alert policies per environment, consider separate organizations instead.

Next Steps

Billing and Plans - Understand Free vs Pro features
Setting Up Alerts - Configure team-wide alert policies
Creating Status Pages - Build public status pages for your org