How MitzvahManager works
A plain-language tour of the preparation lifecycle that runs on the shared organization.
One Organization, Shared Across iLeyn, MitzvahManager, and TropeTrainer
iLeyn, MitzvahManager, and TropeTrainer are three apps in one product family, built on one backend and one shared data model. When your synagogue uses more than one of them, they all run on the same organization: the same members and staff access, and the same settings live once and apply everywhere. Adding another app does not create a second account or a separate member list — it opens a new view onto the organization you already have. Only the subscription for each app is separate.
iLeyn coordinates synagogue services, MitzvahManager runs B'nai Mitzvah preparation, and TropeTrainer powers chanted-text practice — but they are not three separate systems bolted together. They share one backend and one data model, so your organization is a single record that every app you use reads from and writes to. Your members, your staff and their access, and your organization settings are stored once and shown wherever they are relevant, rather than copied between apps that can drift out of sync.
The clearest example is your chanted text: the trope, voicing, transliteration, and Hebrew display settings. MitzvahManager and iLeyn both surface these settings, and it is easy to assume they are two different configurations you must keep aligned. They are not — they are the same shared value on your one organization. Editing them in MitzvahManager changes the exact same setting you would edit in iLeyn, so if your setup asks you to configure chanted text in both apps, you are editing one value from two doors, not entering it twice. Set it once and every app your organization uses reflects it.
The people on your team, and what each of them is allowed to do, belong to the organization — not to any single app. An administrator is an administrator across the family; a staff member you add is the same person with the same identity everywhere. You manage members and access levels in one place, and every app respects them, so there is never a separate roster to invite or a parallel permission list to maintain when your synagogue adopts another app.
When your synagogue starts using another app in the family, nothing about your organization is duplicated. There is no second sign-up, no fresh member list to rebuild, and no re-entry of your community's settings — the new app simply gives your existing organization another capability. The one thing that is specific to each app is its subscription: you subscribe to iLeyn, MitzvahManager, or TropeTrainer independently, and that billing choice is the only piece that is truly per-app rather than shared.
They are three apps in one product family, built on one backend and one shared data model. If your synagogue uses more than one, they all run on the same organization rather than as separate systems.
No. They are the same shared value on your one organization. Editing chanted text in one app changes the exact setting the other app reads, so if setup points you to configure it in both places, you are editing one value from two doors.
No. Your members and their access belong to the organization, not to any single app, so you manage them once and every app respects the same roster and permissions.
The subscription for each app. You subscribe to iLeyn, MitzvahManager, and TropeTrainer independently, but the organization, its members and access, and its shared settings are the same across all of them.
A plain-language tour of the preparation lifecycle that runs on the shared organization.
The members and access levels described here are the same organization-wide roles every app respects.
Chanted text settings are the clearest shared value — configured once and reflected in every app.
Join synagogues and tutors who manage their programs with confidence.
Get Started