Manage

Manage is where the platform’s boundary model and operator controls come together.

Use it when the question is:

• which organization, workspace, or project am I actually working in?
• who can access this area?
• where do settings, chat models, secrets, and credits live?

Note

This is the context and control layer around the product surfaces. Evaluations, analytics, and training jobs execute elsewhere.

Context chain

Organization
  -> Workspace
     -> Project
        -> Workflow surfaces

Layer or control surface	Primary role
Organization	top-level ownership, membership, and billing boundary
Workspace	access boundary and collaboration area
Project	grouping context for runs, traces, evaluations, and related work
Settings	org-facing configuration pages in the app
Chat Models	user-scoped assistant model preferences
Secrets	user-owned credentials injected into compute
Credits	SaaS usage and billing controls

Common workflows

• confirm the correct org, workspace, and project before launching work
• update access boundaries and sharing rules
• manage provider credentials, model preferences, and billing controls
• answer “why can this person see this?” or “why did this workload run here?”

What agents should assume

• organization, workspace, and project materially change what artifacts and runs are visible
• projects are context, not permission boundaries
• settings is a shell that groups several operator surfaces rather than one API object

For the individual control surfaces, use Settings, Organizations, Workspaces, Projects, Secrets, Chat models, and Credits.