microCMS
Documentation
  • Pricing
  • Blog
  • FAQ
  • Contact
  • Sign In
  • Get started for free
Navigation
Tutorial
Next.js
  • Integration with Next.js
  • Getting Started with App Router
  • Tutorial (App Router)
  • Getting Started with Pages Router
  • Tutorial (Pages Router)
Astro
  • Getting Started
  • Integration with Astro
  • Tutorial
Nuxt
  • Integration with Nuxt
  • Getting Started
  • Tutorial
Gatsby
  • Integration with Gatsby
  • Getting Started
  • Tutorial
JavaScript
  • Integration with JavaScript
  • Getting Started (Browser)
  • Getting Started (Server)
PHP
  • Integration with PHP
  • Getting Started
Ruby
  • Integration with Ruby
  • Getting Started
Go
  • Integration with Go
  • Getting Started with microCMS
Manual
  • Introduction
Account & Login
  • Account Registration
  • Login
  • Email Address Authentication
Services
  • Creating a Service
  • Service Configuration
  • Template
  • Service Deletion
Payment
  • Change of Pricing Plan
  • Registering and Changing Payment Methods
API
  • Creating and Managing APIs
  • API Settings
  • Export/Import of API Schema
Fields
  • Text Field
  • Text Area
  • Image
  • Multiple Images
  • Date
  • Boolean
  • Selectable Field
  • Content Reference
  • Multiple Content References
  • Number
  • File
  • Extended Field
  • Repetition
  • Custom
Contents
  • CSV Export of Content
  • Content Creation
  • Content Editing
  • Content Management
  • View
  • Content Status
  • Custom Status
  • Setting the Content ID
  • Automatically Assigned Values for Content
  • CSV Import of Content
  • API Preview
  • Examples of Using Query Parameters with API Preview
  • Integration Methods by Rendering Type
  • Screen Preview
  • Setting Up Webhooks for Content
Rich Editor
  • How to Use the Rich Editor
  • Rich Editor WRITE API
  • How to Use the Old Rich Editor
Reviews
  • Review
  • AI Review
Media
  • Media Management
  • Changing Media Filters and Display Order
  • Media Tag Configuration
  • Setting Up Media Webhooks
  • Custom Domain Settings for Media
Permission Management
  • Member Management
  • Roles (Permission Management in the Admin Panel)
Environments
  • Multiple Environments (Development Environment)
  • Merging API Settings Between Environments
Connection
  • Amazon S3 Integration
Logs
  • Audit Log
  • Data Transfer Volume
Security
  • Content Update History
  • IP Restrictions for Management Dashboard
  • IP Restrictions for APIs
Authentication
  • Setting Up Two-Factor Authentication
  • Mandatory Two-Factor Authentication
  • Single Sign-On
Specifications & Limitations
  • Recommended Environment
  • Limitations / Precautions
Content API
  • What is the Content API?
Basic Operations
  • GET /api/v1/{endpoint}
  • GET /api/v1/{endpoint}/{content_id}
  • POST /api/v1/{endpoint}
  • PUT /api/v1/{endpoint}/{content_id}
  • PATCH /api/v1/{endpoint}/{content_id}
  • DELETE /api/v1/{endpoint}/{content_id}
API Keys
  • API Key (API Authentication and Authorization Management)
  • Migration from the Old API (X-API-KEY, etc.)
Responses & Error Handling
  • Response format for each field in the GET API
  • Specifying Query Parameters in the GET API
  • Error Responses of the Content API
Management API (Beta)
  • POST /api/v1/roles
  • DELETE /api/v1/roles/{role_id}
  • GET /api/v1/roles/{role_id}
  • PATCH /api/v1/roles/{role_id}
  • GET /api/v1/roles
  • What is the Management API?
Content Operations
  • PUT /api/v1/contents/{endpoint}/{content_id}/reservation
  • GET /api/v1/contents/{endpoint}
  • GET /api/v1/contents/{endpoint}/{content_id}
  • PATCH /api/v1/contents/{endpoint}/{content_id}/status
  • PATCH /api/v1/contents/{endpoint}/{content_id}/createdBy
Media Operations
  • GET /api/v2/media
  • GET /api/v1/media
  • POST /api/v1/media
  • DELETE /api/v2/media
Member Operations
  • PATCH /api/v1/members/{member_id}
  • GET /api/v1/members
  • GET /api/v1/members/{member_id}
API Operations
  • POST /api/v1/apis
  • GET /api/v1/apis
  • GET /api/v1/apis/{endpoint}
Service Operations
  • GET /api/v1/service
Responses & Error Handling
  • Management API Error Responses
Image API
  • What is the Image API?
Parameters
  • Image Size
  • Quality
  • Resolution and Screen Size
  • Format
  • Text
  • Border
  • Padding
  • Shape
  • Download
  • Watermark
MCP Server
  • microCMS MCP
  • microCMS Document MCP Server
  • Top
  • Manual

Multiple Environments (Development Environment)

Last updated: 2026/10/19

The multiple environments feature allows you to duplicate the service configuration and create a completely isolated separate environment.

By utilizing this feature, you can safely make configuration changes to the service in production without any impact on the production environment, ensuring secure operations.

Information

