Support
FAQ
Can parish staff have different permissions?
Yes. Owners, admins, editors, and viewers can be separated so sensitive actions like billing, domains, deletion, and publishing stay controlled.
In-depth answer+
Roles and permissions control who can edit content, publish, manage billing, configure domains, upload assets, and invite other users. Access should follow least privilege: give each user only the permissions needed for their work.
Technical checks
- Confirm the user is signed in with the expected email address. Google account aliases and parish emails can easily be confused.
- Check whether the user is active, invited, suspended, or attached to the wrong organization.
- Confirm the user has access to the specific site, not only the parent organization.
- Match the blocked action to the required permission: content edit, publish, billing, domain setup, analytics, or people management.
Escalation details to include
- Send the user email, organization, site, expected role, blocked page, and blocked action.
- If an invitation failed, include the invited email, sender email, approximate send time, and whether the link expired.
- If ownership is wrong, include who should be owner and who currently appears to control the account.
Reference notes
- Owner or admin: can usually manage organization-level settings and critical access.
- Editor: can change draft content but may not publish.
- Publisher: can approve and publish live changes.
- Viewer or restricted roles: can inspect content or analytics without changing production state.
Who should be an owner?
Use owners sparingly: typically the pastor, business manager, communications lead, or trusted administrator responsible for billing and critical settings.
In-depth answer+
Roles and permissions control who can edit content, publish, manage billing, configure domains, upload assets, and invite other users. Access should follow least privilege: give each user only the permissions needed for their work.
Technical checks
- Confirm the user is signed in with the expected email address. Google account aliases and parish emails can easily be confused.
- Check whether the user is active, invited, suspended, or attached to the wrong organization.
- Confirm the user has access to the specific site, not only the parent organization.
- Match the blocked action to the required permission: content edit, publish, billing, domain setup, analytics, or people management.
Escalation details to include
- Send the user email, organization, site, expected role, blocked page, and blocked action.
- If an invitation failed, include the invited email, sender email, approximate send time, and whether the link expired.
- If ownership is wrong, include who should be owner and who currently appears to control the account.
Reference notes
- Owner or admin: can usually manage organization-level settings and critical access.
- Editor: can change draft content but may not publish.
- Publisher: can approve and publish live changes.
- Viewer or restricted roles: can inspect content or analytics without changing production state.
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.