Frequently asked questions
This page covers the rollout questions that come up most often: who should apply, how approval works, what the first setup looks like, and how the product handles access and privacy.
MyStakeTools is built for stake and ward leaders who are responsible for scheduling, communication, or rollout. That usually means stake presidents, bishoprics, clerks, executive secretaries, or another admin helping coordinate setup.
Both get schedule management, announcements, calendars, and agenda tools. Stakes also unlock building lockup coordination, service assignments, and high council management. The product page has a full comparison.
Members use the public site with no login: request interviews with the bishopric or stake presidency, view the calendar, find a ward, read announcements and the newsletter, and request building reservations when the stake enables them.
Schedule management for the bishopric. It replaces the back-and-forth texts and phone calls for interview coordination with a self-serve appointment flow. After that, having announcements and calendars in one place is the next most valuable piece.
Bishopric members and the ward executive secretary share the schedule and interview tools. Ward clerks get schedule visibility and action items. Unit, building, and settings administration stays with the stake.
Stake clerks set up units, wards, and buildings, manage settings and the audit log, keep visibility into the presidency schedule, and record finalized callings in LCR.
Yes. High councilors manage their assignments and ward liaisons, track one-on-ones and ward visits, and handle the ward-scoped extension and setting-apart steps after the presidency approves a calling.
Yes. The admin side is designed around inviting the right leaders and scoping access by role so people get the tools they need without seeing everything.
No. You can launch on a MyStakeTools URL first and attach a custom domain later. That keeps rollout simple while still leaving room for a more polished public presence over time.
Member-facing pages stay public and simple, while presidency schedules, setup, and other admin workflows stay inside authenticated leader views with role-based access.
Only the stake president sees confidential interview notes. Counselors and other leader roles get the rest of the scheduling tools without those notes.
The first rollout is meant to stay manageable. Once the request is approved, the process looks like this:
The first version does not have to include every possible detail. Most units start by getting the main public experience in place, then they keep refining the site after launch.
If the FAQ answered what you needed, the next step is the application. If you want one more pass through the product, the walkthrough is still the best place to see the full experience.