v4.2.0 Feature

Collaboration & Projects

Team workspaces with shared models, role-based access control, workgroups spanning multiple projects, and project-scoped conversations — built for organizations that need structured AI collaboration.

3 Member Roles
Owner / Editor / Viewer
4 Visibility Levels
Private to Public
Workgroups
Cross-Project Teams
Model + Agent Registry
Shared Resources

How It Fits Together

Users belong to projects, projects belong to workgroups, and models and agents flow through a visibility-controlled registry.

User owner / editor / viewer Project A Members: 5 (owner, editors, viewers) Enforced Model: llama3.2:70b Scoped Conversations Workgroup: R&D Project A Project B Project C Shared Resources Registry Models Agents Users join projects with role-based access — projects form workgroups — registries publish shared models and agents

Projects

A project is the fundamental unit of collaboration. It groups people, models, agents, and conversations under a single scope with enforced access control.

Create & Configure

Create projects with a name, description, and default model. Set tool restrictions, system prompt overrides, and knowledge base bindings. Every project gets its own isolated conversation history.

👥

Member Management

Invite users by email or API key. Each member has one of three roles: Owner (full control), Editor (use and configure), or Viewer (read-only access to conversations and results).

🔒

Enforced Models & Tools

Lock a project to specific models — members cannot switch to unapproved models. Restrict available tools to prevent unintended actions. Tool allowlists are inherited from the project configuration.

💬

Scoped Conversations

All conversations within a project are isolated from other projects. Search, export, and audit trails are scoped to the project boundary. Members see only their project's history.

# Create a new project curl -X POST http://controller:8880/api/v1/projects \ -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_KEY" \ -d '{ "name": "Drug Discovery Q2", "description": "Molecular docking and ADMET prediction pipeline", "enforced_model": "llama3.2:70b", "allowed_tools": ["WebSearch", "Read", "Grep", "ScienceQuery"], "knowledge_bases": ["pharma-kb", "chembl-data"], "system_prompt_override": "You are a pharmaceutical research assistant..." }'

Workgroups

Teams that span multiple projects, sharing resources across organizational boundaries.

Cross-Project Teams

A workgroup is a collection of projects that share a common purpose. Research departments, product teams, or client engagement groups can bundle their projects into a workgroup. Members of the workgroup gain access to all contained projects according to their workgroup role, simplifying permission management for large organizations.

Role inheritance: A workgroup admin automatically has owner access to all projects within the workgroup. Workgroup editors get editor access, and workgroup viewers get viewer access. Project-level overrides can elevate but never reduce inherited permissions.

Shared Resources

Workgroups can define shared model pools, knowledge bases, agent configurations, and system prompts that all contained projects inherit. This eliminates duplication and ensures consistency across related projects.

# Create a workgroup curl -X POST http://controller:8880/api/v1/workgroups \ -H "Content-Type: application/json" \ -d '{ "name": "R&D Division", "project_ids": ["proj-001", "proj-002"], "shared_models": ["llama3.2:70b", "codellama:34b"], "shared_knowledge_bases": ["internal-docs"] }'

Model Registry

Publish, discover, and control access to models across the organization with four visibility levels.

VisibilityScopeWho Can SeeUse Case
Private Single user Only the owner Personal fine-tunes, experiments in progress
Project Project members All members of the project Team-specific models, project-trained adapters
Workgroup Workgroup members All members across projects in the workgroup Department-wide models, shared fine-tunes
Public Organization-wide Everyone in the cluster Approved production models, base models

Model Badges

Models in the registry carry metadata badges indicating their status: verified for models that passed validation, experimental for models under evaluation, fine-tuned for LoRA/QLoRA adapted models, and quantized for models with reduced precision.

Version Tracking

Every model entry tracks version history with SHA-256 checksums, training metadata, parent model lineage, and performance benchmarks. Roll back to any previous version or compare performance across versions directly from the registry.

Agent Registry

The same four-tier visibility model applied to custom agents — share agent configurations, tool sets, and system prompts across your organization.

Publish Agents

Register custom agents with their tool definitions, system prompts, and example interactions. Control who can discover and use each agent through visibility levels.

🔍

Discover & Fork

Browse available agents, review their capabilities, and fork them into your own project with customizations. Forked agents maintain a link to the original for update tracking.

📊

Usage Analytics

Track agent usage across projects: invocation count, average response quality, tool call patterns, and error rates. Identify top-performing agents and retire underperforming ones.

Agent Builder integration: Agents created via the Agent Builder or Agent Generator are automatically registered in the agent registry with private visibility. Promote them to broader visibility levels once validated.

API Endpoints

Full REST API for managing projects, workgroups, and registries.

Projects

EndpointMethodDescription
/api/v1/projectsGET / POSTList / create projects
/api/v1/projects/{id}GET / PUT / DELETEGet / update / delete project
/api/v1/projects/{id}/membersGET / POSTList / add members
/api/v1/projects/{id}/members/{uid}PUT / DELETEUpdate role / remove member
/api/v1/projects/{id}/conversationsGETList project-scoped conversations
/api/v1/projects/{id}/configGET / PUTGet / update project settings

Workgroups

EndpointMethodDescription
/api/v1/workgroupsGET / POSTList / create workgroups
/api/v1/workgroups/{id}GET / PUT / DELETEGet / update / delete workgroup
/api/v1/workgroups/{id}/projectsGET / POSTList / add projects to workgroup
/api/v1/workgroups/{id}/projects/{pid}DELETERemove project from workgroup
/api/v1/workgroups/{id}/membersGET / POSTList / add workgroup members

Model Registry

EndpointMethodDescription
/api/v1/model-registryGETList models (filtered by caller visibility)
/api/v1/model-registryPOSTRegister a model
/api/v1/model-registry/{id}GET / PUT / DELETEGet / update / remove model entry
/api/v1/model-registry/{id}/visibilityPUTChange model visibility level
/api/v1/model-registry/{id}/versionsGETList model versions

Agent Registry

EndpointMethodDescription
/api/v1/agent-registryGETList agents (filtered by caller visibility)
/api/v1/agent-registryPOSTRegister an agent
/api/v1/agent-registry/{id}GET / PUT / DELETEGet / update / remove agent entry
/api/v1/agent-registry/{id}/forkPOSTFork agent into target project
/api/v1/agent-registry/{id}/statsGETUsage analytics for agent

License Tiers

Collaboration feature availability by license level.

FeatureFreeStandardProfessionalEnterprise
Projects 1 10 50 Unlimited
Members per project 2 10 50 Unlimited
Workgroups 3 20 Unlimited
Model registry
Agent registry
Enforced models/tools
Cross-workgroup sharing
Audit logs