Platform
Kixo is organized around teams, projects, apps, members, credits, and scoped SDK keys. This page explains the customer-facing model.
Teams and projects
A team represents your company. A project represents one product or business unit inside that company. Most work in Kixo happens inside a project: dashboards, events, audience data, campaigns, apps, and SDK keys.
Roles
| Role | Best for | Typical access |
|---|---|---|
| Owner | Company lead or finance owner | Team settings, billing, members, projects |
| Admin | Project lead or operations owner | Project settings, SDK keys, apps, campaigns, members |
| Member | Marketer, product manager, analyst | Dashboards, chat, segments, campaigns |
| Viewer | Read-only stakeholder | Dashboards and analytics |
| Guest Viewer | Outside collaborator (agency, contractor) | Read-only, on the specific projects they are invited to |
| Guest Editor | Outside collaborator who authors content | Author dashboards and segments on invited projects; still cannot manage campaigns, pushes, workflows, domains, billing, or team settings |
Guest Viewer and Guest Editor are for people outside your company. Unlike Members and Viewers, guests see only the projects they are explicitly added to — there is no team-wide fallback — and they do not count against your billing seats. Guest Editor can create and edit content on those projects but remains capped below a full Admin: sensitive actions (campaigns, pushes, workflows, domains, billing, member management) stay server-side blocked even if a control appears in the UI.
Billing
Kixo separates team-level billing from project-level usage so finance and project operators can reason about different costs.
Team billing
Team billing covers your company account, plan, payment method, seats, and AI credit wallet. Credits are the customer-facing unit for Kixo Chat and other model-powered work.
Project billing
Project billing shows usage tied to a specific product: SDK event volume, audience size, campaigns, and project-specific overages when they apply.
SDK keys
Each project has SDK keys for event ingestion. A Project ID identifies the project, and the SDK API key authorizes client SDK traffic for that project.
- Project ID (
kx_proj_...) -- project identifier used by the SDK - SDK API key (
kx_key_...) -- scoped ingestion credential used by web and mobile apps
SDK keys cannot open dashboards, manage billing, send campaigns, or access team settings. If an SDK key must be replaced, contact Kixo support; customer self-service key rotation is not available today.
Apps and approval
Kixo auto-discovers apps from SDK traffic, such as a web domain, iOS bundle identifier, or Android package name. The first app for a platform can be accepted automatically during setup. Later app identifiers should be reviewed by your team before Kixo accepts their traffic.
If an unknown app appears, review it in the dashboard. Approve it when it belongs to your product, or block and report it if it looks like spam, fraud, or a leaked setup snippet.