Tenant management
Tenant management is the core of the platform admin console: the lifecycle of every organization on ActionConnect, from creation to teardown.
WARNING
ActionConnect staff only.
Listing and searching tenants
The console lists all organizations with their provisioning status and health. Search and filter by name, slug (subdomain), status, or plan to find a specific tenant quickly.
A tenant's detail view shows its provisioned resources, plan and usage, and its audit trail — a per-tenant record of significant events.
Tenant status lifecycle
An organization moves through these states:
| Status | Meaning |
|---|---|
| provisioning | Resources are being created; not yet usable. |
| active | Fully provisioned and in use. |
| suspended | Temporarily disabled (e.g. non-payment); data retained. |
| deprovisioning | Resources are being torn down. |
| deleted | Fully de-provisioned. |
| failed | Provisioning failed and needs attention. |
Creating a tenant
A tenant can be created from the marketing-site signup or directly from the console. Either way, ActionConnect writes a registry row and enqueues a provisioning job so the request returns fast while work happens in the background.
The provisioning lifecycle
Provisioning runs as an idempotent, retryable state machine. Each step is guarded so re-running never creates duplicate resources:
- Registry — record the tenant.
- Create database — create the tenant's isolated database.
- Migrate — run all schema migrations.
- Storage — assign per-tenant file storage.
- Routing — set up subdomain routing.
- Email — configure the inbound support address.
- Seed — seed defaults: statuses, priorities, roles and permissions, an admin user, email templates, settings (branding, business hours), a starter knowledge-base category, a sample project with default views, and a starter automation and form template.
- Activate — publish routing and set status to active.
If a step fails, the job is retryable and resumes from the first incomplete step — no duplicate resources are created. Every step transition is recorded for audit.
Suspending and resuming
Suspend an organization to disable access while retaining its data (for example during a billing dispute). Resume restores access. Both actions are audited.
De-provisioning (offboarding / delete)
De-provisioning runs the teardown in reverse: revoke routing, delete stored files, delete the tenant's database, and mark the tenant deleted. Like provisioning, it is step-tracked and idempotent (delete-if-exists), so it can be safely retried.
IMPORTANT
De-provisioning permanently removes a tenant's resources. Confirm the target tenant carefully — the action is fully audited.
Health and troubleshooting
For a failed tenant, open its provisioning history to see which step failed and why, then retry the job. Because steps are idempotent, retrying is safe.