Managing packages and package permissions
Managing package permissions is important because it provides precise control over how others interact with your work in Studio. Rather than applying a uniform access model, you can tailor security to fit the specific requirements of your team.
Managing these permissions allows you to:
Keep your data secure: You decide exactly who can see or use your work. This keeps your sensitive data models and complex logic safe from unauthorized access.
Prevent accidental deletions: You can let teammates edit and improve assets without giving them the power to delete the entire package. This adds a safety net to your collaborative work.
Stay organized with admin controls: You can reserve big changes—like moving items to the trash or changing access levels—for project leads. This keeps your workspace stable and well-managed.
Control the final experience: You use specific settings to choose who can actually interact with your finished app, ensuring it reaches the right audience at the right time.
To manage your existing packages:
Click Studio.
Open the Studio space containing the package.
Locate the package and click Options.
Depending on the permissions you hold, you then have the following package management options:
Star / unstar package: Star or unstar this package to and from the top of your Studio space.
In this example, Example Package 1 has been starred within the Studio space.
Open in Apps: This allows you to open the published version of the app you've created. For more information about viewing your apps, see: Using Apps.
Edit name: This allows you to rename the package (but keep all existing settings and permissions).
Copy to: This wizard allows you to copy the package (and all assets, settings, and permissions) to other teams or spaces that you hold permissions for. The original package remains in the same location after it is copied.
Note
When overwriting an existing package, any existing audit logs and execution histories for Action Flows are deleted and can't be recovered.
Move to space: This allows you to move the package (and all assets, settings, and permissions.) to other spaces. The original package no longer remains in the same location after it is moved.
Duplicate: This creates a copy of the package (and all assets, settings, and permissions etc.) within the existing space. When duplicating a package, you are prompted to enter a new package name and key.
Move to Trash: This moves the package to your Trash area, allowing you to recover the package back to its original location or delete it permanently. Items are held in the trash for 180 days from the point of deletion and then automatically deleted permanently with no recovery possible.
To access your Trash, you need admin permissions to your Studio space.
Permissions: This allows you to control who or what can view and use this package and its content. For more information, see: Available package permissions.
Settings: This allows you to manage the package key, package variables, dependencies, app perspectives, and translations / languages. For more information, see: Managing package settings.
You can assign the following permissions to a Studio package:
Use package: This allows the user to view and use the package within an app.
Edit package: This allows the user to edit the package and any assets contained within that packet. Users are not able to delete the package itself, however.
Delete package: This allows the user to delete the package only. This permission should be combined with the Use and Edit permissions.
Manage permissions: This allows the user to manage the package permissions only. This permission should be combined with the Use and Edit permissions.