Profile
Your name, role, login email, and profile photo identify you across SitePulse, including in team areas and member lists. Changing your email may require re-verification before you can access verified-only areas again. Profile photos must be image files up to 1 MB.Current team
Your current team controls which sites, issues, monitoring settings, notifications, and billing data you see. Switch teams from Teams or the team selector. SitePulse stores the current team for the session and uses it for dashboard and API policy checks.Password and passkeys
You must know your current password to set a new one. If your account was created with social sign-in and has no password, you can set one from Settings -> Password. After a successful password change you remain logged in. If you’ve forgotten your password, request a reset link by email from the login page. You can also register passkeys for passwordless sign-in. Passkeys use your device’s biometrics or a security key (WebAuthn) and work alongside your password.Two-factor authentication (2FA)
2FA is enabled per account using an authenticator app. During setup SitePulse shows a QR code and recovery codes — store the recovery codes securely, as they let you sign in if you lose access to your authenticator. 2FA requirements are controlled at the team level. When any team you belong to enforces 2FA, you must enable it before accessing that team’s areas. See Team security.API tokens
Personal access tokens authenticate requests to the SitePulse API.- Give each token a descriptive name
- Select one or more scopes before creating it
- Tokens authenticate as your user — team membership, role permissions, and subscription status still apply to API requests
- Each token carries only the OAuth scopes you grant it; grant the minimum the integration needs
- The token value is shown once at creation and cannot be retrieved again
- Tokens expire six months after creation
- The token list shows active token names, scopes, creation dates, and expiration dates
- Revoke tokens you no longer use
teams:read, teams:write, sites:read / sites:write / sites:delete, checks:read / checks:run / checks:delete, and issues:read. See Authentication for the full scope reference.
MCP integrations
Use Settings -> MCP to connect AI clients such as Cursor, VS Code, Claude, Codex, and other MCP-compatible tools. OAuth is preferred when your client supports it. If OAuth is unavailable, create an MCP token and store it asSITEPULSE_MCP_TOKEN. See MCP integrations for setup steps and available tools.