Handing it on
Share a beacon, what travels with it, and why adoption is the one sharing signal the app trusts.
By the end of this lesson
- Share a beacon and explain what the recipient receives
- Say why results do not travel with the method
- Understand what adoption counts and what it deliberately does not record
Watch
No episode recorded
This lesson has no video. It covers material the narrated season does not, and the written lesson is complete on its own.
The lesson
Sharing a beacon produces a link. Anyone with it can read the method — the problem, the community, and the worksheet answers. Nobody needs an account to look.
A signed-in person can then adopt it, which gives them their own copy. The method comes across; the results do not. Their copy starts with no people helped, no test history, no recorded impact. This is the right behaviour and it is worth being explicit about why: your results are a record of what you did, and inheriting them would make somebody else's record partly fictional from the first day.
Each adoption increments a count on the original. That count is the one sharing signal this app can actually verify — it watched the copy being made — which is why it feeds the sharing factor alongside the teachers you report having trained.
What is deliberately not recorded is who adopted it. You see how many people carried the work forward, never their identities. That is a privacy decision rather than a technical limitation, and it means the number is a genuine measure of reach rather than a contact list.
A link can be revoked. If you do, existing copies stay with the people who made them — they took the method, and it is theirs now.
Do this in the app
Put the lesson down somewhere real
Open your beacon and create a share link.
Done when — You have a link you could send to someone.
/dashboardOpen the link yourself to see what a recipient sees before you send it to anyone.
Done when — You have read the public view of your own method.
/dashboard
Go further
Check yourself