Skip to content

Enterprise Admin Workflow Guide

This guide covers the core administrative workflows in SkillMeat's enterprise edition, including inspecting artifacts, performing bulk actions on multiple artifacts, managing collections, and triaging activity feeds.

Table of Contents

Overview

The Enterprise Admin Dashboard provides four primary workflows for managing your organization's artifacts and collections:

  1. Inspecting Artifacts — Deep-dive into artifact governance, propagation, and change history
  2. Bulk Actions — Perform operations on multiple artifacts simultaneously (deploy, lock, delete, reassign)
  3. Managing Collections — Create, organize, and manage collections for teams and projects
  4. Activity Monitoring — Review prioritized activity feed for actionable governance events

Key Concepts

Artifact Inspection: Clicking an artifact row opens a detailed modal with three tabs: - Governance — Ownership, enforcement status, permissions, and scope - Propagation — Deployment targets, cascade policies, and version tracking - Audit Trail — Complete history of changes, deployments, and access events

Bulk Actions: Select multiple artifacts to apply the same action across them (deploy globally, lock, unlock, delete, or reassign ownership).

Collections: Organized groupings of artifacts that can be deployed together or shared with teams.

Activity Feed: Prioritized log of governance events (deployments, enforcement changes, violations, team changes) with filtering and deep-linking to affected artifacts.

Inspecting Artifacts

Click any artifact row in the dashboard to open the Artifact Inspection Modal, which provides detailed governance, propagation, and audit information.

Opening an Artifact

  1. Navigate to the Enterprise Admin Dashboard
  2. Locate the artifact you want to inspect in the artifact list
  3. Click anywhere on the artifact row (not the checkbox)

The artifact inspection modal opens with three tabs.

Governance Tab

The Governance tab shows ownership and enforcement information:

Field What it shows
Owner Who owns this artifact (user, team, or enterprise)
Owner Type Scope: enterprise, team, or personal
Current Status Active, draft, deprecated, or archived
Enforcement Status Locked (enforce_override enabled) or unlocked
Enforcement Mode "Silent Override" (auto-push) or "Notify Only" (manual pull)
Access Control Who can view, edit, or delete this artifact
Created Date When the artifact was created
Last Modified When it was last updated and by whom
Source URL Upstream GitHub link (if tracking a source)

What you can do: - Check enforcement status at a glance - Verify owner and access permissions - See modification history - Identify if the artifact is tied to a GitHub source

Propagation Tab

The Propagation tab shows deployment targets and cascade policies:

Section What it shows
Deployment Targets List of teams, projects, and user collections this artifact is deployed to
Deployment Status Which targets are in sync, diverged, or experiencing errors
Cascade Policy How updates propagate down tiers (enterprise → team → user)
Last Deployment When this artifact was last deployed and by whom
Version in Each Target Specific version deployed to each team/project/collection
Pending Updates If new versions are waiting to be pushed to any target

What you can do: - See which targets have received the latest version - Identify which targets are out of sync - Review enforcement cascade behavior - Check deployment timestamps - Trigger re-deployment if needed

Audit Trail Tab

The Audit Trail tab shows a complete history of changes:

Event Information logged
Creation Who created the artifact and when
Modifications What changed, who changed it, and when
Deployments Target, deployment time, enforcement mode, outcome
Access Events Who accessed (viewed/modified) the artifact and when
Enforcement Changes When enforcement was enabled/disabled and by whom
Ownership Changes When the artifact was reassigned to a different owner

What you can do: - Audit who has modified the artifact - See complete deployment history - Track enforcement changes and their timing - Identify access patterns - Verify compliance with governance policies

Example Inspection Workflow

To audit a critical security artifact:

  1. Click the artifact row for security-audit-agent
  2. Governance tab: Confirm it's enterprise-owned with enforcement enabled
  3. Propagation tab: Verify all 5 teams received the latest version
  4. Audit Trail tab: Review recent modifications to confirm authorized changes only
  5. Close the modal and take action if issues detected

Using Bulk Actions

Bulk actions allow you to perform the same operation on multiple artifacts simultaneously.

Selecting Artifacts

  1. Navigate to the artifact list in the dashboard
  2. Check the checkbox next to each artifact you want to select
  3. Use the top-level checkbox to select all visible artifacts
  4. The Bulk Action Bar appears at the bottom of the screen showing:
  5. Number of artifacts selected (e.g., "5 artifacts selected")
  6. Available actions for those artifacts
  7. Clear selection button

