Skip to content

Security Overview

Mainbranch is built with enterprise security in mind, providing robust protection for your organization’s data while maintaining ease of use.

Mainbranch supports enterprise SSO through:

  • Google Workspace — OIDC-based authentication
  • Microsoft Entra ID — OIDC-based authentication (formerly Azure AD)

SSO provides:

  • Centralized user authentication
  • No separate passwords to manage
  • Automatic deprovisioning when users leave
  • Support for your existing MFA policies
MethodDescription
Google SSOSign in with Google Workspace account
Microsoft SSOSign in with Microsoft 365 account
Email/PasswordTraditional authentication (if enabled)

Mainbranch uses role-based access control:

RoleCapabilities
OwnerFull access, workspace management
AdminSettings, users, connectors
MemberStandard feature access

Data access inherits from source systems:

  • Google Drive sharing settings are respected
  • Microsoft 365 permissions are maintained
  • Users only see content they have access to
  • In Transit — All data encrypted with TLS 1.2+
  • At Rest — Data encrypted using AES-256
  • API Communications — Secure HTTPS connections
  • Workspaces are isolated from each other
  • Multi-tenant architecture with strict separation
  • No data sharing between organizations
  • Data is processed for indexing only
  • Content is not used for AI model training
  • Data can be deleted upon request

Mainbranch follows security best practices:

  • Regular security assessments
  • Secure development lifecycle
  • Incident response procedures
  • Employee security training
  • Cloud-hosted on secure infrastructure
  • Regular security updates and patching
  • Network security controls
  • Access logging and monitoring

Administrators can configure:

  • SSO enforcement
  • Member management
  • Feature access (web search, file uploads)
  • Data retention policies
  • User activity logs
  • Connector status monitoring
  • Security event tracking
  • Invite-only access
  • Role assignment
  • Access revocation

Best practices for users:

  • Use SSO when available
  • Enable MFA on your identity provider
  • Report suspicious activity
  • Sign out on shared devices
  • You can only access data you have permission to view
  • Search results are filtered based on your access
  • Sensitive actions are logged

No. Your organization’s data is used solely for providing Mainbranch functionality. It is not used to train AI models.

Your searches are private to you. Administrators may have access to usage statistics but not individual query details.

When an employee is removed from your identity provider, they lose access to Mainbranch. SSO ensures access is revoked centrally.

Data can be deleted by:

  • Removing it from the source (syncs to Mainbranch)
  • Disconnecting a data source
  • Requesting data deletion from support

For security questions or concerns:

  • Contact your Mainbranch administrator
  • Review documentation for specific features
  • Report security issues to support