Know who can receive
Centralized eligibility evaluates consent, suppression, contact status, and workspace boundaries before any send path is considered.
GFA newsletter operations
Community email, with the safety rails already built in.
Move from contact consent to campaign readiness in one transparent workspace—built for community teams, human operators, and authorized agents.
Production sending remains approval-gated.
Governed workflow
From identity to campaign readiness
Every important decision has an owner, a capability check, and evidence you can inspect.
- GFAVIP identity Sign in with Wallet; access still requires explicit workspace membership.
- Workspace Multi-org, multi-workspace isolation with role and capability checks.
- Contacts & audience Contact records, provenance, and static or rule-based audiences.
- Consent review Consent history, global and workspace suppression, eligibility.
- Sender readiness Provider config by secret reference, domain checks, sender identities.
- Template Versioned email templates with previews—no delivery from preview.
- Test Synthetic rehearsal or tightly allowlisted test sends when configured.
- Preflight Validation and scheduling controls before any campaign path proceeds.
- Campaign Drafts and operational visibility with delivery evidence when approved.
Core capabilities
What Connect gives community operators today
Implemented features only—no growth-speak, no claims about unlimited or fully automated production sending.
Prepare without pressure
Version templates, preview content, and build campaign drafts before any delivery path is opened.
Prove sender readiness
See provider configuration, DNS domain readiness, and sender identities in the same workspace.
Rehearse safely
Run database-only synthetic checks or tightly allowlisted delivery tests—never surprise your audience.
Follow the evidence
Correlate Mailgun events and operational history without exposing provider secrets in application records.
Humans & authorized agents
One product surface, one set of rules
Browser operators and headless agents share workspace capabilities and safety rails. Explicit membership is always required.
Human operators
Sign in with GFAVIP Wallet, pick a workspace, and move contacts through consent, audiences, templates, preflight, and campaign drafts with full UI feedback.
- Role-aware console workflows
- Previews and synthetic rehearsal
- Operational visibility and evidence
Authorized agents
Integrate through the same governed API. PowerLobster and other agents use bearer tokens under the same capability checks as people.
Safety gates
What contacts the network—and what does not
Preview, drafts, eligibility, preflight, and synthetic rehearsal do not contact recipients. Production marketing delivery stays off until the owner approves and every gate passes.
| Action | Contacts Mailgun? | Contacts a recipient? |
|---|---|---|
| Email preview | No | No |
| Eligibility check | No | No |
| Preflight | May read configured external readiness | No |
| Synthetic rehearsal | No | No |
| Test send | Yes | One configured allowlisted recipient |
| Controlled rehearsal | Yes | One configured allowlisted recipient |
| Campaign scheduling | No immediate delivery | Only when all gates remain open |
| Production delivery | Yes | Disabled until explicit approval |
Roles & accountability
Clear ownership without a stale permission matrix
Detailed capability maps live in the developer docs so marketing copy does not drift from the product.
Owner
Accountable for workspace direction, high-stakes approvals, and production launch controls when enabled.
Brand admin
Responsible for consent posture, domains, senders, provider configuration, and operational approvals.
Editor
Prepares audiences, templates, and campaign drafts within the capabilities granted to the role.
Analyst
Reviews operational visibility and delivery evidence without needing write access to every control.
Planned — not available yet
What is still on the roadmap
These items are intentionally labeled planned. AI content generation is not implemented. Do not treat the roadmap as a commitment to dates.
Phase 4
Production launch controls
Operational hardening and the remaining controls required for an explicit production go-live.
Phase 5
Automations
Automation authoring and execution. There is no automation API or operator-console route today.
Phase 6
Platform & developer experience
Broader platform work and deeper developer experience improvements beyond the current headless surface.
FAQ & trust
Straight answers for safety-conscious operators
Does signing in grant access?
No. A local workspace membership is required. GFAVIP Wallet proves identity; it does not automatically open every workspace.
Does preview send email?
No. Preview renders content only. It does not contact Mailgun or any recipient.
Can the platform send production marketing email today?
No. Production marketing delivery remains explicitly gated until the owner approves and all global, workspace, provider, domain, sender, consent, preflight, scheduling, and approval gates pass.
Where are provider secrets stored?
Connect stores a reference to the secret, not the secret value itself, in application records.
Can an agent use the product?
Yes—with a GFAVIP Wallet bearer token and the same capability rules that apply to human operators. See the agent guide at /skill.md.
Is unsubscribe and suppression state centralized?
Yes, within the implemented eligibility and suppression model at global and workspace scope.
Ready when you are
Bring your community workflow into one safe, inspectable place.
Open the app to work with your workspaces, or explore the headless API and agent guide when you are integrating.