Fixing something that is wrong

Every value on Homeward belongs to one record, and the fix is always to correct the record that owns it. Editing a nearby field to compensate — a profile note explaining a wrong transaction, a renamed fund covering for a mis-applied gift — leaves the underlying error in place and makes it harder to find later.

This page is a map: find what needs fixing, and go to the place that owns it.

What needs fixing	Where it is owned	Where to go
A public field — name shown publicly, story, photos, contact channels	The profile	Your individual profile or Building your organization profile
A private field — date of birth, health and dietary notes, travel documents	The person’s private record	Travel documents, health, and emergency contacts
A legal name, registration number, or annual financials	The country-specific legal entity	Legal entities, verification, and financials
A role, platform role, or management grant	A separate access record	Visibility, connections, and profile managers
A duplicate person or organization	A reviewed combination request	Getting help
A transaction, receipt, fund balance, or payout	The owning financial workflow	Getting help

Why the boundaries matter

The boundaries are what keep records trustworthy. Public identity, story, media, and contact channels belong to the profile, so you can fix them yourself in seconds. Private identity data sits on the person’s private record, where it is not exposed. Regulator identifiers, verified names, governance, and annual financials belong to a legal entity, because that is what a regulator checks — changing them anywhere else would not change what is verified.

Access is the same. Organization roles, profile-management grants, and platform roles are separate records: granting someone access to a profile does not make them staff, and being an organization admin does not grant a Homeward-wide role. If access is wrong, change the access record — do not try to reach the same result by editing a profile.

Duplicates and money are different again. Combining two people or two organizations is reviewed before it happens, so the dependent records and audit history survive under one durable profile. Transactions, receipts, funds, balances, and payouts must be corrected in the workflow that owns them; a transaction is a payment record, not a field on a profile.

Requesting a correction

For anything you cannot change yourself, send Homeward a support request and include:

the affected record;
the current value;
the correct value;
the source that supports the correction.