Transporting Private Objects

To export a private object, your administrator must enable Allow Private Objects Export in the System Configurations tab of the SAP Analytics Cloud.

Once it is enabled, you are able to choose the private objects from the Users folder and Workspace  Users folder for the new export workflow.

You can have private objects inside workspaces too. An administrator must grant permissions to specific teams and users to manage the private objects inside workspaces.

To export any private object, you must have these permissions:

• Lifecycle rights with Read, Maintain, and Share permissions – enables you to read, maintain, and share objects.
• Private Files rights with Create, Read, Delete, and Manage permissions - enables you to view and manage all user’s private objects. If you don’t have Manage permission, you can only see your User’s private objects.

You can either export packages that has public objects, private objects, or both public and private objects.

When you export a package that contains private objects, it is imported to the public folder in the target system by default. However, you can move it to the custom location based on the required authorization.

Suppose your administrator disabled the Allow Private Objects Export toggle and there are few packages that contains private objects. In such a case, only you can include public objects to your package. No other user will be able to view or edit any private objects.

To import any private object, you must have these permissions:

• Lifecycle rights such as Read, Maintain, and Share – enables you to read, maintain, and share objects.
• Public Files access rights such as Read, Create – enables you to create and import private objects.

If your package includes private objects, it is imported to My Files  Public  Content Network. However, you can move it to the custom location based on the required authorization.