The Three-Tier Role Model
Welcome to AgentLane, a B2B2C AI-agent-as-a-service platform. AgentLane provides the infrastructure for marketing and automation agencies (Partners) to resell AI-driven workflows to their own end-customers (Clients), while AgentLane staff (Admins) run the platform underneath both of them.
AgentLane operates on a three-tier role system, each with its own distinct area of the Portal. A user’s Role (ADMIN, PARTNER, or CLIENT) is fixed at the platform level and determines which of these three areas they can even reach — there’s no toggling between them.
1. Platform Staff (ADMIN)
Users with the ADMIN role are internal AgentLane staff. They manage the entire platform across all partners from the /admin/* routes.
| Area | What it covers |
|---|---|
| Partners | Every agency account, its plan tier, billing mode, and integration status |
| Plans | The pricing tiers shown on the signup stepper and marketing pricing page |
| Billing | Cross-partner MRR, active agents, and raw Stripe event log |
| Agent requests | Approve/reject partner requests for new client agent instances |
| Workflows | Every workflow configured across all partners |
| Users | Every user account on the platform, with the ability to change PARTNER/CLIENT roles |
| Audit log | Immutable ledger of every significant mutation platform-wide |
| Support | Escalated client chat conversations that need a human reply |
| Deletion requests | Partner/client self-service account deletion requests, subject to a 30-day grace period |
ADMIN accounts are not self-service — they’re granted only via seed data or direct database access, never reassignable from the Users table.
See the full route reference at Admin Panel, and the procedural walkthrough at Provision a partner.
2. Agency Partners (PARTNER)
A Partner is an agency selling AI agents. This is the primary user of the platform, working from the /dashboard/* routes.
- Onboard Clients and configure agent workflows per-client.
- Manage client billing/usage and monitor execution logs across their entire portfolio.
- Manage their own subscription, seats, team, and integrations.
Within the PARTNER role there’s a second, agency-scoped permission level — see Team permissions within a Partner for the admin/moderator distinction that controls what a given team member can actually change.
See the full route reference at Partner Dashboard, and the end-to-end procedural walkthrough at Deploy your first agent.
3. End Clients (CLIENT)
A Client is the end-business (e.g. a dental clinic or plumbing service) that actually uses the AI agent, working from the /client/* routes.
- View their specific agent’s conversations and take over from the AI when needed.
- Maintain their business profile (hours, services, contact links) that feeds the AI prompt.
- Manage their own AI/integration credentials and view usage.
Clients never see workflow logic, executions, or other clients’ data — the Client view is intentionally the smallest surface in the product.
See the full route reference at Client Portal, and how a client gets there in the first place at Invite a client to their portal.