Skip to main content
Palette Desktop is built for shared workspaces. Put your workspace folder on a cloud sync service, and your whole team is in. Watch the video

​
How it works

Pick where the folder lives:
  • Google Drive
  • Dropbox
  • iCloud
  • Any other folder sync tool your team already uses
Each person on your team installs Palette Desktop and points it at the same folder. The cloud service syncs files between machines. Palette Desktop handles the agent work on top. No invite flow. No separate Palette workspace to set up. If your team can share a folder, your team can share a Palette workspace.

​
Why this works in parallel

When two people work in the same folder through chat-based tools, things get messy fast. Files overwrite each other. Drafts get lost. The team stops trusting the shared folder. Palette Desktop fixes this with sessions:
  • Each person works in their own session, which is a sandboxed clone of the folder
  • The agent writes to the sandbox, not the live folder
  • When the session is ready, the person reviews changes and saves back
Palette compares the session with the main folder during Update and Save. If both changed the same file, Palette can detect the conflict and ask you to resolve it before continuing. Cloud sync distributes the saved files between teammates; it is not Palette’s merge engine.

​
Setting it up

The first time:
  1. One person creates the workspace folder, ideally inside their Google Drive or Dropbox
  2. Share the folder with the team through Google Drive or Dropbox
  3. Each teammate downloads Palette Desktop and points it at their synced copy
After that:
  • Everyone opens Palette Desktop, picks the shared folder, and starts a session
  • Work happens in parallel, sandboxed, reviewed before saving back

​
When things get crowded

Sessions reduce collisions, but they cannot make them impossible. If the main folder and a session changed the same file, Palette can open a conflict resolver during Update or Save. Review both versions and choose the content that should continue. Do not rely on cloud sync to merge concurrent edits. For larger teams, consider:
  • One workspace per major area of work, not one workspace for the whole company
  • A naming convention for sessions so people can tell what each one is for
  • A light norm around who’s working on what, the same way you’d handle any shared doc

​
Next

  • Sessions, the unit of work that makes parallel safe
  • Workspaces, what the workspace itself is
  • Marketplace, shared folder systems and workflows your team can use