Skip to content

docs: fiscal host profile hides internal platform billing transactions - #25

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/frontend-documentation-updates-363e
Draft

docs: fiscal host profile hides internal platform billing transactions#25
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/frontend-documentation-updates-363e

Conversation

@cursor

@cursor cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown

Summary

Documents frontend change opencollective-frontend#12345: Fiscal Host public profile pages no longer show internal platform billing transactions (platform tips on the internal Platform Tips account and application fees) in the default Budget and Transactions sections.

Docs added/updated

  • advanced/ledger/viewing-transactions.md — new "Public profile vs. Dashboard" section for fiscal hosts
  • advanced/ledger/individual-transactions.md — added APPLICATION_FEE transaction kind; clarified PLATFORM_TIP on host accounts
  • advanced/ledger/ledger-changelog.md — August 2026 changelog entry
  • fiscal-hosts/platform-settlements.md — where to find platform tip activity

Codepaths covered

  • Fiscal Host public profile Budget and Transactions sections (getDefaultKinds({ isHost }))
  • Dashboard Transactions kind filter (unchanged; documented as the place to review hidden transactions)

Knowledge gaps addressed

  • Why platform tip and application fee transactions disappeared from fiscal host public profiles
  • How fiscal host admins can still access these transactions
  • Distinction between tips a contributor gave vs. tips collected on behalf of the platform

Other recent changes reviewed (no doc updates needed)

Open in Web View Automation 

Document frontend change (opencollective-frontend#12345) that excludes
PLATFORM_TIP and APPLICATION_FEE from the default Budget and Transactions
sections on Fiscal Host public profiles. Dashboard transactions, exports,
and API behavior are unchanged.

Co-authored-by: Benjamin Piouffle <Betree@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant