> [!abstract] Summary > Workaround for **"Copy to Global" being greyed out** in Prism — a version-related issue. Uses **manual Copy + Paste-as-new-version** between Local and Global, which is also a cleaner workflow because it avoids having a scene that exists in both Local and Global at the same time. > [!info] First seen > Issue reported on **2025-09-22** — version mismatch in Prism. May or may not still apply depending on the version you are running. --- # The Issue In some Prism builds, **"Copy to Global"** is greyed out on a local scene: ![[image-67.png]] --- # Workaround — Manual Copy → Paste new version This workflow also avoids ending up with a scene that exists **both in Local and Global at the same time** (which is a frequent source of "I updated my local but never published" mistakes). ### Local → Global (publishing your work) 1. On the local scene, right-click → **Local / Copy**. - ![[image-68.png]] 2. Then right-click → **Global / Paste new version**. - ![[image-69.png]] You now have a clean published global scene, with no stale local twin. ### Global → Local (going back to local work) When you want to bring a published scene back to local for new work: 1. Right-click on the global scene → **Global / Copy**. 2. Right-click → **Local / Paste new version**. Your published global scene stays untouched in Global: ![[image-70.png]] --- # Why This Is Better Even Without the Bug - **One scene = one place at a time.** No accidental "I edited the local but forgot to push to global" situations. - The version history is **clean and explicit** — every Local↔Global transfer is a deliberate new version. - It matches the **Local / Global** mental model that Prism is trying to teach. --- # 🔗 Related - [[../PRISM MOC Protocol|PRISM MOC]] - [[PRISM a trier|PRISM — Working Notes]] — Local vs Global basics. - [[PRISM Installation and Overview|PRISM Installation and Overview]] — full Prism guide.