--- title: "Workspaces" slug: "workspaces" updated: 2025-10-21T16:47:10Z published: 2025-10-21T16:47:10Z --- > ## 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. # Workspaces *Learn how to organize Tulip assets for multiple production environments within a single instance.* Who can use this feature Users on Enterprise plans. Workspaces are a new feature set in Tulip, allowing organizations to manage users and resources for multiple sites within a single global Tulip instance. A Workspace is a partition within a Tulip account with its own set of resources like apps, Machines, and Tables, that are independent of other workspaces within an account. Workspaces can be useful for separating data for different teams or facilities. Resources like Connectors can be standardized and deployed globally to different sites, while apps and data can be managed locally at each facility. ### Workspace Use-Cases - Organizing operations by site - Boston, Munich, Hungary - Organizing team data by department level ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/What%20are%20Workspaces_436368619.png) Prior to Workspaces, these use-cases required a number of instances to be provisioned in order to segregate data but this is now made simpler with only needing to manage one instance that houses multiple workspaces. ### Workspaces Page To find the Workspaces page, click your user icon in the top right corner. Select **Account Settings** then click the **Workspaces** tab on the left navigation bar. ![Workspaces Page.gif](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Workspaces%20Page.gif) ## Configuration With the addition of Workspaces, you have access to assign a new user role: Workspace Owner. This user role has all Account Owner permissions, but restricted to their assigned Workspace. All other user roles/permissions remain unchanged. Learn more about user roles [here](https://support.tulip.co/docs/adding-users-and-managing-user-roles). An Account Owner can specify which Workspace a user has access to by navigating to the Account Settings and then to the Users page. SAML and LDAP functionality remains unchanged. For SAML, Account Owners will have the ability to specify a Workspace mapping from their IdP. This will be used to set the initial Workspace for a user. A default Workspace can also be defined for all new users. ### **Resources** Here is the breakdown of resource sharing at the Account and Workspace level: | **Account Scoped** | **Workspace Scoped** | | --- | --- | | Connectors | Stations | | Connector Functions | Apps | | Machine Types | Analytics | | Machine Data Sources | Tables | | Edge Devices | Machines | | IP Cameras | Cameras | | Camera Detectors | User Table* | *With Workspaces enabled, the User Table is scoped to users defined within the Workspace. Global roles (Account Owners) are not included in the User Table for an individual Workspace, which may impact the ability to run app logic that involves reading or writing to the User Table. ### Settings With Workspaces enabled, here is a breakdown of the Account and Workspace scoped settings that can be adjusted by Account Owners at the account level and Workspace Owners at the Workspace level: | **Account Settings** | **Workspace Settings** | | --- | --- | | Account | Workspace | | Users | Users | | Player | Date and Time - Time Zone | | Date and Time - Format only | Schedules and Shifts | | Color Palette | Device Uptime | | Developer Mode | Approvals | | Network Access | API Tokens | ### Add users to multiple workspaces In the App editor, you can navigate across Workspaces using the dropdown menu in the top left of the page from Workspace scoped pages. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Workspace%20Configurations%20and%20Settings_436464106.png) **Global Roles** Account Owners have the ability to navigate across workspaces within an Instance. **Workspace-Scoped Roles** Users can be a part of multiple workspaces, with a separate role in each workspace. Once you add a user to multiple workpsaces, they will be able to choose from the list of workspaces where they have a role, as shown above. ### Add/archive/rename a workspace Account Owners can create new workspaces, as well as rename, archive, and un-archive workspaces. To access these abilities, go the the **Workspaces** page under **Account Settings**. NOTE You cannot archive workspaces that use the [Enterprise App Exchange](/r230/docs/an-overview-of-the-enterprise-app-exchange). You must first disable this feature from your workspace. ### Move apps across workspaces The App Import/Export functionality remains unchanged across Workspaces within the same instance. ## Further Reading - [Workspace management](https://support.tulip.co/docs/workspace-management) --- **Machine** A **Machine**is a digital representation of a physical datasource. Machines have **Attributes**that are updated through an OPC-UA Connector or the Tulip API. **Tulip Tables** **Tulip Tables**are a global location to store your production data. Tables are made up of Records (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview.gif) **Connectors** **Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions. - **HTTP Connectors** utilize HTTP API endpoints. - **SQL Connectors** can enable connectivity with certain SQL databases. - **MQTT Connectors** can connect to MQTT brokers for machine monitoring. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif) **Station** **Stations**are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,**Tulip Vision Camera Configurations, Machines,****and more. **Connector Function** **Connector Functions** are individual operations to interact with an HTTP or SQL Datasources. Connector Functions can have inputs and outputs, and can be called from: Triggers, Functions, Automations, and AI Agents. Once pulled, data can be used throughout your applications. **Machine Type** **Machine Types** are global definitions of what data to expect from machines of different types. Each Machine Type will have different states, **triggers**, and **attributes**.*EX. We have 5 makes/models of CNC mill, but they all have the same set of attributes (Spindle speed, feed rate, etc.) These can all be combined into a single "CNC Mill" Machine Type* **Analytics** **Analytics** are live updating graphs and metrics calculated based on app data, Table data, and machine data. Analytics can be embedded and dynamically filtered within an application. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-1662410510869.png) **Edge Devices** **Edge Devices** are any hardware intended to connect physical things to the cloud. This can include entirely mechanical devices, older machines without network functionality, PLCs, and more. Tulip sells the **Edge IO** and **Edge MC** that interface directly into **Triggers** in a breeze, but Tulip can also support other Edge Devices. **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. **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 Instance** A Tulip customer account. Your instance can be found at https://[your-instance].tulip.co When *your instance*is referenced, we are just talking about your Tulip account on an organization-level, not user-level.