Projects & Workloads
AVAILABLEA Project is an isolated workspace within an Organization dedicated to a specific application, microservice, or AI initiative.
Rendering diagram...
graph TD
Project["Project: Customer Support AI"]
Project --> Env1["Test Environment"]
Project --> Env2["Production Environment"]
Project --> CM["Customer Members Directory (external_user_id)"]
Project --> Access["ProjectAccessAssignment (Portal Users)"]
Project --> ST["Project Service Tokens"]
Project --> Agents["Autonomous Agents"]
Project --> Tools["Registered Tools & MCP Servers"]
Why Use Projects? #
Projects enforce strict resource and credential isolation between different workloads:
- Credential Segregation: API Keys and Service Tokens created in Project A cannot access models or resources in Project B.
- Customer Member Directory: End-user identities (
external_user_id) and individual budgets are strictly scoped per project. - Portal User Assignment: Team members are granted access to specific projects through ProjectAccessAssignment.
- Autonomous Agents: Agents, prompt templates, skills, and MCP tools are scoped to the project.
- Budget Allocation: Assign specific monthly budgets to individual projects to prevent runaway costs from affecting other teams.
Project Structure #
Every Project contains:
- Environments: Two-tier isolation stages (
TestandProduction). - Customer Members: Workload and end-user directory with individual spending limits.
- Portal User Access: Assigned developers and operators via
ProjectAccessAssignment. - Service Tokens: Machine-to-machine credentials scoped to the project and environment.
- Routing Policies: Custom fallback cascades and latency/cost optimization rules.
- Agent Ecosystem: Autonomous agents, tools, skills, and MCP server integrations.
Managing in the Developer Portal #
- Navigate to the Projects list at https://console.naagmani.com/projects.
- Click + Create Project to initialize a new workspace.
- Select any project to view its dedicated dashboard, members, service tokens, agents, and analytics.
Next Steps #
- Understand environment boundaries: Environments & Isolation
- Manage project customer members: Customer Members
- Assign team members: Portal Users vs Customer Members
- Issue project credentials: Project Service Tokens