The team library

Choose File > Add Team Library, or enter an absolute shared-folder path, file URL, HTTPS git URL or SSH git URL in Settings > Advanced > Library. An MDM can set TeamLibraryURL instead; the person cannot edit that managed value. The managed source uses the remote's default branch. An invalid managed value does not fall back to your personal source or branch; ask IT to correct the profile.

The source is a library root containing group folders, each with group.json and macro JSON files. Team git branch selects a branch; HEAD uses the remote's advertised default branch. If that default changes, refresh before publishing. Git uses your configured credentials, with hooks disabled. The engine checks every 5 minutes; Refresh Team Library checks on demand. Shared-folder changes are watched, validated and mirrored into a local snapshot. Sources and resolved branches have separate support-folder caches; they do not become remotes for your personal library.

Team groups have a building glyph. Their macros can run, but the store refuses edits, renames, moves and deletion.

Enable Group and Disable Group change only your local choice. The source's group.json is not edited, and the choice survives refreshes.

Edit and publish #

Choose Copy to My Library on a team macro. The personal copy is off until you enable it, so the same trigger does not fire twice. Edit it in your own group.

Choose Publish to Team on the copy and confirm the destination. A shared-folder publish writes the source folder. A git publish commits and pushes with your own credentials, so repository permissions decide who can publish. The app shows git failures; it does not silently force-push.

Pulls are fast-forward only. Git publishing uses a separate working checkout; the runnable snapshot contains only a validated commit fetched from the remote. A failed push leaves the pending commit in that checkout, without changing what runs, even after a restart. Retry publishing once access is restored. If the remote has diverged, reconcile the working checkout before refreshing. No forced reset discards unpublished work.

Team refreshes record macro and group-metadata versions in History. Activity lists how many macros and groups changed; a check that finds no change adds no entry. Audit exports include these entries as teamLibrary records, with a UTC timestamp and the cached account identity.

Invalid folder or git updates keep the last valid cached version. Team Change Log shows the git history; a plain shared folder has no git log.

A group can record its source as {"kind":"git","url":"https://example.com/team.git","branch":"main"} or {"kind":"folder","path":"/Volumes/Company/Macros"} in group.json. The loaded team overlay supplies the configured source metadata so a repository cannot redirect publishing to an unrelated path.