Post-Deployment Information for Portal Administrators 
This section provides information for portal administrators about managing content that was modeled in Visual Composer.
Managing Modeled Content
Users
No user or permission management is performed in Visual Composer.
For example, you model a role and associate content to it in Visual Composer. When you deploy the role to the portal, the associated content is included (as dependencies) with the role. After deployment, a portal administrator must assign users to the role in the portal.
Any permissions required for viewing modeled content or running applications contained within that content must be assigned in the portal by a portal content/system administrator.
More information: see Portal Permissions.
Applications
In Visual Composer, you can include applications into modeled portal content in two ways:
Search for an existing portal application or portlet and drag it into a model
Create a new application with Visual Composer tools by dragging a Composite View icon into an iView model
The content created in the portal points to the relevant application, but appropriate permissions must be set in the portal to view them at runtime.
Content
Content deployed from Visual Composer to the portal is moved to predefined folders in the portal (Content Provided by SAP and/or Content Provided by Other Vendors).
Caution
It is strongly recommended not to move, change, or delete modeled content. Doing so may cause serious runtime inconsistencies and unexpected behavior.
You can copy and create delta links from deployed content, which you can manage in the same way any other non-modeled portal content. Standard portal behavior of delta links and copies of modeled content is maintained.
To modify deployed content, make the changes in Visual Composer and redeploy.
Preview Role Cleaning-Up
With each deployment of modeled content from Visual Composer the deployed content is added to the VC Dev Preview role to enable a portal preview of the content from Visual Composer. Periodic clean-up of the preview role is necessary to prevent the amount of content from becoming unwieldy. For information about how to clean up the VC Dev Preview role in the portal, refer to SAP Note 1081909.
Transport
Content modeled in Visual Composer is transported within its development component using the NWDI transport mechanism.
NoteNWDI does not transport user assignments and permissions to the target system.
End of the note.You may also need to transport some non-modeled portal objects to other systems, such as:
Portal objects that you reused in your models
More information: Reusing Existing Components
Delta links to modeled content, to which you made property changes in the portal environment
You can transport these objects using two different methods:
Export/import of transport packages (EPAs) using the standard portal transport tools
More information: Transporting Portal Objects.
Transporting EPAs from NWDI
More information: Adding Transport Packages to NWDI.
Both methods enable transport of permissions. Using NWDI also enables source control.