Copying Spaces

Spaces can be copied between environments, letting you promote tested configurations from staging to production or maintain consistent setups across multiple environments. This guide covers what gets copied, what doesn't, and how to use copying effectively.

When to copy a space

Copying spaces is useful when you want to:

• Promote from staging to production — Test your space configuration in staging, then copy it to production once you're satisfied
• Maintain consistency — Keep the same space setup across development, staging, and production environments
• Share configurations — Quickly set up identical workspaces for different environments without manual recreation

What gets copied

When you copy a space, Keel creates an identical copy in the target environment(s) including:

What doesn't get copied

Members are not copied. Each environment maintains its own member list, so you'll need to invite team members separately in each environment where the space is copied.

This is intentional. The people who need access to a staging environment are often different from those who need production access. You might want developers testing in staging, but only operations staff in production.

Copying to other environments

To copy a space to one or more environments:

1. Navigate to Spaces in the Keel Console
2. Open the space you want to copy
3. Click the ⋮ menu in the top-right corner
4. Select Copy to environment
5. In the dialog, check the boxes next to each target environment
6. Click Copy

The copy happens immediately. You can select multiple environments at once, and each receives its own independent copy of the space.

After copying, you're redirected to one of the newly created spaces where you can verify the configuration and invite members.

Duplicating within the same environment

Sometimes you want a copy of a space in the same environment, perhaps as a starting point for a new team's workspace or to experiment with different configurations.

To duplicate a space:

1. Open the space you want to duplicate
2. Click the ⋮ menu in the top-right corner
3. Select Duplicate

Keel creates an identical copy in the current environment. You can then rename it and modify the configuration as needed.

Use case: Promoting space configuration from staging to production

Here's a typical workflow for managing spaces across environments:

1. Build and test in staging

Start by creating your space in the staging environment:

1. Create the space with an appropriate name (e.g., "Warehouse Operations")
2. Add and organize your tools into logical groups
3. Configure custom labels and descriptions
4. Add helpful links
5. Invite a few team members to test

2. Iterate based on feedback

Work with your test users to refine the configuration:

• Adjust group organization based on actual workflows
• Update tool labels to match team terminology
• Add any missing actions or remove unused ones
• Verify links point to the right resources

3. Copy to production

Once the space configuration is stable:

1. Open the space in staging
2. Click the menu and select Copy to environment
3. Check Production (and any other environments that need it)
4. Click Copy

4. Invite production members

In the production environment:

1. Open the copied space
2. Click Members
3. Invite your production team members

5. Maintain going forward

If you need to make changes later:

• Minor updates: Make them directly in production
• Major reorganization: Consider making changes in staging first, then copying a fresh version to production

Copying multiple spaces

You can only copy one space at a time through the console interface. If you need to copy several spaces to a new environment, repeat the copy process for each one.

After copying

Once a space is copied, the original and the copy are completely independent. Changes to one don't affect the other. This means:

• Editing tools in the original won't update the copy
• Adding members in one environment doesn't grant access in others
• Deleting the original doesn't remove copies

If you need to synchronize changes across environments, you'll need to make the changes manually in each environment or copy a fresh version.