Available Bulk Actions

Once you've selected artifacts, the bulk action bar displays available operations:

Deploy Global

Pushes the selected artifacts to all downstream teams and user collections.

  1. Click Deploy Global
  2. A confirmation dialog appears with options:
  3. Enforcement Mode: Choose "Silent Override" (auto-push) or "Notify Only" (manual pull)
  4. Review Selected: See list of artifacts being deployed
  5. Click Confirm Deploy

Deployment proceeds in the background, and you'll see a progress indicator.

Lock / Unlock

Enables or disables enforcement on the selected artifacts.

Lock (Enable Enforcement): 1. Select artifacts 2. Click Lock 3. Confirm in dialog 4. All selected artifacts now have enforce_override: true 5. Lock icon appears on the artifacts 6. Local users cannot modify these artifacts

Unlock (Disable Enforcement): 1. Select artifacts with lock icons 2. Click Unlock 3. Confirm in dialog 4. All selected artifacts now have enforce_override: false 5. Lock icons disappear 6. Local users can now modify these artifacts

Delete

Removes selected artifacts from the enterprise.

  1. Select artifacts
  2. Click Delete
  3. A warning dialog appears listing:
  4. Artifacts being deleted
  5. How many deployments will be affected
  6. Whether any teams/projects depend on these artifacts
  7. Click Confirm Delete to proceed

Important: Deletion is permanent and may break downstream artifacts that depend on the deleted artifacts. Review carefully before confirming.

Reassign

Changes the owner of selected artifacts.

  1. Select artifacts
  2. Click Reassign
  3. A dialog appears with:
  4. Current owner (e.g., "enterprise", "team-name", "user-email")
  5. Owner type dropdown (enterprise, team, or user)
  6. If reassigning to a team, select which team from the dropdown
  7. If reassigning to a user, select from the user directory
  8. Click Confirm Reassign

Example Bulk Action Workflows

Deploy all new skills organization-wide:

  1. Filter by type = "skill" and date created = "last 7 days"
  2. Select all visible artifacts (use top checkbox)
  3. Click Deploy Global → choose "Silent Override" → confirm
  4. All new skills deploy to every team and user collection

Lock down critical artifacts:

  1. Filter by tag = "security" and status = "active"
  2. Select all visible artifacts
  3. Click Lock → confirm
  4. All security artifacts are now read-only with enforcement enabled

Archive deprecated artifacts:

  1. Filter by status = "deprecated"
  2. Select all visible artifacts
  3. Click Delete → review dependencies → confirm
  4. All deprecated artifacts are removed from the system

Managing Collections

Collections are organized groupings of artifacts that can be deployed together or shared with specific teams.

Creating a Collection

  1. Click the Create Collection button (usually at the top of the collections section)
  2. A dialog opens with the following fields:
  3. Name (required): Short, descriptive identifier (e.g., data-science-toolkit)
  4. Description (required): Explain what this collection contains and who should use it
  5. Team (optional): Assign the collection to a specific team, or leave unassigned for enterprise-wide
  6. Tags (optional): Add tags for easier discovery (e.g., ml, experimental, tier-1)
  7. Icon/Color (optional): Choose a visual identifier for the collection
  8. Click Create

The collection now appears in your collections list and is ready to receive artifacts.

Adding Artifacts to a Collection

  1. Navigate to the collections view
  2. Click the collection name to open its details
  3. Click Add Artifacts or + Add
  4. A dialog or panel appears with:
  5. Search bar to find artifacts
  6. Filter options (type, status, owner, tag)
  7. List of available artifacts with checkboxes
  8. Select the artifacts you want to add
  9. Click Add Selected or Confirm

Artifacts are now part of the collection and can be deployed together.

Viewing Collection Details

  1. Click the collection name from the collections list
  2. The Collection Details page shows:
  3. Metadata: Name, description, owner, creation date
  4. Artifacts: List of all artifacts in the collection with counts by type
  5. Deployments: History of deployments (when, where, by whom)
  6. Team Assignment: Which team(s) use this collection
  7. Settings: Access controls and visibility

Using the Kebab Menu

