Solara operations
Commerce, marketplace, and financial oversight from persisted data.
Complete SMTP host, port, sender identity and password, then send a test message. → Open Email Settings
Business position
Commercial activity
Commercial activity
Not enough history yet.
Campaign readiness
Campaign dimensions · No event
No active event data is available.
Campaign Health
Active event performance
Customer and entry activity
Commercial contribution
Operational readiness
—
—
Safe 60-second polling · no environment variables, credentials, network addresses or secret paths exposed.
Platform portfolio
Tenant-scoped commerce, admission and settlement position.
| Organizer | Events | Tickets | GMV | Solara revenue | Payable | Check-in | Settlement | Action |
|---|
Organizer applications
Review verified applicants before any tenant is created.
Organizer plans
Admin-managed pricing and real platform capabilities. Historical assignments remain snapshotted.
Transactions
Bounded payment-level records, separate from customer orders.
| Transaction | Date | Event / Organizer | Order | Method | Amount | Customer fee | Gateway cost | Status |
|---|
Refunds
Refund actions and provider state remain distinct from orders.
| Refund | Date | Order | Customer | Event / Organizer | Amount | Status |
|---|
Users / Roles
Invite operators, apply least privilege, and deactivate access without deleting history.
| User | Role | Status | Activation | Last login | Created | Actions |
|---|
Hard delete is intentionally unavailable because user identities may be referenced by immutable audit and financial history.
Customer relationships
Normalized by email from completed purchases. Transactional customers are kept separate from marketing consent.
Public review and placement
Approval permits public sale. Placement independently controls Solara promotion.
| Event | Organizer | Visibility / status | Sales / capacity | Placement | Action |
|---|
Orders
Search, filter, and open the customer transaction record. Refund controls live in order detail.
| Order | Date | Customer | Organizer | Event | Qty | Charged | Status | Action |
|---|
Platform position
Manual payout register
No settlement batches match this view. Clear filters to see all batches.
Gateway readiness
Simulated payments remain active until a certified adapter is configured and tested.
Prepare sandbox provider configuration
Saving credentials encrypts them at rest. Values are never returned. A provider cannot accept payments until its dedicated adapter is installed and certified.
Email / SMTP
Passwords are write-only and encrypted with a dedicated key.