Organizations & Projects
Organizations
Section titled “Organizations”An organization is the top-level container for billing, membership, and subscription. Every
user belongs to one or more organizations. Organizations have a type, which determines which
portal surface(s) are available to them:
| Organization type | Portal | Purpose |
|---|---|---|
standard | app. only | The default — a customer building hotline and/or platform projects. |
partner | app. + partners. | A referral or reseller partner; see Partner guide. |
headless | app. + headless. | An integrator embedding Nairon in their own product; see Headless guide. |
An organization has exactly one type in v2 — an org cannot be both a partner and a headless integrator simultaneously (use a second organization if you need both).
A tenant organization (a customer of a partner, or an instance target under a headless
integrator) is a standard organization that carries a managingPartnerId or
managingHeadlessIntegratorId back-reference, which is how partners/integrators get access to
manage it without changing its own type.
Projects
Section titled “Projects”Projects live inside an organization and hold the actual work: flows, phone numbers, knowledge
bases, and agent profiles. A project has a type:
| Project type | What it is |
|---|---|
hotline (default) | A phone-answering (and/or web-embedded) voice agent project: flows, phone numbers, knowledge bases, call history/analytics. |
platform | An API-consumption project: no flows or phone numbers. Its surface is API keys, usage, and an invoice preview on platform.v2.nairon.xyz. |
Choosing platform as the project type is how you get access to the OpenAI-compatible
platform-api and the service-api control plane under
that project’s API keys — see the Developer guide.
Projects also carry a plan (free, starter, growth, pro, enterprise) which, among other
things, gates access to pro-flow nodes in the graph editor — see Flows.
Glossary
Section titled “Glossary”- Flow — a conversation design, either
simpleorgraphtype (see Flows). - Flow version — a saved snapshot of a flow’s configuration; one version is active at a time.
- Agent profile — the model/voice/language configuration a flow runs with.
- Knowledge base — a set of ingested documents/URLs an agent can query for answers.
- Phone number — a Nairon-provided, partner-provided, or externally-trunked number attached to a flow.
- API key — a
publishableorsecretproject-scoped credential (see API keys).