This feature is available in the Business and Enterprise plans for multiple environments.
For details on the features available in each plan, please visit the pricing page.



How to Use the Multiple Environments Feature

First, to create an environment, open the Environment menu in the Administration console.



Click the [Create New] button to display the environment creation dialog.



When creating an environment, specify the environment name (any string) and the range of content and media to copy.
The copy range includes the following options:

  • Content
    • Copy all
    • Copy only published content
    • Do not copy
  • Media
    • Copy all
    • Do not copy


In the created environment, all users will have "Administrator privileges." (For constraints in the created environment, please refer to the specifications mentioned later.)
Therefore, if there is information that should not be viewed, such as draft content, included in the production environment, please narrow down the copy range when creating the environment.

After entering the above, you can create the environment by clicking the [Create] button.
Created environments can be checked in the settings screen. You can also change the environment name and delete the environment from this screen.

Source and Destination for Copying

When creating a new environment, the only source that can be used is the production environment. You cannot create a new environment using another existing environment as the source.

Additionally, for staging purposes, there is also a method using draft saving and draftKey. For details on the construction methods, please refer to the related articles.

microCMSでステージング環境を構築する手法3選 | microCMSブログ
https://blog.microcms.io/building-staging-environment
Information

Merging API Settings Between Environments allows you to reflect API settings from the production environment to another environment, from another environment to the production environment, and between different environments. Content and media will not be copied from the source of the merge.
For details on the merge targets, how to operate, and precautions, please refer to Merging API Settings Between Environments.

Caution
  • It is not intended to use the created environment for production purposes. Even if the current specifications are acceptable, there may be impacts in future updates. For use cases in a production environment, please use the production environment.

Specifications

The detailed specifications of the environment are as follows.

Information

In the Enterprise plan, some restrictions may differ.

Basic Features

  • A random string will be assigned to a separate subdomain for the created environment (e.g., Production environment example, Created environment example-0htwv5q6lmdmk0ze4l8o).
  • Duplicate environment names cannot be set.
  • The data transfer amount is the total transfer amount of all environments combined.
  • The number of API usages is unlimited. It is not counted towards the API limit calculation.
  • The number of contents is unlimited. It is not counted towards the content limit calculation.

Copied Content

What Will Be Copied

  • All API settings (excluding IP address restrictions)
  • API Groups
  • Custom status settings (excluding custom statuses set on contents)

Items Not Copied

  • API Key (A new API Key will be automatically issued)
  • Media Tag
  • Review
  • Webhook Settings
  • Content Update History
  • View

Items Available for Copying

  • Content (You can specify the copy range as "Copy All," "Copy Only Published Content," or "Do Not Copy")
  • Media (You can specify the copy range as "Copy All" or "Do Not Copy") (Note 1) (Note 2)
Caution

(Note 1) To prevent data inconsistency, copying media is mandatory when copying content.

Information

(Note 2) Even if the media copy range is set to [Do not copy], the settings for the "Amazon S3 Integration" feature will be copied as default settings. For more information on handling the Amazon S3 Integration feature across multiple environments, please refer to the documentation for "Amazon S3 Integration".

Constraints (Functionality)

  • You cannot add or remove members. They are always synchronized with the members of the production environment.
  • Access to the created environment is controlled by the role "Environment Read Permission". However, within the accessible environments, role functionalities are not available, and all members will have permissions almost equivalent to administrators.
  • The audit log feature is not available. Additionally, operations within the environment will not be reflected in the audit log of the production environment.
  • The feature to display editing members is not available.

Constraints (Size and Count)

  • The CSV import of content has a limit of 100 items.
  • The size of a single media file is limited to 40MB.
  • You can have a maximum of 3 API Keys.
  • You can create up to 10 environments (excluding the production environment).


Edit Environment Display Settings

To edit the environment display settings, click the three-dot icon on the right side of the environment settings and select [Edit Environment].
Only members with administrator privileges can make edits.

Change Environment Name

You can edit the environment name in the editing screen.


Change Label Color

You can edit the label color in the editing screen.



The color selected here will be reflected at the top of the screen for the configured environment.
For example, if you change the label color to "Green," it will look like the image below.

Delete Environment

Similar to editing the environment display settings, you can delete it by clicking the three-dot icon and selecting [Delete Environment].
When you press [Delete Environment], a dialog like the one below will appear. Please enter the environment name in the form, review the warning items, and proceed with the deletion.

Caution

When you delete an environment, all data related to that environment (including Content, Media, and all API data) will be permanently removed. If you delete it by mistake, it cannot be restored from a backup.

Before deletion, please ensure that there is no necessary data remaining in the target environment.

Conditions for Deletion

To delete an environment, you must be a member with administrator privileges or deletion permissions for that environment.

Contents

  • How to Use the Multiple Environments Feature
  • Source and Destination for Copying
  • Specifications
  • Basic Features
  • Copied Content
  • Constraints (Functionality)
  • Constraints (Size and Count)
  • Edit Environment Display Settings
  • Change Environment Name
  • Change Label Color
  • Delete Environment
  • Conditions for Deletion
  • Company
  • Legal Notice
  • Terms of Service
  • Privacy Policy

Copyright © microcms.io All rights reserved.