Each collection has a kebab menu (three dots) with additional actions:

Action What it does
Edit Change name, description, team, or tags
Deploy Push all artifacts in the collection to specified targets
Duplicate Create a copy of the collection with all artifacts
Share Grant access to specific teams or users
Delete Remove the collection (artifacts are not affected)
Export Download collection metadata and manifest

Example Collection Workflows

Create and deploy a data science toolkit:

  1. Click Create Collection → name it Data Science Toolkit
  2. Description: "Pre-curated skills and commands for data analysis"
  3. Team: "Data Science" (or leave unassigned for org-wide)
  4. Click Create
  5. Open the collection → Add Artifacts
  6. Search for and select: pandas-analysis, matplotlib-charts, jupyter-launcher
  7. Click Add Selected
  8. Open kebab menu → Deploy → select teams → confirm

All teams now have access to the data science toolkit.

Organize artifacts by project:

  1. Create a collection for each project: Project Alpha, Project Beta, etc.
  2. Add relevant artifacts to each collection
  3. Assign each collection to the responsible team
  4. Use collections as the unit of deployment (deploy entire collection instead of individual artifacts)

Triaging the Activity Feed

The Activity Feed is a prioritized log of governance events, deployments, and team changes. Use it to stay informed about organizational changes and take action on issues.

Accessing the Activity Feed

  1. In the Enterprise Admin Dashboard, navigate to the Activity or Feed section
  2. The feed displays recent events, sorted by priority (actionable first, then by date)

Understanding Activity Priorities

Events are color-coded and sorted by actionability:

Priority Color Event Types Action
Critical Red Enforcement violations, failed deployments, unauthorized access, policy breaches Requires immediate review and remediation
High Orange Deployment errors, enforcement disabled unexpectedly, access control changes Review soon and verify intended changes
Medium Yellow Successful deployments, ownership changes, team reassignments Monitor and log for audit purposes
Low Gray View access, artifact searches, routine sync events Informational, no action needed

Filtering the Activity Feed

At the top of the activity feed, use these filters to focus on relevant events:

Filter What it does
Event Type Show only specific event types (e.g., deployments, permission changes, sync events)
Artifact Type Show events for specific artifact types (skills, commands, agents, etc.)
Owner/Team Show events for specific owners or teams
Date Range Restrict events to a specific time period (last 24 hours, last 7 days, custom)
Status Show only resolved, unresolved, or in-progress events

Taking Action on Events

Click any actionable event in the feed to deep-link to the affected artifact:

  1. Click the event (e.g., "Deployment failed for security-audit-agent to Team Alpha")
  2. The Artifact Inspection Modal opens automatically
  3. Review the Governance, Propagation, and Audit Trail tabs
  4. Take corrective action:
  5. Re-deploy the artifact
  6. Change enforcement settings
  7. Reassign ownership
  8. Investigate access violations
  9. Close the modal to return to the feed

Example Activity Feed Workflows

Monitor critical deployments:

  1. Filter by Event Type = "Deployment" + Priority = "Critical"
  2. Review failures in the feed
  3. Click each failed deployment to open the artifact modal
  4. Check propagation tab to see which targets failed
  5. Retry deployment with corrected settings

Audit permission changes:

  1. Filter by Event Type = "Permission Change" + Owner = "enterprise"
  2. Review all permission modifications in the past month
  3. Click suspicious changes to verify they were authorized
  4. Document findings in your governance log

Track team transitions:

  1. Filter by Event Type = "Ownership Change" + Date Range = "last 30 days"
  2. See all artifacts reassigned between teams
  3. Verify downstream impacts are handled (re-deployments, consent changes)
  4. Update team documentation with new artifact ownership

Workflow Examples

Example 1: Deploy a New Security Artifact Organization-Wide

Scenario: You've created a new security audit agent and need to roll it out to all teams with enforcement enabled.

Steps:

  1. Navigate to the artifact list and find security-audit-agent
  2. Click the row to open the Artifact Inspection Modal
  3. Check the Governance tab to confirm it's enterprise-owned
  4. Close the modal, select the security-audit-agent checkbox
  5. Click Deploy Global → select "Silent Override" → confirm
  6. The artifact deploys to all teams with enforcement enabled
  7. Check the Activity Feed to confirm deployment succeeded
  8. Click the deployment event to verify it reached all targets

