Optiak Docs
Administration

Organization and Projects

How projects group applications and how you manage them.

An organization contains projects, and projects contain applications. Use this structure to group applications in the way that best suits your organization: by products, environments, departments, and countries, all while keeping application access and configuration manageable.

Required role

Organization AdminWorkspace AdminProject AdminApp Admin

Applies to

LLM requestsTool calls
Organization Admins and Workspace Admins manage projects. Organization Admins, Workspace Admins, and Project Admins can create applications; App Admins can configure them. See Members and Access for each role's permissions.

Why use it

Projects group applications that share an owner or purpose, such as a product, environment, or customer. Project-level access then applies to the applications in that project, so you can manage related workloads together. See Members and Access for role scopes.

How it works

An organization contains projects, and each project contains applications. Every application belongs to exactly one project. Each organization has a Default project, so every application has a project even when you have not created another.

Organization

One account for members, settings, projects, and applications.

Default project

Always included

A project ready to use in every organization.

  • Applications

    Each application belongs to one project.

Other projects

Create as needed

Group work by product, environment, or customer.

  • Applications

    Each application belongs to one project.

Projects

Use a project to keep applications with a shared purpose together. For example, you might separate development and production applications, or group applications by customer. Give the project a name, add an optional description so teammates know what belongs there, and choose a risk level: Unassigned, Low, Medium, or High. Projects also have a slug; you can edit it later, except for the Default project's fixed slug.

Use the Projects list to compare projects at a glance. The application count shows how many applications each project groups, and request activity helps you see which projects are handling traffic. Risk level and creation and update dates provide more context. Budget (for projects where it was set) shows how much the applications within a project are spending. Search, filter, or sort the list to find a project.

Open a project when you want to work with the applications it groups. Their status and request activity help you spot which ones are active or receiving traffic; creation and update dates help you find recent changes. Search or sort the list, filter by status. You can create an application from the project page. To delete a project, first delete all its applications. Project roles apply to every application in that project; see Members and Access for details.

Applications

Think of an application as one AI workload, such as a product assistant or a staging service. It belongs to one project, but its settings let you decide how that workload uses Optiak. For example, you can choose which models it can call, add available data and tools, and set application-specific guardrails. Organization policies can limit which options are available. See Data Governance for organization-wide restrictions, Models and Routing, Data Integrations, and Tools for application settings, and Members and Access for the roles that can change them.

The application's Overview shows the Dashboard for that application only.

When you need to understand one call, open the application's Requests tab. Each request has a trace showing the steps it went through. See Application Observability for how to use those traces to investigate failures, blocks, or delays.

Use Configuration to decide how the application behaves:

  • General: In Details & status, identify the application and choose its project or whether it is active. Budgets help you set spending limits for its traffic.
  • Capabilities: Choose the models it can call, configure Smart Router and the Context Engine, and set request defaults such as fallback models and the system prompt.
  • Data & tools: Enable the Data Integrations and Tools this application needs from the options made available by the organization.
  • Security: Set Guardrails to check application traffic against your safety policy.
  • Access: Manage the Application API keys your services use to call this application. Keys are specific to an application; see Authentication for key creation and revocation.

These settings shape how the Gateway handles this application's traffic. See the Gateway overview for how a request flows through Optiak, or Application Observability for more about metrics and traces.

Create an application in the project where it belongs. See Members and Access for role permissions.

To let a service call this application through the Gateway, create an Application API key in Configuration -> Credentials. Each key is tied to one application; see Authentication for setup and revocation.

Applications can be Active or Paused. A paused application rejects Gateway requests made with its API keys until you activate it again; pausing does not delete the application or its credentials.

Set it up

In the console, open Projects. Create a project with Create project, or select an existing project, including Default. From a project, choose Create application and enter the application details. You can change its settings later in Configuration; use Details & status to pause, activate, or delete it.

If you leave the application creation form before finishing, the console keeps your progress as a draft for up to 7 days and shows a reminder so you can resume where you left off.

For example, a company could keep an internal knowledge assistant in Default, put its live support and invoice assistants in Production, and keep their test versions in Development. Each application belongs to one project, so production traffic stays separate from development while the projects remain part of the same organization.

ACME Inc.

Where crazy ideas become real.

Default project

Always included

Use when an application does not need a separate project.

  • Internal knowledge assistant

    Answers employee questions.

Production project

Example

Groups customer-facing applications.

  • Support assistant

    Helps customers find answers.

  • Invoice assistant

    Extracts details from invoices.

Dev project

Example

Keeps test applications separate from live traffic.

  • Support assistant (staging)

    Tests before release.

  • Invoice assistant (staging)

    Tests before release.

Limits and behavior

  • You cannot delete the Default project. A project must have no applications before you can delete it; delete its applications first.
  • Pausing is reversible and preserves the application and its credentials, but requests using its API keys are rejected until it is active again.
  • Deleting an application is irreversible and stops its Gateway traffic. Plan to retire or replace services using its Application API keys before deleting it; see Authentication for key management.
  • Members and Access: role permissions and project-level access.
  • Authentication: Application API keys and organization connections.
  • Budgets: organization, project, application, and key spending limits.
Copyright © 2026