Golf Club Hub · test copy

Who opens what, and approval before live

How Club Hub will look for the Met's office once the staff are added: each person keeps exactly what they open today, and website changes wait for Ivano.

Test data only. Nothing here is live, and nobody was emailed.

The four people

On top of their role, each person has a list of what they open. The club's owner or manager sets it on the Staff screen.

PersonOpensAlso
IvanoEverythingApproves website changes
SimaEverything except RentalsSends the newsletter, works applications
BillyEverything except the newsletterWorks applications
JohnWebsite pages, Pictures, Enquiries, Rentals and Website settingsNo newsletter, no applications

Still to confirm: whether Sima and Billy open Rentals. This test copy gives Billy Rentals and not Sima. Either way it is one tick per person on the Staff screen.

Club Hub Staff screen: Billy, Ivano, John and Sima with what each opens, Ivano marked as approving website changes, and approval switched on
Ivano's Staff screen: what each person opens, a Change button for each, and who approves website changes.

What each person sees

The menu shows only what a person opens. Communications is the newsletter.

Ivano's Club Hub: the full menu and the club overview
Ivano: everything.
Sima's Club Hub: Overview, Applications, Enquiries, Communications and Website, with no Rentals
Sima: no Rentals.
Billy's Club Hub: Overview, Rentals, Applications, Enquiries and Website, with no Communications
Billy: no newsletter.
John's Club Hub: Overview, Rentals, Enquiries and Website, with no Communications and no Applications
John: no newsletter, no applications.

A website change waiting for Ivano

It is still waiting on the test copy, so this is exactly what Ivano would see.

  1. Sima changes the Events page and presses Save and send for approval.

    A new title and a new date for the Club Championship. The website does not change: her work stays as a draft, and Club Hub tells her it went to Ivano.

    Sima's page editor: Sent to Ivano for approval, and the change waiting for Ivano's approval

  2. Ivano gets an email with what would change.

    The button opens the change in Club Hub. On this test copy the email was kept in a folder instead of being sent.

    The approval email: Sima has changed the Events page, with before and after, and a Review and approve button

  3. His Approvals list shows it waiting.

    Ivano's Approvals list: the Events page waiting, asked by Sima

  4. He reads the before and after, then approves it or not.

    Approving puts it on the website straight away. Not approving leaves the website as it is, with an optional note for Sima. Sima is told either way.

    The change: page title Events to Events and competitions, and the Club Championship from 17 to 24 October, with Approve and Do not approve
    The same change on a phone, with Approve and Do not approve

What waits and what does not

Waits for Ivano

  • Website pages
  • The website's menu
  • The club details on the website
  • The website settings
  • Deleting a page

Never waits, as on the Met's admin today

  • Pictures
  • The newsletter
  • Enquiries
  • Applications
  • Rentals

Ivano's own changes go live straight away. If the person named to approve ever left the staff, website changes would be held, never published, until somebody else is named.

Locked, not only hidden

Each person's own login asked Club Hub's server and its database directly for each area. Checked at 15:44 on the test copy.

AreaIvanoSimaBillyJohn
NewsletterOpensOpensRefusedRefused
ApplicationsOpensOpensOpensRefused
RentalsOpensRefusedOpensOpens
EnquiriesOpensOpensOpensOpens

Refused means the server said no and the database showed no rows. Nobody gains or loses anything until the owner or a manager narrows somebody, so the club's other logins are unchanged.