Managing Engineering Teams on SkillVault

01 Creating & Setting Up Team Vaults

A Team Vault provides a shared space for playbooks, secrets, service accounts, and cognitive memories. Personal scratchpads and individual developer notes stay private, while verified standards and team playbooks are shared across the company.

How to Create a Team Vault

1. Go to /dashboard/orgs in your SkillVault sidebar.
2. Click Create Organization Vault.
3. Choose an Organization Name (e.g. Acme Engineering) and a URL Slug (e.g. acme-corp). Your team vault address will be https://app.skillvault.dev/v/acme-corp.
4. Choose your seat allocation. The Team tier starts at €14.95/seat/month with a 100,000 shared memory pool, unlimited team skills, and team-wide secret proxying.

Inviting Team Members

In your organization dashboard (/dashboard/orgs/acme-corp), go to the Team Members card:

• Enter the teammate's work email address.
• Assign their role (Admin, Skill Author, or Member).
• Click Send Invitation. Teammates receive an activation link to join your organization vault immediately.

02 Roles & Permissions (RBAC)

SkillVault enforces Role-Based Access Control so team members get the playbooks and memories they need without risking sensitive organization settings.

03 Managing Team Skills

Team skills standardize internal architecture patterns, brand guidelines, deployment checklists, and review playbooks across every assistant on your team.

Publishing Skills to the Team Vault

You can publish skills to your organization in two ways:

• From the Web Dashboard: In /dashboard/orgs/acme-corp, locate the Publish / Link Skill to Team Vault form. Select any skill from your personal library to link it to the organization.
• From the CLI Terminal: Any user with the Admin or Skill Author role can push directly from their local terminal:
  TERMINAL · CLI TEAM SKILL PUBLISH

  skillvault push ./internal-api-guidelines --org acme-corp

Per-Member Skill Access Overrides

For contractors or specialized squads working on sensitive services (e.g. db-migration-tools or production-deploy), Admins can grant or restrict access on a per-member basis. In your member list, click Manage Access to toggle specific skill permissions.

04 Team Secrets & Secure Credential Proxying

Never ask engineers or contractors to paste API keys, database credentials, or client secrets into chat windows or unencrypted local files.

Setting Organization Secrets

1. Go to /dashboard/orgs/acme-corp and locate the Organization Secrets card.
2. Add your keys (such as INTERNAL_STAGING_KEY, CLIENT_API_KEY, or JIRA_API_TOKEN).
3. SkillVault encrypts your secrets using hardware-isolated AES-256 keys in the EU.

05 MemVault: Team Cognitive Memory Governance

Shared memory is the core superpower of SkillVault Teams. When an engineer fixes a tricky bug or documents a client policy, every teammate's AI agent benefits immediately.

Curating "Org Standards" (Golden Directives)

In standard working memory, temporary debugging notes naturally fade over time. However, core company rules and architecture standards must never fade.

• Go to /dashboard/memories and select your team vault ([ 🏢 Acme Corp ]).
• Find or ingest an important rule (e.g., "Client proposals must never exceed a 10% annual discount cap" or "All public endpoints require JWT middleware before touching the database").
• Click Pin Standard.
• This locks the memory at strength 1.0, exempts it from Ebbinghaus decay, and automatically marks it with the 📌 Org Standard badge.
• Result: That directive is immediately injected into [ASKER CONTEXT] for every engineer and AI agent on your team.

Contributor Auditing & Emergency Redaction

• Audit Attribution: Every team memory displays an author badge (e.g. by @sarah or by @ci-bot), letting you trace where decisions originated.
• Emergency Redaction (🗑️ Forget): If an engineer accidentally commits a test secret or deprecated specification, an Org Admin can click Forget. MemVault instantly purges the item from all semantic vectors, knowledge graph links, and team prompt builders.

06 Compliance & Automated Retention Policies

For organizations operating under SOC2, ISO 27001, HIPAA, or strict client confidentiality agreements, MemVault includes built-in compliance guardrails in /dashboard/orgs/acme-corp.

Repository & Project Blacklists

Prevent sensitive codebases from ever being captured in memory:

• Blocked Repositories: Enter comma-separated repository names (e.g. pci-vault, customer-kyc-service). If a developer commits code in these repos, the git hook will automatically reject memory ingestion.
• Blocked Projects: Enter confidential project tags to reject manual or agent-driven memory writes.

Compliance Auto-Purge Windows

Configure automated data destruction to satisfy compliance policies:

• 30 Days: Strict SOC2 and financial audit compliance.
• 60 or 90 Days: Recommended for fast-moving engineering teams.
• Memories older than the threshold are automatically purged by SkillVault's background retention worker.

07 CI/CD Automation with Service Accounts

Automate team memory and skill synchronization by connecting SkillVault to GitHub Actions, GitLab CI, or internal deployment pipelines.

Creating a Service Account

1. In /dashboard/orgs/acme-corp, locate the Service Accounts card.
2. Click Create Service Account (e.g. github-actions-bot).
3. Copy the issued token (sv_svc_...). Store it as a repository secret (SKILLVAULT_TOKEN) in your CI pipeline.

GitHub Actions Workflow Example

Automatically ingest release milestones whenever code is merged into main: