Skip to content

Enterprise Unified Sync UX

This guide covers SkillMeat's enterprise synchronization interfaces for managing artifact consistency across teams and tiers. Use these tools to monitor sync health, detect divergence, manage cascade policies, and enforce updates organization-wide.

Table of Contents

Overview

The Enterprise Unified Sync UX provides two complementary interfaces for managing synchronization:

  1. Team Sync Dashboard — Team-level view for managing artifacts across team members
  2. Admin Sync Management — Organization-wide view for managing tiers, policies, and propagation

Key Concepts

Divergence: When an artifact's version in one scope differs from the baseline for that tier. Divergence can be intentional (team customization) or unintentional (missed updates).

Cascade Policy: An organization-wide rule that automatically propagates artifact updates from one tier to the next (e.g., org → team → user), with configurable enforcement modes.

Sync Health: Metric showing how many artifacts in a team or organization are in sync with their baseline versions.

Tier Propagation: The process of pushing artifact updates down through organizational tiers, from enterprise → team → user scope.

Team Sync Dashboard

The Team Sync Dashboard is located at /enterprise/team-sync and provides a team-lead view of synchronization across team members and their artifact deployments.

Who Can Access

  • Team Admins — Can see sync status for their team members' artifacts
  • System Admins — Can see sync status across all teams

Dashboard Components

Team Selector

At the top of the dashboard, choose which team to view:

Team:  [All Teams ▼]
  • All Teams — Aggregated view showing all teams' artifacts
  • Specific Team — Filter to a single team's artifacts

Artifact Sync Table

A table showing every artifact deployed within the team, with key columns:

Column What it shows
Artifact Name Human-readable artifact name and type badge
Type Skill, command, agent, etc.
Status Badge Visual indicator (green = in sync, yellow = diverged, red = out of sync)
Divergence Count of team members whose scope is diverged from the team baseline
Cross-Axis Divergence Indicator showing which tiers are out of sync (e.g., artifact is in sync with org but diverged at user level)
Last Synced Timestamp of most recent successful sync to any member's scope
Actions Bulk sync button to push updates to all team members

Status Indicators

Green Badge (In Sync): All team members' scopes match the team baseline version. No action needed.

Yellow Badge (Diverged): Some team members have different versions than the team baseline. This can happen due to: - Local customization by team members - Pending updates from higher tiers not yet applied - Intentional version pins by team admins

Red Badge (Critical): Significant drift detected. One or more team members are running versions that are outdated or conflicting. Review and apply sync urgently.

Cross-Axis Divergence Indicator

Shows visual information about which tiers are out of sync:

Artifact: canvas (skill)

Sync State:
  Org Tier:     [✓ In Sync]
  Team Tier:    [⚠ Diverged]  (2 members affected)
  User Tier:    [⚠ Diverged]  (1 member affected)

This helps identify whether the divergence is isolated to your team or cascades from higher tiers.

Common Tasks

Check Overall Team Sync Health

  1. Navigate to /enterprise/team-sync
  2. Select your team from the Team selector
  3. Scan the Status column:
  4. Green badges: OK
  5. Yellow/Red badges: Review and act

Bulk Sync Team Artifacts

To push the team baseline to all team members at once:

  1. Select artifacts that are diverged (yellow/red badges)
  2. Click Bulk Sync at the bottom of the table
  3. Confirm the operation in the dialog
  4. Monitor the sync progress — artifacts update within seconds

Investigate Divergence

When you see a yellow badge:

  1. Click the artifact row to expand details
  2. View which team members are diverged and by how much
  3. Review the version difference (what changed between team baseline and member versions)
  4. Choose to sync, merge, or investigate further

Admin Sync Management

The Admin Sync Management page is located at /admin/sync-management and provides organization-wide synchronization controls for system administrators.

Who Can Access

  • System Admins — Full access to all controls
  • Team Admins — Read-only view of sync health (may be granted write access for their tier)

Page Components

Organization Sync Health Panel

A dashboard showing aggregate metrics across all teams and tiers:

