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:

1. Go to Settings → Organization
2. Click Create Organization
3. Enter a name (e.g., "Acme Corp")
4. Choose a slug (e.g., "acme-corp") — this is used in URLs
5. Click Create

Switching Organizations

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

Team Roles

Pingara uses three roles to control what each team member can do:

Owner

The organization creator. Full access to everything.

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

Admin

Trusted team members with broad management access.

Member

Standard team members with read and limited write access.

Inviting Team Members

How to Invite

1. Go to Settings → Team
2. Click Invite Member
3. Enter their email address
4. Select a role (Admin or Member)
5. Click Send Invitation

Invitation Process

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

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:

1. Go to Settings → Team
2. Find the team member
3. Click the role dropdown
4. Select the new role
5. Change takes effect immediately

Removing Members

1. Go to Settings → Team
2. Find the team member
3. Click Remove
4. 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

Security Settings

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
• Member — Junior engineers, support staff, stakeholders

Audit Team Access Regularly

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

Consider creating separate organizations (or using monitor tags) to keep production and staging monitoring cleanly separated.

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