Custom build
Email Change API
New email, same student.
How do you teach?
When a district changes someone’s email, their history in Pencil Spaces can split into two accounts. We build an API to change a user’s email while keeping every past lesson and record attached to the same person.
When a partner district changes student emails, your records split in two. Change emails by API, and every past lesson and attendance record stays with the same person.
Your school moves to a new email domain, and student histories risk splitting. Change emails by API, with history and attendance carried along.
Your company changes email domains after a merger. Change every user’s email by API, with their training history carried along.
Your district changes student email formats, and nobody wants duplicate accounts. Change emails by API, keeping every past lesson and record attached.
When people’s emails change, their workshop history stays attached. We build an API to change emails with history carried along.
Parents won’t need this. If your child’s school email changes, their lesson history stays with them.
Free for 2 weeks on any paid plan. No credit card required.
What it solves
Helps you
Save time
Part of
Custom
The problem
A new email splits a person in two
Districts change email addresses for whole schools at once. Without a way to change them in place, people end up with new accounts and lose their history.
The usual way
Support teams create new accounts and move records by hand, or leave the history behind.
How Pencil Spaces solves it
An API to change a user’s email address in your institution when a district changes it, keeping every past lesson and record attached to the same person.
What changes
Every person keeps one account and one history, whatever their email.
What we build
- Update email by API
- History and attendance carried along
- Re-verification handled in the flow
Typical build time: about 1 month.
What it looks like
In practice
A district moves every student to a new email format. The program changes each email by API. History and attendance carry over, and re-verification is handled in the flow.
In a 1:1 lesson
A partner district renames every student email, and your tutors still see each student’s full history.
In a group class
After the domain change, every student’s past classes and attendance are still on their account.
In a virtual training
After the merger, everyone’s training history follows them to their new email.
In your classroom
A student’s email changes mid-year, and her intervention history stays on her account.
In the training room
A facilitator’s email changes, and their workshop history stays with them.
At home
Your son’s school email changes, and his tutor still sees every past lesson.
