# Announcing: Workspaces in Tulip

**URL:** <https://community.tulip.co/t/announcing-workspaces-in-tulip/3699>\
**Category:** Announcements\
**Created:** [September 30, 2021, 2:54pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699 "2021-09-30T14:54:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jemmadupuis](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jemmadupuis/32/8228_2.png) [@jemmadupuis](https://community.tulip.co/u/jemmadupuis)\
**Post date:** [September 30, 2021, 2:54pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/1 "2021-09-30T14:54:05Z")

</div>

Introducing Workspaces: a powerful new set of local and global controls to make it easier to scale with Tulip across multiple locations and teams.

 ![](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/7/7f8c0d2eab9296d19b4ae93387f36aa4b5c17362.png)

A Workspace is a partition within a Tulip account with its own set of resources like apps and machines, that are independent of other workspaces within an account. Workspaces can be useful for separating different teams or facilities.

Now, Workspaces comes with global and local settings menus to enable you to centralize branding and user access. Resources like connectors can be standardized and deployed globally to different sites, while apps and data can be managed locally at each facility.

Users can be assigned to multiple workspaces, and their roles can be easily changed as needed by an administrator with the role of Account Owner or Workspace Owner.

 ![Workspaces](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/0/05a6544e5afd414925e59b17f91861e5ced234ca.png)

In each Workspace, settings and resources can be configured and created to meet your facility’s needs. Some of the settings unique to Workspaces include:

- Timezones
- Schedules and Shifts
- Device Uptime
- Bots
- Approval Types

Resources like apps, tables, analytics, camera configurations, and machines are all local to each Workspace, so your team can edit apps and configure resources to your operational needs.

## Share across your organization

Account owners will have full access to local Workspace resources, and global resources across all Workspaces.

In addition, Account owners can adjust settings and resources for all of the Workspaces, to ensure branding and resources are centralized and standardized across your teams. Global settings that affect all Workspaces include:

- Tulip Player
- Date and Time Formatting
- Color Palette
- Developer Mode Toggle
- Network Access

Resources and configurations that may be vital to every Workspace can be controlled at the account level, making it easy to configure and deploy across every site. These resources and configurations include:

- Connectors
- Connector Functions
- Machine Types
- Machine Data Sources
- Edge Devices
- IP Cameras
- Camera Detectors
- Connector Host

Workspaces are available to all enterprise customers. At this time, adding new workspaces will require support from Tulip. If you’re interested in getting started with this feature, [please contact us](https://tulip.co/contact-us/).

---

<div class="post-metadata">

**Author:** ![jjj](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jjj/32/4542_2.png) [@jjj](https://community.tulip.co/u/jjj)\
**Post date:** [April 12, 2023, 5:33pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/2 "2023-04-12T17:33:15Z")

</div>

![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/2/22c73e4668d4bc6af7f1ccf271d3347ea797a1e3.png)  
Is there any way to make Connector not accessible to all workspace? When I hover over the little globe it says “Available in all workspaces.” If I make a training/sandbox workspace I don’t want all of the connectors to be accessible.

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [April 12, 2023, 10:25pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/3 "2023-04-12T22:25:29Z")

</div>

Hey @jjj -

Any new connectors created in any workspace will by default only be scoped to that workspace, and they can be promoted to be global if you desire it. Existing connectors were historically available in all workspaces (they weren’t workspace-scoped) so we retained this behavior for existing connectors.

We are scoping some work to give a whole lot more control for cross-workspace asset management that will include quite a bit more flexibility for managing connectors, but that work is probably something we won’t pick up on the engineering side until late this year.

Pete

---

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [April 13, 2023, 7:59am UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/4 "2023-04-13T07:59:12Z")

</div>

Thanks, we are very interesting for this features: having connector at workspace level and account level.  
In which release is plan to create Connector at workspace level?  
Today in v250.1, under a workspace, a new connector is still created and available for all workspace and not for a dedicated workspace.  
Thanks

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [April 13, 2023, 12:05pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/5 "2023-04-13T12:05:11Z")

</div>

Hey @Nicolas -

Just talked to the team, this is just behind a _Feature Flag_ as it is just being rolled out now. Shoot an email to your tulip commercial team or [support@tulip.co](mailto:support@tulip.co) and they can turn on the `connectorsAreSeparatedByWorkspace` for you.

Pete

---

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [April 13, 2023, 12:52pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/6 "2023-04-13T12:52:47Z")

</div>

Is it part of r249 or r250 this featre flag? (part of LTS10 or not)

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [April 13, 2023, 12:56pm UTC](https://community.tulip.co/t/announcing-workspaces-in-tulip/3699/7 "2023-04-13T12:56:08Z")

</div>

Hey @Nicolas -

This was introduced in r249, so it is available within LTS10 (being released very very soon)

Pete
