---
title: "Connector environments"
slug: "connector-environments"
tags: ["Developer Mode", "Connectors", "Connector Function", "Connector Environment"]
updated: 2025-06-04T18:29:56Z
published: 2025-06-04T18:29:56Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connector environments

*Learn about connector environments and which environments to set up for different stages in your process.*

## What are Environments?

Connector Environments allows you to define seperate target external systems for your connectors to interact with, depending on the lifecycle phase of applications.

Environments allow you to safely develop applications without impacting production databases, and automatically migrate to production databases when applications are published.

## How environments are used

Based on the place where in application is run, and the state of that application, different environments will be used.

Within Developer Mode, the environment can be overwritten, but within Tulip Player, the environment used will be entirely drive by the phase in the app lifecycle.

![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28742%29.png)

**Development** - When the Development Version of an application is used (in player or developer mode), the configuration of the Development environment will be used.

**Pre-Production** - When an application has been submitted for Approvals, but has not been approved, the "Pre-Production" environment configuration will be used.

**Production** - When an application has been published, the production environment will be used.

## Set up multiple environments

          
          

**MQTT connectors do not support multiple environments.**

          Editing Environments Used in Published Apps/Automations

          

Editing environments that are being used by published applications/automations can impact production. Not all users are granted the rights to make these changes.

[Custom User Roles](/r230/docs/customize-user-roles) give account owners the ability to grant edit access for environments that are in use. Users without adequate permissions will see a warning ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28727%29.png)

After you create a new SQL or HTTP connector, you will see the following screen:.

![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28628%29.png)

By default, only the **Production** environment will be configured. The **Development** and **Pre-Production** environments will be configured to match Production.

![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28629%29.png)

## Further Reading

- [How To Write a Connector Function](/r230/docs/how-to-write-a-sql-connector-function)
- [How To Call a Connector Function Using Triggers](/r230/docs/how-to-call-a-connector-function-using-triggers)

**Environment**

An **environment** is a set of parameters that match specific configurations for tests. An environment includes **API endpoints** and authentication profiles for REST, SOAP, and GraphQL services, as well as database connection settings, custom project properties, and parameters of connection to JMS servers.

**Developer Mode**

**Developer Mode**is a dedicated interface to test your applications. Dev mode doesn't write to **Tables**or create **Completions**so production data isn't impacted.

**Tulip Player**

**Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls.

**Development Version**

The **Dev Version**of a Tulip app is the work-in-progress of your application after an app has been published. If a **Station**is assigned to run the Development version of an application, it will see live changes as they are made in the app editor.

Generally, **Stations**running in production will be running the **Published Version**of an Application.

**Approval**

A mechanism for ensuring that applications are reviewed and approved before publication. *Approvals types*can be configured under the settings menu. Specific approvals may be applied to an application on the application homescreen.