Teams and sync
Jingle status for team sharing, private extensions, organization permissions, sync, and migration.
After personal desktop workflows are stable, the next layer is team sharing: shared quicklinks, snippets, private extensions, organization settings, member permissions, and cross-device sync. This area needs care because it changes local-first and user-control boundaries.
Capability Status
| Capability | Status | Target |
|---|---|---|
| Local settings, themes, and memory | Ongoing | Local-first, visible, editable, and deletable by the user |
| Shared quicklinks | Planned | Team-shared URLs, parameter templates, default browser, and access scope |
| Shared snippets | Planned | Team snippets, variables, review, and sync conflict handling |
| Private extensions | Planned | Team extension publishing, install, update, and permission governance |
| Organizations and members | Planned | Members, roles, permissions, audit, and organization settings |
| Cross-device sync | Planned | Explicit sync for settings, themes, AI profile, extensions, quicklinks, snippets, and local knowledge |
| Import and migration | Planned | Migrate from old configs, other launchers, or export files into Jingle |
Sync Boundary
- Local data remains the authority. A server can only be an explicitly enabled sync or backup layer.
- Users must know what remains local and what is synchronized.
- Delete, revoke, disconnect, and disable-sync semantics must be explicit.
- Account credentials should not sync as plain settings; OAuth tokens and secrets need a separate security strategy.
- Team-shared content needs source, owner, permission, and audit information.
Release Stage
Teams and sync affect privacy, credentials, permissions, and collaboration boundaries. These capabilities will open by platform release stage, with developer-facing interfaces and security semantics documented as they become available.