Team sync

Why team sync?

Otherwise everyone in the team sets up the same host profiles, URL profiles and filters by hand – and everyone a little differently. With team sync, one person maintains the settings in a team package and everyone else takes them over. There is no FrontTailor server for this: the file lives wherever your team already keeps files. from Team

A package can contain these sections: host profiles, URL profiles, OData filters, replay requests, snippets, PII masking rules, palette favourites, bookmarks, known errors, morning check lists and performance budgets. How a package is created and signed is described under Team packages.

The Team tab has four cards: Team packages (sources with their state), Preview (appears as soon as a package is checked), Import & export and Local settings.

Subscribe to and fetch a package

1. Open an app on your SAP system, then the Team tab in the panel.
2. Under Subscribe to a package URL, enter the address of the package file your team maintains and click Subscribe. Allow access to this host when the browser asks.
3. Subscribing itself loads nothing yet. Click Fetch at the new source.
4. The Preview opens with all changes compared to your settings. Review them and click Apply – see Review changes.

The URL must be HTTPS (HTTP only for localhost). FrontTailor refuses a user name, password or token parameter in the URL before anything is stored. If the host needs a sign-in, sign in once in the browser; FrontTailor uses that browser session and stores no credentials of its own.

1. If your administrator provides packages, this says how many and whether they are fetched on a schedule – here every 60 minutes.
2. If the policy requires signatures, FrontTailor names the trusted keys.
3. The state of the source: “Not fetched yet”, “Up to date”, the number of open changes, “Access required” or “Error”.
4. The signature: “Signed · …” with the key ID, “Unknown key”, “Unsigned” or “Invalid signature”.
5. Review … changes opens the preview. Without open changes the button says Show.
6. Fetch loads the current version. Without access to the host, the button says Allow access.

Each source lists the URL, the package version (date and author), Last fetched and Last applied. You can have up to 20 own sources.

Review and pick changes

The preview compares the package with your settings, section by section. Each change is marked New, Changed or Removed and shows the fields before → after. Only entries that earlier came from this source and are missing from the package are removed; team sync never deletes what you created yourself.

1. Conflicts show as a tag on the change: “Own local entry” (same key, but not from this source) or “Changed locally” (from this source, changed by you since).
2. One checkbox per change, one per section. Conflicts are not preselected – your version stays unless you select the change.
3. Decline declines all open changes. They are suggested again only when their value in the package changes.
4. Apply (n) applies the selected changes. Whatever you did not select counts as declined.

Other notes in the preview: “This package is not signed. Only apply it if you trust where it comes from.” for unsigned packages, and “Invalid package entries skipped: n.” when single entries were invalid – the rest of the package stays usable.

Packages provided by your administrator

Your administrator can provide packages by policy (up to 10). They are listed with the tag Administrator and cannot be removed. With a schedule set, FrontTailor fetches them automatically – they are still applied only after your review. The source then shows the number of open changes.

1. “Provided by your administrator: the package is applied as a whole; single changes cannot be left out.”
2. All changes are selected and locked.
3. Apply all applies the package. If you changed provided entries locally, they show as “Changed locally” on the next fetch and are reset with the package.

If the policy requires signatures, FrontTailor accepts only packages signed with one of the configured keys – provided packages, own subscriptions and imports alike. An invalid signature is always rejected. What administrators can configure is described under Policy for team packages.

Import and export

Without a URL, it also works by file or clipboard, in the Import & export card.

1. Package file: choose a .json file.
2. Or paste the package: paste the content of the file – a signed package exactly as it is.
3. Check package opens the preview. “Nothing is applied yet” – you pick changes just like with a subscription.
4. Sections for the export, with the number of your local entries per section.
5. Download saves the package as a file, Copy puts it on the clipboard. Package name and author are required.

The export is unsigned and contains no credentials: secret headers and query values are removed. Whoever publishes it as a team package signs it first – see Sign a package.

Local settings and removing sources

The Local settings card (collapsed at first) shows, per section, how many entries this browser holds and where they come from.

1. One row per section: Local (all entries), From team, Changed locally (from the team, changed by you since) and Administrator (from provided packages).

Remove source (bin icon at the source) drops an own subscription or import. The applied entries stay and from then on count as your local entries.

The tab has no shortcut of its own. Palette favourites from a package show up in the command palette (Alt+Shift+K), see Command palette.

What is transferred

When fetching, the extension’s service worker sends a plain GET request to the package URL – with what the browser sends for that address anyway, including the cookies of your session with that host. No data from your SAP systems or from FrontTailor goes out. Sources, packages and the origin of entries are kept only in chrome.storage.local, never in synced storage. More under Privacy.

Common problems