• Blog
  • Documentation
  • FAQ
  • Contact
Sign InBook a Demo

Your oncall copilot.

© Copyright 2025 StackPilot. All Rights Reserved.

About
  • Blog
  • Contact
Product
  • Documentation
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Getting started with StackPilot
    • Initial Setup & Integrations
  • Connecting Data Sources
  • User Management & Teams
    • AI Assistant & Incident Response
  • Understanding Tickets
  • Tool Integrations
  • AI Investigation Process

User Management & Teams

Learn how StackPilot manages user authentication, team workspaces, and role-based access control.

StackPilot uses a secure, team-based authentication system designed for engineering teams working on incident response.

Authentication Methods

StackPilot supports multiple authentication methods to fit your team's workflow:

  • Email/Password - Traditional sign-in method for individual accounts
  • Google OAuth - Single sign-on with your Google workspace
  • GitHub OAuth - Sign in with your existing GitHub account (recommended for developers)
  • SAML/SSO - Enterprise single sign-on (Pro plan and above)

Team Workspaces

Creating a Team Workspace

When you sign up for StackPilot, you can:

  1. Join an existing team - if invited by a team member
  2. Create a new team workspace - for your engineering team or organization

Each team workspace includes:

  • Shared incident history and playbooks
  • Team-wide learning and pattern recognition
  • Centralized integrations and connections
  • Collaborative incident response

Team Roles & Permissions

StackPilot uses a role-based permission system:

Owner

  • Full administrative access
  • Manage team members and roles
  • Configure billing and subscriptions
  • Access to all integrations and settings

Admin

  • Manage team members (except owners)
  • Configure integrations and connections
  • Modify project settings
  • Access incident history and analytics

Member

  • Participate in incident response
  • View and create tickets
  • Access team playbooks and timelines
  • Use AI-powered analysis tools

Viewer

  • Read-only access to incidents and reports
  • View team analytics and metrics
  • Cannot modify settings or configurations

Security Features

Multi-Factor Authentication (MFA)

  • TOTP support - Use apps like Google Authenticator or 1Password
  • Required for sensitive operations - Account changes, billing modifications
  • Team-wide MFA policies - Admins can require MFA for all members

Session Management

  • Secure session handling with automatic timeout
  • Device management - View and revoke active sessions
  • IP allowlisting - Restrict access to specific IP ranges (Enterprise)

Audit Logging

  • Complete audit trail of user actions and system changes
  • Integration activity - Track when tools connect and disconnect
  • Incident response logging - Record who did what during incidents

Account Settings

Profile Management

  • Update personal information and preferences
  • Configure notification settings
  • Manage connected OAuth accounts
  • Set timezone and display preferences

Team Management

  • Invite new team members via email
  • Assign roles and permissions
  • Remove or suspend team members
  • Transfer team ownership

This authentication system ensures that your incident response remains secure while enabling seamless collaboration across your engineering team.

  1. Authentication Methods
    1. Team Workspaces
    2. Security Features
    3. Account Settings