Checking access

Private information will not load until your account and protected role are confirmed.

Founding contributors

Grant complimentary access

Use this to give a trusted client Trail Contributor access before subscriptions open, so there is useful rider data in place when they do. Grants are recorded against the admin who made them, and are revoked by status rather than deleted so the history survives.

Members can never grant themselves access. Firestore Rules only accept a grant written by a confirmed owner administrator. A future Square webhook will write through a trusted backend, not the browser.

Site usage

What people are actually using

A tally of how many times each tool was run, by day. It records a key, a number and a date, with no visitor identity of any kind: no session, no address, no location. It answers “what should we build next and what should we fix first”, and it deliberately cannot answer “who”.

Google Analytics

Visitors, where they are, and how they arrived

Geography, devices, referrers and traffic sources come from Google Analytics, because they are worked out from the visitor’s network address, which a browser cannot see and this site therefore never records.

The panel below is the live report, shared with everyone on a @lazykhorsemanship.com address, so every administrator on a company account sees it, now and in future, with nothing to set up.

If it asks for access: either you are signed in to this browser with a different Google account, or your administrator account is not on the company domain. The first is fixed by switching accounts; the second by an owner adding your address once, as a Viewer, from the report’s own Share dialog. The report is deliberately not public, because the address of this frame is readable in the page source.

Data begins on 25 August 2026, when Analytics was switched on. Open it full size at Looker Studio, where you can add charts by dragging a field onto the canvas.

New members

People to welcome

Members who joined recently, newest first. There is no automated welcome email. Firebase does not send one, and building it would need a billing account and an outside email vendor for a handful of people. This opens your own mail client with the message already written, so it goes out in your words and from your address.

Print reports

Client and horse report

Reports include everything the selected member has saved. Untick a section to leave it out.

Sections
Payments

Payments nobody could match

Somebody paid and the email Square holds does not match any account: a typo, a different address from the one they signed up with, or a subscription bought as a gift. The payment is real and the person has nothing. Nothing here is automatic: find who it was, grant them Horse Hub Plus above, then mark it handled so it leaves this list.

Loading.

Members who may be paying twice

Two Square subscriptions on one account, usually a checkout page left open and paid later, after a second one had already gone through. They are being charged $6.99 twice a month and will not necessarily notice. Nothing is canceled automatically: canceling somebody’s payment arrangement on a guess is not a thing this site does. Open the two subscriptions in Square, cancel the one they did not mean to keep, and refund it if that is the right thing. Sales being final is a policy about people changing their minds, not about our own double billing. Then mark it handled, which records who dealt with it and what they did.

Loading.

Trail stewardship

Moderation and source review

Waiting for review

A rider report and a photograph are both filed as pending and are visible only to their author and the trail team; approving one is what makes it visible to other members. Comments are the other way round: they are published immediately and appear here only when somebody reports one, where the action is to hide it. Nothing anybody uploads is ever seen until this queue is worked.

Loading the review queue.

Source discrepancies

Keep provider disagreements visible and mark individual facts as Lazy K reviewed only after checking the cited source.

No discrepancies loaded.

Activity history limitation

Administrator actions recorded by this browser are useful operational history, but they are not a tamper-proof audit log. A complete, guaranteed audit trail would require trusted server-side writes.