Skip to main content

Site Homepage, Payments, Team, and Settings

Site Homepage builder​

The Site Homepage module controls the tenant-facing public website for that workspace.

EventSale homepage builder

From the Layout tab you can publish and reorder homepage sections such as:

  • header
  • tenant hero
  • partners ticker
  • photo gallery
  • FAQ
  • previous rounds gallery
  • current gallery items

This is the main place where the buyer shapes the public-facing brand without touching code.

Public team roster​

The Team tab inside Site Homepage is not the same as internal staff access. It controls the public manager list shown to visitors.

Use it to:

  • add managers to the public roster
  • reorder who appears first
  • sync in-world presence status
  • edit profile links and remove old staff

Payments​

The Payments page combines ledger visibility with payment device management.

EventSale payments

The top ledger lets you filter by month and round. It answers:

  • who paid
  • when they paid
  • how much was charged
  • whether the payment is already attached as paid

The bottom section lists payment terminals enrolled for the workspace.

Use it to verify:

  • the terminal is active
  • the map link is correct
  • disabled terminals are not left in production accidentally

Internal team management​

The main Team page is for workspace staff, not public-facing creators.

EventSale team roster

This is where owners:

  • invite workspace members by email
  • assign roles
  • suspend or remove access
  • track invite acceptance and status

Use this area for internal operators. Use the creator-side Managers area only for assistants attached to one creator profile.

Settings as the control center​

The Settings page brings together branding, portal toggles, and operational defaults.

EventSale settings page

Public-facing controls include:

  • brand name
  • support email
  • hero text
  • accent color
  • hero image
  • logo
  • portal, login, and application enablement

Operational controls include:

  • payment land link
  • default weekly fee
  • creator verification policy
  • manager onboarding policy
  • automation-related defaults

Use this weekly routine:

  1. Settings: confirm public and operational defaults
  2. Team: confirm staff access is still correct
  3. Payments: confirm active terminals and paid ledger entries
  4. Site Homepage: publish updates only after public copy and gallery content are ready

That keeps the tenant stable without overcomplicating the daily workflow.