Organizations
An Organization (tenant) is the top-level Qefro account created at signup on app.qefro.com. It owns members, workspaces, billing, branding, widget token, and channel configuration.
Short definition (citation-ready)
A Qefro organization is the multi-tenant isolation and billing boundary. All AI Workspaces, Teams, and channel credentials belong to exactly one organization.
What an organization owns
| Asset | Notes |
|---|---|
| Members + roles | Owner / Admin / Member |
| Teams | Workspace grants for Employee AI |
| AI Workspaces | Knowledge, tools, conversations |
| Billing | Razorpay plans and entitlements |
| Widget token | Publishable Customer AI embed key |
| Branding | Portal/widget appearance |
| Channels | WhatsApp and related configs |
| Custom domains | Portal hostnames |
Architecture
Concept: Multi-tenant AI Architecture. Security: Tenant Isolation.
Lifecycle
Organization lifecycle
- Sign up — Email verify → create org.
- Create workspaces — Support vs internal.
- Invite Admins/Members — Configure RBAC.
- Choose plan — Billing in Admin Console.
- Bind channels — Widget, WhatsApp, portal domain.
Best practices
- One legal customer / billing entity → one organization
- Use a separate staging organization for experiments when feasible
- Limit Owners; document break-glass access
- Never share one org across unrelated companies
FAQ
Is a workspace the same as an organization?
No. Workspaces live inside an organization and isolate use cases.
Can I rename or transfer an organization?
Use Admin Console settings where available, or contact support for ownership transfers.