Integrations Overview
Big Picture integrates with existing systems to fit into your infrastructure and workflows. Integrations enable CI/CD pipelines to publish releases, artifact repositories to store installers, directory services to authenticate users, and endpoint management tools to deploy software.
Integration Categories
Section titled “Integration Categories”CI/CD Integration
Section titled “CI/CD Integration”CI/CD systems publish releases into Big Picture automatically. Integrations support artifact registration, release creation, and multi-platform builds. Big Picture provides APIs and examples for common CI/CD platforms.
See CI/CD Integration for overview and platform-specific guides.
Artifact Repositories
Section titled “Artifact Repositories”Big Picture references artifacts stored in external repositories or manages storage directly. Supported repositories include S3-compatible storage, Google Cloud Storage, JFrog Artifactory, and self-hosted MinIO. Artifacts can be served from managed storage or external URLs.
See Artifact Repositories for configuration details.
Directory Services
Section titled “Directory Services”Directory services provide authentication and user management for Big Picture. Integrations support OIDC/OAuth2 providers, Active Directory, and LDAP. Directory services enable single sign-on and centralized user management.
See Directory Services Integration for setup and configuration.
Endpoint Management Tools
Section titled “Endpoint Management Tools”Endpoint management tools deploy software when Big Picture policy is set to MANAGED_BY_IT mode. Integrations provide artifacts and metadata for tools like Microsoft Intune and SCCM. This enables IT teams to manage deployments through familiar tools while maintaining vendor-controlled release governance.
See Endpoint Management Tools for integration details.
Webhooks and Events
Section titled “Webhooks and Events”Webhooks notify external systems when events occur in Big Picture. Events include release creation, approval decisions, policy changes, and license events. Webhooks enable automation and integration with monitoring, notification, and workflow systems.
See Webhooks and Events for configuration and event types.
Integration Principles
Section titled “Integration Principles”Big Picture integrations follow these principles:
- Complement, don’t replace — Big Picture enhances existing systems rather than replacing them
- API-first — All integrations use standard REST APIs with bearer token authentication
- Flexible storage — Artifacts can be stored in Big Picture or external repositories
- Policy-driven — Integration behavior adapts to tenant policy settings (AUTO_INSTALL, NOTIFY, MANAGED_BY_IT)
- Standards-based — Integrations use standard protocols (OAuth2, OIDC, REST, webhooks)
When to Integrate
Section titled “When to Integrate”Integrate Big Picture when:
- CI/CD pipelines need to publish releases automatically
- Existing artifact repositories should store installers
- Directory services provide user authentication
- Endpoint management tools deploy software in MANAGED_BY_IT mode
- External systems need to react to Big Picture events
- Organizations need to fit Big Picture into existing infrastructure
Integration Setup
Section titled “Integration Setup”Most integrations require:
- Service account or API credentials — Create service accounts with appropriate scopes
- Configuration — Configure endpoints, authentication, and integration-specific settings
- Testing — Verify integration behavior in non-production environments
- Monitoring — Monitor integration health and error rates
See individual integration guides for specific setup instructions.
Related Documentation
Section titled “Related Documentation”- Workflows — Operational procedures that use integrations
- Reference — API documentation for programmatic integrations
- Getting Started — Initial setup and configuration