Support

FAQ

All Getting started Import Editing Publishing Domains Roles Billing Support Security Websites

What is Loreto Sites for?

Loreto Sites is the admin side for creating, editing, publishing, hosting, and managing parish and school websites.

In-depth answer+

Loreto Sites uses a draft-first workflow: create or import a site shell, review generated content, make edits in draft, preview the public experience, then publish only after approval. The dashboard is intended to be the operational source of truth for the next required action.

Technical checks

Confirm whether the site should begin from an import or from scratch. Use import when a public website already has useful structure, Mass times, staff pages, bulletins, or event content.
Check that the organization name, current website URL, primary contact, and site type are correct before sending a request. Incorrect intake data can create duplicate organizations or hard-to-match drafts.
After sign-in, verify that the dashboard shows the expected site and that the user has access to edit content, publish, or manage billing depending on the task.
If a draft appears missing, include the URL submitted, the approximate import time, and the Google account used to sign in so support can trace the import claim and organization membership.

Escalation details to include

Send support the site URL, organization name, user email, and the exact screen where the workflow stopped.
Attach a screenshot if the dashboard shows no site, the wrong site, or a disabled next-step button.
Do not restart the import repeatedly for the same website unless support asks you to. Duplicate imports can make ownership and review history harder to follow.

Reference notes

Dashboard: shows the next recommended setup, review, publish, billing, or domain action.
Import flow: creates a draft from public website content and stores the review state before publish.
Scratch flow: creates a structured draft from manual answers when no usable source website exists.
Support request: use when the app state and expected next action do not match.

What should I do first after signing in?

Start with one guided setup path: import an existing website or create a new draft. The dashboard keeps the next step visible so you only need to handle one decision at a time.

In-depth answer+

Technical checks

Confirm whether the site should begin from an import or from scratch. Use import when a public website already has useful structure, Mass times, staff pages, bulletins, or event content.
Check that the organization name, current website URL, primary contact, and site type are correct before sending a request. Incorrect intake data can create duplicate organizations or hard-to-match drafts.
After sign-in, verify that the dashboard shows the expected site and that the user has access to edit content, publish, or manage billing depending on the task.
If a draft appears missing, include the URL submitted, the approximate import time, and the Google account used to sign in so support can trace the import claim and organization membership.

Escalation details to include

Send support the site URL, organization name, user email, and the exact screen where the workflow stopped.
Attach a screenshot if the dashboard shows no site, the wrong site, or a disabled next-step button.
Do not restart the import repeatedly for the same website unless support asks you to. Duplicate imports can make ownership and review history harder to follow.

Reference notes

Dashboard: shows the next recommended setup, review, publish, billing, or domain action.
Import flow: creates a draft from public website content and stores the review state before publish.
Scratch flow: creates a structured draft from manual answers when no usable source website exists.
Support request: use when the app state and expected next action do not match.

Can one parish manage more than one site?

Yes. A parish can manage parish, school, campaign, ministry, and location-specific sites from the same dashboard when the plan and permissions allow it.

In-depth answer+

Technical checks

Confirm whether the site should begin from an import or from scratch. Use import when a public website already has useful structure, Mass times, staff pages, bulletins, or event content.
Check that the organization name, current website URL, primary contact, and site type are correct before sending a request. Incorrect intake data can create duplicate organizations or hard-to-match drafts.
After sign-in, verify that the dashboard shows the expected site and that the user has access to edit content, publish, or manage billing depending on the task.
If a draft appears missing, include the URL submitted, the approximate import time, and the Google account used to sign in so support can trace the import claim and organization membership.

Escalation details to include

Send support the site URL, organization name, user email, and the exact screen where the workflow stopped.
Attach a screenshot if the dashboard shows no site, the wrong site, or a disabled next-step button.
Do not restart the import repeatedly for the same website unless support asks you to. Duplicate imports can make ownership and review history harder to follow.

Reference notes

Dashboard: shows the next recommended setup, review, publish, billing, or domain action.
Import flow: creates a draft from public website content and stores the review state before publish.
Scratch flow: creates a structured draft from manual answers when no usable source website exists.
Support request: use when the app state and expected next action do not match.

Contact us

Include the domain, current site or dashboard URL, what changed, what you expected, and a screenshot when the issue is visual.

Need urgent help?

We will get back to you as soon as possible.

Text support