Frequently asked questions

Questions before you apply?

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.

Who should apply?

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.

Do wards and stakes get the same features?

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.

What is the biggest win for a ward?

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.

Do we need a custom domain to get started?

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.

Can we invite clerks, executive secretaries, and other leaders?

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.

How are schedules and leader workflows protected?

Member-facing pages stay public and simple, while presidency schedules, setup, and other admin workflows stay inside authenticated leader views with role-based access.

What happens after approval?

The first rollout is meant to stay manageable. Once the request is approved, the process looks like this:

  1. You submit the request with the unit details and main contact.
  2. We review the request and provision the workspace for the approved unit.
  3. You receive a welcome email with the next steps for password setup and onboarding.
  4. You complete the guided setup, invite leaders, and launch when ready.

What should we expect at launch?

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.

  • Start with schedule management for the bishopric or presidency since that delivers the fastest return.
  • Add announcements and calendars next to give members one place to go.
  • Invite the core leaders first, then expand access and adopt additional features as needed.

Ready to move from questions to setup?

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.