Result: All teams now have the security audit agent locked with enforcement, ensuring consistency.

Example 2: Audit and Lock Down Critical Artifacts

Scenario: Q4 compliance requires all critical artifacts to be locked with enforcement enabled. You need to audit which artifacts are currently vulnerable.

Steps:

  1. Filter artifacts by tag = "critical"
  2. Review each artifact:
  3. Click to open the inspection modal
  4. Check Governance tab for enforcement status
  5. Check Audit Trail tab for recent changes
  6. For artifacts without enforcement:
  7. Select them (checkboxes)
  8. Click Lock → confirm
  9. Navigate to Activity Feed
  10. Filter by Event Type = "Enforcement Enabled" + Date Range = "today"
  11. Verify all critical artifacts are locked

Result: All critical artifacts now have enforcement enabled and are documented in the audit trail.

Example 3: Organize and Deploy a Team Toolkit

Scenario: The Data Science team needs a curated toolkit of pre-configured skills and commands. You'll create the collection and manage it.

Steps:

  1. Click Create Collection
  2. Name: Data Science Toolkit | Team: Data Science
  3. Click Create
  4. Open the collection → Add Artifacts
  5. Search for and add: data-analysis-skill, visualization-command, ml-inference-agent
  6. Open the collection's kebab menu → Deploy
  7. Select the Data Science team as the target
  8. Choose enforcement mode and confirm
  9. Check Activity Feed to see the deployment event
  10. Click the deployment event to verify all artifacts arrived

Result: The Data Science team now has a curated toolkit deployed as a unit.

Example 4: Investigate a Failed Deployment

Scenario: The activity feed shows a critical deployment failure. You need to diagnose and fix it.

Steps:

  1. In the Activity Feed, filter by Priority = "Critical"
  2. Find the deployment failure event (e.g., "Deployment failed for logging-agent to Team Sales")
  3. Click the event to open the Artifact Inspection Modal
  4. Check the Propagation tab to see:
  5. Which targets failed
  6. What error messages were returned
  7. Whether it's a network issue, permission issue, or data issue
  8. Possible fixes:
  9. If it's a permission issue: reassign the artifact or update access controls
  10. If it's a data issue: edit the artifact content and re-deploy
  11. If it's a network issue: wait and retry
  12. Click Deploy (or close and use bulk actions to retry)
  13. Confirm deployment
  14. Return to the Activity Feed and verify the retry succeeded

Result: The deployment is fixed and the team receives the artifact.

Best Practices

Artifact Inspection

  1. Inspect before deploying — Always check the Governance and Audit Trail tabs before deploying to verify the artifact is in the expected state
  2. Monitor propagation — Regularly check the Propagation tab to ensure artifacts reach their intended targets
  3. Audit changes — Review the Audit Trail monthly to catch unauthorized modifications
  4. Verify source links — If tracking GitHub sources, ensure the source URL is valid and up-to-date

Bulk Actions

  1. Test before bulk deploying — Deploy to a pilot team first, then expand
  2. Group by intent — Only bulk-deploy artifacts with the same enforcement intent
  3. Document bulk actions — Record what you deployed and why in your governance log
  4. Stagger large deployments — For >50 artifacts, deploy in batches to avoid overwhelming the system
  5. Always review the list — Read the confirmation dialog carefully before confirming bulk actions

Collection Management

  1. Use collections as deployment units — Instead of deploying individual artifacts, deploy entire collections to teams
  2. Document collection purpose — Keep descriptions clear so team members understand what's included
  3. Version your collections — Create versioned copies (e.g., Toolkit v1.0, Toolkit v1.1) when making significant changes
  4. Regularly audit membership — Verify collections contain what you expect and remove obsolete artifacts
  5. Use kebab menus for organization — Duplicate collections when creating variations for different teams

Activity Feed Monitoring

  1. Check daily — Review high and critical priority events at least once per day
  2. Establish thresholds — Define what warrants escalation (e.g., deployment failures, access violations)
  3. Use filters aggressively — Filter to your area of concern rather than reviewing all events
  4. Deep-link and verify — Click events to inspect the affected artifacts in detail
  5. Document anomalies — Keep a log of unusual events for compliance and audit purposes
  6. Set up alerts — If your organization has monitoring configured, set critical event thresholds

See Also