Studio Spaces
What is a Studio Space?
Studio Spaces allow you to organize your Studio Packages in a meaningful way, with access control. You can think of it as having different folders or repositories to put and access your work in.
All Packages belong to a Space, for Teams which has Packages before the launch of Studio Spaces, we have put all Packages in a Studio Space called 'Default'. The 'Default' Space acts like any regular Space and can be changed accordingly.
There is a 1-to-Many relationship between Spaces and Packages. One Space can contain many Packages, one Package can belong to only one Space.
Packages can be moved across Spaces with the 'Move to Space' option on the three-dot menu of a package.
Studio Spaces are created and maintained in Studio and are visible for end-users in Apps.
 |
How do I create and use a Studio Space?
You can create as many spaces as you need:
Team Spaces - give each team or department their own Space so they can focus and make their Packages easier to find. Eg. QA, Development, Accounting, Go To Market, Support, Procurements...
Project Spaces - put all Packages related to an initiative or project together,
Personal Spaces - store individual work inside a personal Space.
A new Space can be created in Studio using the Space dropdown.
A new Space has an icon and a name.
Space Permissions
In addition to the existing permissions at Package and Asset level, permissions can also be given on an individual Space level:
Use all Packages: lets end users use all Packages within the Space (Endusers use Packages in Apps).
Create Package: lets collaborators create a Package within the Space (this is required for installing Apps from the Marketplace).
Edit Space: permission to rename the Space.
Edit all Packages: permission to edit all packages within the Space.
Delete Space.
Delete all Packages.
Manage Permissions.
 |
FAQ
TryCelonis - What happens when creating a TryCelonis team from two different demos?
In our created team, each demo will be in its individual Studio Space.
How were Team Permissions handled before Studio Spaces?
Before Studio Spaces, the Studio permissions on the team level were given to Packages directly.
 |
How can I structure my content inside Celonis Spaces?
Studio Spaces allow you to organize Studio Packages, this feature has you two main use cases - i) granular permissions control, and ii) improved content browsing experience.
Firstly, the granular permissions management allows your Central IT to enable analysts to build and publish in their designated Space. This case should be considered if different analysts work on multiple use cases and should not be able to access each other’s work. In Studio Studio, you have the following permission opportunities: Use all packages, create packages, edit space, edit all packages, delete space, delete all packages, manage permissions.
Secondly, the structuring of Celonis Studio into different use-cases is useful to enhance the content browsing experience if you have a high volume of Packages.
Below you will find two examples of how to leverage the Celonis Studio:
1. Division by Department, Subsidiary
Permission Setup:
End users:
‘Use’ on Space.
Technical Analyst/ App Builders
‘Edit’ within their own Package.
‘Create Package’ within Space.
 |
2. Division by Process and Operating Model
Permission Setup:
End users
‘Use’ on Space.
Technical Analyst/ App Builders:
‘Edit’ within their own Package.
‘Create Package’ within Space.
 |
When to Apply:
Several use cases within the same process
When different analysts/creators work on different use cases and should not be able to access each other’s work
The end-users across the different use cases are the same
Analysts should be able to create new packages for their end-users
 |