How Terumbu.eco connects funding, fieldwork, learning, and verified impact.

1. 1Visitor reviews a published campaign with partner verification, progress, field activity, and impact targets.
2. 2Supporter chooses a donation or ecosystem sponsorship intent and completes checkout with contact details and amount.
3. 3Payment state is recorded through the transaction layer, then paid or reconciled records update campaign totals.
4. 4Receipts and email logs are created for successful donations.
5. 5Signed-in users see donations, sponsored ecosystems, and related milestones in the dashboard and Impact Passport.

Public campaign totals, donor history, receipts, and passport milestones stay connected to the same contribution.

1. 1Traveler reviews the expedition region, itinerary, impact allocation, departure options, preparation notes, and availability.
2. 2Checkout stores contact details, participant names, selected departure, total amount, and payment state.
3. 3Confirmed bookings increase seats booked for the departure and create participant records.
4. 4Confirmation email logs are queued so operational teams can track communication side effects.
5. 5The user expedition dashboard lists upcoming and historical field activity.

The public trip catalog and private user booking history remain consistent after checkout and refresh.

1. 1Learner searches or filters Academy courses and opens a course detail page.
2. 2Enrollment is created once and reused on repeat visits.
3. 3Lesson progress, assessment attempts, scores, and completion status are stored per user.
4. 4A passing final assessment issues a certificate with a certificate number and public slug.
5. 5Certificates can become Impact Passport items when the user has a passport.

Learning records become durable credentials rather than isolated course activity.

1. 1Partner opens the portal to review campaign summaries, activity status, recent records, and submission forms.
2. 2Partner creates one activity record linked to a campaign, with a public note, a review attachment, or both.
3. 3New review attachments start in a submitted or review state.
4. 4Admin verifies or rejects the activity from the admin review workflow and records an audit event.
5. 5Verified activity can appear on campaign pages, impact-site histories, and corporate reporting when relevant.

Partner field activity is useful quickly, but verification stays under platform governance.

1. 1Admin creates a corporate account and program, then assigns a user or grants corporate permissions.
2. 2Corporate user manages programs, project portfolio allocations, contribution status, budgets, and employee engagement.
3. 3Contribution ledger records can count toward public campaign progress only when eligible and configured to do so.
4. 4Verified campaign activity is linked into corporate reporting for funded projects.
5. 5Reports bundle portfolio, contribution, financial, and activity data into export records.

Corporate impact is auditable without mixing organization support into personal donation records.

1. 1Admin manages campaigns, expeditions, partners, impact sites, Academy content, reports, users, and activity review.
2. 2Admin reconciles payment status when operational review is required.
3. 3Admin changes partner verification levels and campaign status while preserving public-page stability.
4. 4Important admin actions write or preserve audit log records.
5. 5Public pages continue to expose only approved, public-safe information after operational changes.

The platform can grow operationally while keeping public trust pages and private workspaces separated.