Multi-Environment Setup

5 min read

10 min setup

Quick Summary

Want to test new features without affecting your production data? With BedrockDocs' multi-environment support, you can create separate spaces for development, testing, and production. Each environment gets its own settings, team members, and integrations – perfect for a professional deployment pipeline.

Quick Environment Switching

Once set up, use the organization selector in the header to instantly switch between environments. Each environment maintains its own configuration, data, and team access.

Key Features

Development Sandbox

Create a safe environment for testing new features and configurations without affecting production data.

Best for: Perfect for experimenting with new document types and AI models

Team Collaboration

Each environment can have its own team members with specific access levels.

Best for: Ideal for separating development and production teams

Independent Configurations

Maintain separate settings, webhooks, and integrations for each environment.

Best for: Connect test systems to test environments, production to production

Quick Switching

Seamlessly switch between environments with our organization selector.

Best for: Perfect for developers and admins managing multiple environments

Setup Process

Create Development Account

Using email aliases (like +dev) keeps all notifications organized in your inbox

Name Your Environment

Set a clear environment name like "Company Name - Dev" in Settings > Account

Consistent naming helps team members identify environments at a glance

Configure Environment Settings

Set up document types, AI models, and integrations specific to this environment

Start with a subset of document types to test your setup

Set Up Webhooks

Configure environment-specific webhook endpoints for your test systems

Use different endpoints to keep test data separate from production

Invite Team Members

Add team members who need access to this specific environment

Consider different team compositions for different environments

Best Practices

Clear Naming Convention: Use consistent environment names across your organization (e.g., "Company - Dev", "Company - Prod")
Separate Access Control: Limit production access to essential team members only to prevent accidental changes
Test Then Deploy: Always test new features in development before rolling them out to production

Pro Tip

Consider creating a dedicated QA environment between development and production. This gives your team a stable environment for final testing before deploying to production.