Frontend Management Dashboard

DayTidy Pro’s Frontend Dashboard gives permitted users a frontend workflow for managing offerings. With Resource Groups, offering-owned resource workflows are available too. This dashboard serves managers and contributors; the Free customer portal serves customers reviewing their own reservations.

Before setup

Keep Free and Pro active, verify Pro authorization, and enable Frontend Dashboard under DayTidy → Settings → Modules. Enable Resource Groups when offering-owned resource management is needed. Confirm which WordPress users should manage content and review the dashboard module’s options before allowing registration or submission.

The shortcode is not an access-control substitute. Module settings, logged-in identity, ownership, and the relevant capabilities determine what a visitor can do. Do not assume every signed-in customer should manage offerings.

Publish the dashboard page

1. Create a WordPress page with a clear title such as “Offering management.”
2. Add a Shortcode block containing the following shortcode.
3. Publish the page. Open the Frontend Dashboard module options, select it as Dashboard Page, and save. Add it to the appropriate staff navigation.
4. Open it as an intended non-administrator user and check the available controls.
5. Open it as a visitor without that access and verify the actual authentication/submission behavior matches your policy.

[daytidy-dashboard]

Guest submission controls

The module options include Guest Submission → Status. It is disabled when unset. If the business intentionally accepts guest offering submissions, review Registration: Disabled, Once Submitted, or Once Approved. These govern offering-contributor registration, not the customer portal. Test the guest outcome and approval policy before opening that path publicly.

Verify an offering workflow

Using a test offering owned by the intended manager, open its editor and review details, schedule, booking options, and available resources. Save a small authorized change and reopen it to verify persistence. Confirm the public offering still has valid sessions and options. Check with a second user that ownership and access restrictions are respected.

Offering-owned resources must be saved with their containing form. Dialog completion alone does not establish persistence. After a validation error, correct the reported problem and recheck the saved resource rather than adding duplicates.

Common problems

• Missing dashboard controls: check Pro authorization, enabled modules, module options, and the user’s permissions.
• A manager cannot see an offering: verify ownership and permitted workflow before broadening access.
• A resource save fails: inspect its required name/type/capacity, duplicate names, and the reported error.
• A customer needs a cancellation link: configure the customer portal instead of giving them management access.

Use Resources for resource setup and the launch checklist to verify the public booking experience after manager changes.