DocumentationOpen PingAgain
Browse

Public Beta

Customer security overview

Learn how PingAgain protects accounts, credentials, and outbound requests.

PingAgain separates account data, checks roles before changes, and protects sensitive configuration throughout customer workflows.

Account boundaries

Monitors, incidents, integrations, Status Pages, and team membership belong to one account. If your login belongs to several accounts, switching changes the active workspace; it does not merge data or carry a role from one account to another.

Invitations and sign-in linking include identity checks to prevent the wrong account from being joined or connected automatically.

Credentials and destinations

Secret headers, API keys, signing secrets, Heartbeat URLs, and provider webhook URLs should be stored as credentials. PingAgain masks sensitive values after entry and prevents outbound monitoring or webhooks from targeting unsafe private destinations.

Use the least access needed, keep secrets out of URLs and screenshots, and revoke or replace anything exposed. PingAgain support will never need your full token, Magic Link, OAuth code, or webhook URL.

Next: see API authentication, webhook security, or Feedback and support.