# Platform Fundamentals The **InteractiveAI Platform** organizes resources through a **hierarchical structure** designed for enterprise teams. Understanding this structure is essential for configuring access control, separating environments, and managing resources at scale. ## Architecture Overview The platform follows a two-tier hierarchy that mirrors how organizations actually operate. At the outermost level sits the **Organization**, which contains all billing, membership, and administrative settings. Within the organization, multiple **Projects** exist as isolated workspaces, each containing its own traces, prompts, datasets, secrets, and API keys. This hierarchy serves a practical purpose: it allows enterprise teams to maintain strict isolation where needed while sharing administrative overhead where appropriate. A single organization can house dozens of projects without duplicating user management or billing configuration, yet each project remains completely independent in terms of data and access credentials. *** ## Organizations An **Organization** represents the top-level container in InteractiveAI. It typically corresponds to a company or business unit and establishes the boundary for billing, membership, and administrative control. Every resource you create, every team member you invite, and every project you manage exists within the context of an organization. When you sign into the platform, you land at the organization level. ### What You Will Find Inside an Organization Five sections govern how your organization functions, however, only Projects and Team will be visible for everyone while Usage, Billing and Settings are reserved for those with Owner permits:
#### Projects Projects displays all workspaces within your organization as cards showing their names and creation dates. This view serves as your **launching point** into actual work. From here you create new projects, access existing ones, and get a birds-eye view of everything your organization contains. #### Team Team is where you manage who has access to your organization and what they can do. Every member appears in a table showing their name, email, role, invitation date, and who invited them. You can modify roles directly from this view and invite new members using the button in the top right corner. The platform implements **role-based access** control with four levels: * **Owners** have complete administrative control including billing. * **Admins** handle operational management without billing access. * **Members** create and edit resources but cannot modify protected configurations. * **Viewers** have read-only access to everything. #### Usage Usage provides visibility into **resource consumption** against your plan limits. The screen displays your **Current Plan** information alongside metrics for users, projects, datasets, agents, evaluators, and prompts, the **LLM Token Consumption** with its Token Breakdown and the **Storage Usage** alongside metrics for projects, traces, datasets, data volume, users, and token consumption. Each metric help you understand costs and usage before they become surprises. From here you can access directly to the **Upgrade Plan** section where you can unlock even more possibilities by upgrading your plan. #### Billing Billing handles the financial side of your subscription. Here you see your **current plan** and monthly cost, manage payment methods, and access your **complete invoice history**. The interface shows your payment card on file and provides options to upgrade your plan or edit payment details. #### Settings Settings covers **organization-level configuration**. The General tab lets you modify your organization's name and type, while the Danger Zone at the bottom contains the option to permanently delete your organization, an irreversible action that removes all projects, traces, prompts, datasets, and associated data. ### **Key Characteristics** A user account can belong to multiple organizations, which proves useful for consultants working with several clients, agencies managing multiple brands, or employees working across subsidiaries. When you switch between organizations using the dropdown in the top navigation, the available projects and resources change accordingly because each organization maintains **complete isolation** from others. Organization administrators control membership and permissions for all users within their organization. However, API keys and secrets are scoped to **individual projects** rather than to the organization itself. This means a developer can have access to your organization but still need project-specific credentials. *** ## Projects A **Project** serves as the primary unit of resource isolation within InteractiveAI. All operational data belongs to a single project: traces, prompts, datasets, secrets, evaluators, and dashboards. Nothing crosses project boundaries, which means you can grant a contractor access to a development project without any risk of them seeing production data in a different project. ### What You Will Find Inside a Project When you click into a project from the organization view, the interface transforms entirely. At the top of the sidebar sits the [Dashboard](https://docs.interactive.ai/dashboard), your **operational command center** that provides a real-time snapshot of project health. Here you see total counts for traces, sessions, observations, and scores alongside performance metrics like average latency and average session duration. The cost section breaks down model cost, model cost per trace and per user giving you immediate visibility into spending.
Below the Dashboard, the sidebar reorganizes into all the functional categories that reflect the platform's core workflow: #### Build Build houses the components that define **how your AI system behaves**. Context provides a version-controlled repository for managing everything that drives your agent's behavior, including policies, routines, glossaries, macros, agents, and prompts, independently of your application code. Playground offers an interactive environment for testing context with different models and parameters before committing changes. #### Connect Connect manages **external integrations** and sensitive credentials for your project. Secrets Manager provides secure storage for API keys, tokens, and other credentials that your workflows require while LLMs displays the catalog of available models through the InteractiveAI Router, showing providers, capabilities, context windows, and pricing. Tools functionality and Knowledge Base are coming soon. #### Deploy Deploy handles infrastructure management for deploying and monitoring containerized services within your project. The Deploy page provides a step-by-step tutorial that guides you through the complete deployment lifecycle using the InteractiveAI CLI (`iai`), from installation through infrastructure-as-code synchronization. Monitoring displays real-time operational dashboards for your deployed services, including request volume, status code distribution, response time percentiles (p50, p95, p99), and CPU and memory usage with per-service resource allocation tables. You can filter by specific workloads and adjust the time window to focus on the period that matters. #### Govern Govern provides complete visibility into your **AI system's behavior.** This section contains Traces, which capture end-to-end records of individual AI operations; Sessions, which group related traces into conversations or workflows; and Scores, which attach quality measurements to your activity. Observations exist as the granular building blocks within traces, recording each discrete step like model calls, tool invocations, or retrieval operations. #### Improve Improve contains the tools for systematically enhancing your **AI system's quality**. Datasets let you build collections of test cases to evaluate your application against consistent inputs. Annotations capture expert judgment through manual review, establishing ground truth for your evaluation infrastructure. Evaluators automate quality assessment using LLM-as-a-Judge, where a secondary model grades outputs against predefined criteria. #### Report Report surfaces insights about your **platform usage and user behavior.** Reporting delivers pre-configured visualizations of performance metrics, quality trends, and cost data designed for production AI monitoring. User Tracking connects LLM activity to individual end users, enabling you to debug issues, analyze consumption patterns, and understand how different segments interact with your system. ### Structuring Your Projects Teams commonly structure their projects according to one of two patterns, each with distinct advantages. * **Product-based** structures create separate projects for distinct applications, such as `customer-support-bot`, `internal-search`, and `document-processor`. This works well when different products have different teams, different release cycles, or genuinely distinct operational characteristics. Each product gets its own complete workspace without interference from others. * **Team-based** structures create separate projects for autonomous teams, such as `team-alpha` and `team-beta`. This pattern suits organizations where teams operate independently with their own tooling choices and deployment schedules. Each team owns their project entirely. Some teams choose to create separate projects for **production** and **non-production** workloads, such as `myapp-production` and `myapp-dev`. This provides hard isolation between environments but requires managing multiple sets of API keys. Alternatively, you can use a single project and **distinguish deployment stages** using the environment attribute on traces, which allows filtering by environment in dashboards and trace views without the overhead of multiple projects. {% hint style="warning" %} Resources cannot be transferred between projects after creation. Consider your project structure carefully before deploying to production, as restructuring later requires re-ingesting historical data. A project rename is possible, but moving traces or prompts from one project to another is not. {% endhint %}