Users and Asset permissions

Plasmic Studio Questions
1

Can you clarify below mentioned issues?

  1. Ability to make changes in sandbox environment and after testing and change management approval promote the selected changes to production environment
  2. Storing CSS, JS, Images and other assets as global level and Team level
  3. Access control at different levels such as Folder, Files for users and groups
  4. Integration with Analytics platforms such as Google Analytics in Plasmic studio
2

  1. This feature is called branching, and it is currently available in Early Access to all Enterprise customers. We will soon be releasing it for all Growth level customers as well.

  2. Custom css, js, and other code typically exists in your code base. You can also take advantage of cross project imports to reuse the same assets across different environments. This can include images, styles, components. It can also include components that have Custom HTML Embed, where you can write script tags and style tags. Importing projects | Learn Plasmic

  3. You can configure a different ACLS at the team, workspace, and projects levels. You can think of workspaces as folders.

  4. You can just add Google Analytics or any other analytics integration directly to your nextjs or other code base - plasmic will work fine with it added.

Let me know if that helps.

3

Thanks for reply