What the central Admin Module is, how the connector works, and when you need it.

The Admin Module is a separate, central dashboard that manages every one of your plugin deployments from one place — users, licenses, plans, and stats across all products. Each Customer Portal (this app) connects to it through the connector.

The connector is optional. A Customer Portal runs perfectly standalone. Connect it when you want central, cross-plugin management.

Architecture

        ┌─────────────────────────────┐
        │      Admin Module           │   central console (all plugins)
        │   (one, run by you)         │
        └──────────────┬──────────────┘
                       │  outbound, authenticated calls
                       │  POST {portal}/connector/*
        ┌──────────────▼──────────────┐
        │   Customer Portal (this)    │   one per plugin
        │   /connector/* surface      │
        └─────────────────────────────┘

The Admin Module is always the caller. This deployment exposes the /connector/* surface and responds. Every request is authenticated with a shared service token (and, in the hardened model, an HMAC signature).

What the connector can do

The connector contract covers central management operations:

Area	Operations
Identity	`ping` — handshake + confirm which plugin this is
Stats	`stats.summary` — totals for the central dashboard
Users	`user.list`, `user.get`, `user.suspend`, `user.unsuspend`
Licenses	`license.list`, `license.revoke`, `license.activate`
Plans	push updated plan definitions to this deployment

The connector is delivered in phases. ping is live; several management operations are defined in the contract but return "not implemented yet" until the connector phase is completed on your deployment. The handshake and security model below are ready to wire up today.

The connector surface

All connector calls are POST requests under /connector on the API app:

Endpoint	Purpose	Status
`POST /connector/ping`	Liveness + identity handshake	Live
`POST /connector/stats`	Deployment stats	Reserved
`POST /connector/users/suspend`	Suspend a user	Reserved
`POST /connector/plans/sync`	Push plan definitions	Reserved

When the connector acts, it's recorded in the audit log as the platform actor, so every central action is attributable.

Admin Portal Overview

Architecture

What the connector can do

The connector surface

Next

Connect a Plugin

Security Model

Events Reference

On this page