Profiles & Team Sharing

Command Pocket shares data with your team through per-user profile files: each team member commits their own JSON file, so there are no merge conflicts.

Team collaboration settings

How it works

  • On first launch you are asked to pick a profile name. Your profile is stored at .../CommandPocket/Data/Profiles/{name}.json.
  • In Settings → Team Collaboration, choose which data the profile shares: Pocket, Notes, Colors, Quick Actions. Each toggle is independent and per-profile.
  • Commit your profile file to Git. Teammates pull it and see your shared data inside their own Command Pocket.

Managing profiles

  • Create, clone, rename and delete profiles from Settings. Switching profiles takes effect immediately, no restart needed.
  • The active profile is a per-machine setting: two team members can have different active profiles without conflicts.
  • If another machine wrote to the same profile file in between, Command Pocket warns you before overwriting.

Use one profile per person. A profile file is meant for a single user. If two people share the same profile name and edit it around the same time, the last save wins and the other person's changes to that file can be overwritten and lost. Command Pocket warns you when a file changed underneath you, but it cannot merge the two. Give each teammate their own profile name, and commit often so anything important is backed up in Git history.

Team categories

Pocket categories are team data: even when Pocket sharing is off, the category list lives in the shared Data/SharedData.json, so the whole team keeps a consistent taxonomy.

Where exactly does everything live on disk? See Data, Backup & Upgrading.