Sync Health Overview

Total Artifacts:        157
Artifacts In Sync:      149 (95%)
Artifacts Diverged:     8 (5%)
Artifacts Out of Sync:  3 (2%)

Teams Healthy:          12/14 (86%)
Teams With Issues:      2

Metrics:

  • Total Artifacts — Count of all artifact deployments across the org
  • In Sync — Artifacts matching their scope baselines (green)
  • Diverged — Artifacts intentionally or unintentionally different from baselines (yellow)
  • Out of Sync — Critical sync failures requiring attention (red)
  • Teams Healthy — Teams with no sync issues (percentage)

Tier Propagation Controls

Controls for pushing artifact updates through the organizational tiers (enterprise → team → user):

Tier Propagation

Source Tier:  [Organization ▼]
Target Tier:  [Team ▼]

Propagation Mode:
  ☐ Enforce Override (force all targets to match source)
  ☑ Notify Only (send notifications, let teams decide)

Policy:
  ☑ Cascade Down (propagate from team to users automatically)

[Propagate Now] [Schedule Propagation]

Modes:

  • Enforce Override — Artifacts at the target tier are replaced with the source version immediately. No merge or notification.
  • Notify Only — Notifications sent to target tier owners; they decide whether to accept updates.

Cascade Options:

  • Cascade Down — After propagating to the target tier, automatically continue to the next tier down. For example, if propagating org → team with cascade enabled, team → user propagation triggers automatically.

Compliance Audit Table

A detailed table of all recent sync operations, visible only to system admins:

Column What it shows
Operation Type of sync operation (propagation, force-sync, merge, etc.)
Artifact Artifact name and type
Source Tier Where the artifact is being synced from
Target Scope Which teams/users are affected
Timestamp When the operation occurred
Admin Which admin initiated the operation
Status Success, in progress, or failed

Use this table to: - Track who synced what and when - Investigate sync failures - Prepare compliance reports - Identify patterns (e.g., which teams need frequent manual syncs)

Sync Operations Log

Real-time view of ongoing sync operations:

Active Operations (3)

[████████░░] canvas (skill) → 12 teams
             Status: In Progress (8/12 complete)
             ETA: 45 seconds

[██████████] my-command (command) → 8 teams
             Status: Complete
             Completed at 2026-04-04 14:23:15

[░░░░░░░░░░] security-audit (agent) → 14 teams
             Status: Queued
             Will start in: 2 minutes

Watch operations as they progress, and cancel if needed.

Hard Update Enforcement

Advanced settings for forcing artifact updates across the organization (used when cascade policies alone are insufficient):

Hard Update Enforcement

Enforce Artifacts:
  ☑ canvas (skill)
  ☑ security-audit (agent)
  □ my-command (command)

Force Update Behavior:
  ● Overwrite (replace all versions)
  ○ Merge (if possible)
  ○ Notify (ask permission)

Conflict Resolution:
  Automatic: [Keep Source Version ▼]

[Enforce Now]

Use cases:

  • Emergency security patches that must apply immediately
  • Compliance updates that cannot be deferred
  • Critical bug fixes that affect production
  • Organizational policy changes that must take effect immediately

Divergence Indicators

Divergence is visual and quantified throughout the sync management interface.

Understanding Divergence Colors

Badge Color Meaning Action
In Sync Green Version matches baseline None needed
Diverged Yellow Version differs from baseline Review & decide
Out of Sync Red Significant drift / conflict Review urgently
Missing Gray Artifact not deployed to scope Deploy or accept missing

Divergence Details

When you click on a diverged artifact, you see:

What Changed: - Blue badge: Changes from upstream (organization or collection) - Amber badge: Local customizations (team or user changes) - Red badge: Conflicting changes (both sides modified)

Who's Affected: - List of team members / teams with diverged versions - Version hash for each diverged scope - Last sync attempt timestamp

