The Web Dashboard

Your venue's control panel. This page walks the sidebar top to bottom — the little ? in the dashboard's top bar always jumps straight to the matching section here.

Who sees what: the sidebar adapts to your role. Venue owners see everything below; managers see the pages their access grants; staff see their own profile, stats and the staff board. If a page described here is missing, you don't have that permission at the currently selected venue.

First time: your in-world setup link signs you in automatically and prompts you to create a username and password. After that, use those at the login page.
Forgot your password? Rez something of yours that talks to the system (your server, or touch your jar's owner menu) to get a fresh one-time login link, then set a new password under My Profile.
Venue picker: if you own or work at several venues, the picker at the top of the sidebar switches between them. Every page shows the selected venue's data.

Dashboard

The landing page — a read-only overview of how the venue is doing:

Tips per Day — venue-wide tip volume over time.
Top Earners This Week — who's bringing it in.
Your Stats / Your Tips per Day — your personal numbers, for staff.
Recent Sessions — who logged into which jar, and when.

My Profile

Your personal settings — every user has this page, staff included:

Second Life Profile — the avatar this account belongs to.
Web Account — your username for logging in here.
Change Password.
My Job Settings — your personal stream URL and per-job preferences the jars use when you log in. DJs: this is where your stream lives.

Manage Venue

The venue's own configuration, section by section — each card saves on its own:

Basic Info — name, description, location link.
Notice Bot — attach one of your bots to this venue so events can send group notices and reminders.
Auto-Greet & Invite — have the bot welcome arrivals and offer your group.
Streams — the default stream (plays when no one is on) and the club stream (the house backup DJs can be forced to or fall back on).
Tip Jar / Jar Behaviour — tip amount tiers, hover text, thank-you message, and how tippers are notified.
Tip Split — the staff/house percentage applied in-world the moment a tip is paid.
Notifications — what the venue pings you about.
Danger Zone — delete the venue. This cascades: staff assignments, events and history go with it. There is no undo.

Manage Access

Owner only. Who can manage this venue on the web, and what they can do:

Grant Access — add a person and choose their role. Roles bundle sensible permission sets so you rarely need to think harder than "manager" vs "staff".
People with access — review and revoke. Guardrails stop you from locking yourself out or demoting the owner.

Manage Jobs

The job types your venue offers — DJ, Host, Dancer, whatever fits:

Job Types — each defines how the jar behaves for that role: whether logging in swaps the parcel stream, tip tiers, and rank.
Add Job Type — create new roles as the venue grows.

Manage Staff

Who holds which job. Assign people to the job types you defined, and remove them when they move on — removing someone here is what stops them appearing in the jar's login picker.

Audit Staff

Housekeeping for the staff list: spot people who haven't logged a session in ages, and prune them safely. Removals here use the same careful cascade as Manage Staff — history is kept, future access is removed.

Staff Board

An internal noticeboard for your team:

Post a Notice — announcements, schedule changes, house rules.
Posted Notices — what's currently up; take down what's stale.

Events

The venue calendar, and the engine behind automated notices:

Scheduled Events — create events with a start time (SLT), a genre, and the staff working them (DJ, host).
Reminders — each event can carry reminders that fire at offsets you choose (e.g. 24 h and 30 min before): a group notice to every SL group mapped to the event's genre, or a staff IM to the people working it. Delivery needs a bot; venues without one still get staff IMs via their in-world server.
Notice text comes from your templates, so events stay consistent without retyping.

Genres

Tags for your events — and the routing table for notices. Map each genre to the SL groups that should hear about it, and event reminders fan out to the right audiences automatically.

Templates

Reusable notice text with placeholders (event name, time, staff). Write them once; events reference them for their group notices and reminders.

Fundraisers

The web half of donation jars:

Add Fundraiser — name, recipient (who the donations pay out to), goal, and duration.
Info menu — what donors see when they ask the jar for info: website link, about text, optional freebie item.
Fundraisers — live progress; close them when done. A manager picks which fundraiser each Donation Jar runs from the jar itself, in-world.

Bots

Register a New Bot — name it and you're given the bot's token plus a ready-made .env snippet. Save the token immediately — it's shown once. Lost it? Use Regenerate Token and update the bot's .env.
Live panel — once your bot is running you can see its location, groups, recent IMs and inventory offers here, teleport it home, accept group invites, and send IMs or group notices by hand.
Groups — shows which groups the bot can actually send notices in (it needs the group's Send Notices power).
Token & Removal — regenerate the token or retire the bot.

View Tips

The money page: pick a staff member (or the whole venue) and browse the full tip history — who tipped, how much, when, and on which jar. This is the record the jars report to in real time; if the web was down when a tip landed, it appears here as soon as the server reconciles.

Staff Job Data

A focused page for staffers to check and tune how the jar treats them: find your avatar, review your staff record, and set your tip jar, stream and media details. Staff reach it from their own login — it's the quick version of My Profile → My Job Settings.