Plans & billing

The platform admin console is where ActionConnect staff manage plans, subscriptions, and seats for each organization. Billing is staff-managed — there is no self-service payment gateway or card capture.

WARNING

ActionConnect staff only.

Plans

A plan defines what an organization gets:

• Limits — such as seats, projects, and storage.
• Features — feature flags that turn capabilities on or off per plan.

Plans are defined centrally in the control plane and assigned to tenants.

Subscriptions and seats

Each organization has a subscription that links it to a plan and records its state:

Subscription status	Meaning
trialing	In a trial period.
active	Paid/approved and in good standing.
past_due	Payment overdue.
canceled	Subscription ended.

Staff set the plan, the number of seats, and relevant dates, and can add notes. Because billing is staff-managed ("we bill you directly — no credit card"), there is no online checkout; staff record the commercial arrangement here.

Trials, contracts & e-signatures

New organizations are provisioned onto a 90-day trial (trialing). Converting a trial to a paid plan is contract-driven — there is no online checkout. The flow is:

1. Issue a contract. From the tenant's detail view, staff create a contract (title, agreement body, optional plan, term, and amount) with one or more signers. The agreement body is snapshotted and hashed so a signature is bound to the exact content signed. Each signer gets a tokenized signing link; only the hash of the token is stored.
2. Tenant signs online. Signers open the link on the public signing page, consent (ESIGN/UETA-style), and sign typed or drawn. Every created → sent → viewed → signed → declined → completed transition is recorded as an immutable event with IP and user-agent, forming a defensible audit trail. When the last signer signs, the contract is signed.
3. Activate the subscription. Once the contract is signed, staff convert the trial to a paid subscription (set plan, seats, notes). This is the point at which the organization moves from trialing to active.

NOTE

Contracts and signatures live entirely in the control plane; no payment card is captured at any step. The signing page is public (token-gated) so signers do not need an ActionConnect account.

Feature-flag overrides

Beyond plan-level features, staff can apply feature-flag overrides to an individual tenant — useful for enabling an early-access capability or a custom arrangement without changing the whole plan.

Changing a plan

1. Open the tenant's detail view.
2. Select a new plan or adjust seats.
3. Update the subscription status and any notes.

Limits and feature flags take effect for that organization. All changes are audited — see Audit & impersonation.

A note on future payment integration

The system reserves a seam for a future payment provider, so an online billing gateway could be added later without reworking the plan and subscription model. Until then, billing remains a staff-managed process.

Tips

• Keep seat counts aligned with what each organization actually uses.
• Use feature-flag overrides sparingly and document the reason in notes.
• Review past_due subscriptions and coordinate with tenant suspension where appropriate — see Tenant management.