Resolution Options: - Sync (push baseline to all diverged scopes) - Merge (attempt to combine changes) - Review diff (see exactly what's different)

Cross-Axis Divergence

Some artifacts may be: - In sync at the organization tier - Diverged at the team tier - Out of sync at the user tier

The interface shows this vertical hierarchy so you understand whether divergence is localized or cascading.

Cascade Policies

Cascade policies automate tier propagation across your organization.

What Are Cascade Policies?

A cascade policy defines a rule like: "When artifact X is updated at the organization tier, automatically push it to all teams, and then to all users, using enforce-override mode."

Policies run automatically on a schedule (default: every 5 minutes) or can be triggered manually.

Creating a Policy

  1. Navigate to /admin/sync-management
  2. Click Cascade Policies tab
  3. Click Create Policy
  4. Fill in the policy details:
Policy Name: "Canvas Updates"
Description: "Auto-propagate canvas skill updates org → team → user"

Source Tier:        [Organization ▼]
Target Tier:        [Team ▼]
Cascade To:         [User ▼]

Artifacts:          [Select artifacts...] (canvas)
Propagation Mode:   ☑ Enforce Override
Merge Strategy:     [Overwrite ▼]
Schedule:           [Every 5 minutes ▼]

☑ Enabled
  1. Click Create

Policy Management

View Policies

List all active cascade policies:

Cascade Policies (6)

Name                      Source    Target   Mode               Schedule     Status
──────────────────────────────────────────────────────────────────────────────────
Canvas Updates            Org       Team     Enforce Override   Every 5 min  Active
Security Audit Policy     Org       Team     Notify Only        Every hour   Active
SDK Propagation           Team      User     Enforce Override   Every 15 min Paused

Edit a Policy

Click a policy row to edit its schedule, target tiers, or propagation mode. Changes take effect immediately.

Disable/Enable a Policy

Toggle the checkbox in the Status column. Disabled policies don't run but can be re-enabled.

Delete a Policy

Click the delete button to remove a policy. This does not affect artifacts already synced; it only stops future automatic propagations.

Policy Best Practices

Create policies for critical artifacts: - Organization-wide SDKs and frameworks - Security compliance artifacts - Standardized templates and workflows

Use enforce-override for: - Security patches (must apply immediately) - Compliance updates (cannot wait for team approval) - Bug fixes affecting production

Use notify-only for: - Suggestions and improvements - Optional enhancements - Artifacts teams might need to customize

Set appropriate schedules: - Security patches: every 5–15 minutes - Stable artifacts: every hour - Optional updates: daily or manual

Bulk Sync Operations

Sync multiple artifacts across multiple teams in a single operation.

Performing a Bulk Sync

  1. From the Admin Sync Management page, select artifacts to sync
  2. Click Bulk Sync Selected
  3. Choose your sync strategy:
  4. Overwrite — Replace target versions with source
  5. Merge — Attempt intelligent merge
  6. Notify — Send notifications (no auto-update)
  7. Confirm the operation
  8. Monitor progress in the Sync Operations Log

Bulk Operation Details

Bulk Sync Operation

Selected Artifacts: 5
  ☑ canvas (skill)
  ☑ my-command (command)
  ☑ security-audit (agent)
  ☑ design-system (composite)
  ☑ workflow-engine (workflow)

Target Scopes: 14 teams
Estimated Impact: 70 deployments

Strategy:     [Overwrite ▼]
Cascade Down: ☑

[Start Bulk Sync] [Preview Changes]

Monitoring Bulk Operations

The Sync Operations Log shows:

  • Current progress (N/M complete)
  • Which scopes succeeded/failed
  • Any errors or conflicts requiring attention
  • Detailed logs for each scope

Sync Operations Audit Log

Every sync operation is logged for compliance and debugging.

Viewing the Log

Navigate to /admin/sync-management and select the Audit Log tab:

Audit Log (showing 50 most recent operations)

Timestamp              Admin     Artifact          Operation      Status
──────────────────────────────────────────────────────────────────────
2026-04-04 14:23:15   alice     canvas            Propagate      Success
2026-04-04 14:18:42   bob       security-audit    Force Sync      Success
2026-04-04 14:15:00   alice     my-command        Merge           Conflict
2026-04-04 14:10:30   system    design-system     Auto-Propagate  Success

Filtering and Searching

Use filters to find specific operations:

  • Date range — Show operations from a specific time period
  • Admin — Filter by who initiated the operation
  • Artifact — Filter by artifact name or type
  • Operation type — Filter by sync, propagate, force-sync, merge, etc.
  • Status — Show only successful, failed, or in-progress operations

Exporting Logs

Download audit logs as CSV for external reporting or compliance documentation:

  1. Set your filter criteria
  2. Click Export to CSV
  3. Open in Excel or your preferred tool

Best Practices

Monitoring Sync Health

  1. Daily check — Visit the Team Sync Dashboard or Admin Sync Management to spot divergence trends
  2. Weekly review — Export audit logs to track sync operations and identify patterns
  3. Alert on red — If artifacts turn red (out of sync), investigate immediately
  4. Trend analysis — Are certain teams consistently diverged? Investigate why.

Managing Divergence

Intentional Divergence (Customization): - Document why the team customized the artifact - Create a separate team-owned version if customization will be permanent - Plan merge strategy if the artifact updates frequently

Unintentional Divergence (Missed Updates): - Use bulk sync to push the update to all affected scopes - Review why the update was missed (policy not running? Manual override?) - Adjust cascade policy schedule if needed

Conflicting Divergence (Both sides changed): - Review the diff carefully - Choose: keep local changes, accept upstream, or merge intelligently - Document the decision for future reference

Cascade Policy Strategy

  1. Start conservative — Create policies for only critical artifacts first
  2. Use notify-only initially — Gather feedback before enforcing
  3. Graduate to enforce-override — Once stable, enable automation
  4. Monitor after each change — Watch sync health immediately after deploying new policies
  5. Schedule around workflows — Avoid propagation during peak development hours

Security and Compliance

  • Audit trail — Keep audit logs for at least 90 days for compliance
  • Approval workflow — For sensitive artifacts, require manual approval before propagation
  • Hard update enforcement — Use only for emergency security patches
  • Review permissions — Limit cascade policy creation to system admins
  • Notify on propagation — Always notify users when critical artifacts are updated

Troubleshooting

Bulk Sync Appears Stuck

Symptom: Progress bar not advancing for 5+ minutes.

Solution: 1. Check the Sync Operations Log for error messages 2. If still stuck after 10 minutes, cancel the operation 3. Retry with a smaller subset of artifacts 4. Contact your system administrator if errors persist

Cascade Policy Not Running

Symptom: Artifacts not syncing automatically at scheduled time.

Solution: 1. Verify the policy is enabled (toggle in Status column) 2. Check the policy schedule — does it match your expectation? 3. Review the audit log — when was the policy last executed? 4. If last run was recent, policy is working; next run will be on schedule 5. Manually trigger the policy by clicking Run Now to test

Conflicts During Merge

Symptom: Merge strategy shows "Conflicts" status.

Solution: 1. Review the artifact detail page to see conflicting sections 2. Decide: keep local, use upstream, or merge manually 3. Use the conflict resolution UI to choose approach 4. If automated merge won't work, use overwrite or notify-only strategy instead

Some Teams Not Syncing

Symptom: Bulk sync succeeds for some teams but fails for others.

Solution: 1. Check the audit log for specific error messages per team 2. Common causes: - Team scope is locked (enforcement enabled) - Network connectivity issues to a specific team's deployment - Artifact doesn't exist in that team's tier yet 3. Filter the audit log by status = "Failed" to see exactly which scopes failed 4. Retry failed scopes individually or contact system admin

Divergence Won't Clear After Sync

Symptom: After bulk sync completes successfully, artifacts still show as diverged.

Solution: 1. Refresh the page (browser may have stale cache) 2. Check if the sync included all affected scopes 3. Verify the baseline was updated (check via Admin Sync Management) 4. If baseline didn't update, the sync may have been notify-only; check the audit log 5. Run a second sync if needed, or contact system admin

See Also