Skip to content

Blaqbook Operator Docs

Welcome. This site is the day-to-day operator manual for Blaqbook — a step-by-step companion for the five people who actually run the platform. Each section is organized by the role using it. If you only run the door scanner, you can stop at that page. If you're the executive looking at the dashboards, jump straight to Dashboards. No technical background required.

Screenshot pending

A guided home screenshot will land here in a follow-up commit.


What Is Blaqbook?

Blaqbook is an all-in-one event management platform built for nightlife and music event promoters. It handles everything from selling tickets online to scanning people in at the door — with SMS marketing, vendor tracking, and profit/loss reporting built in.

Everything lives in one place. You don't need separate tools for tickets, guest lists, email blasts, and accounting. Blaqbook connects them automatically: when someone buys a ticket through Stripe, their information goes into your contact database, their ticket shows up in the door scanner, and their sale gets counted in your event P&L.


What Makes Blaqbook Different

  • Purpose-built for nightlife — genre tags, attendance scores, VIP identification, and DJ/production vendor management built in from the start
  • Branded PDF tickets with QR codes — sent automatically after purchase via email, scannable at the door
  • Mobile door scanner — works on any phone, no app required, validates tickets in real time
  • Twilio SMS marketing — send targeted text blasts directly to your contact list (not through a third-party platform; live US sends require completed 10DLC A2P registration — check with your administrator)
  • Referral engine — guests share unique links; you see exactly who referred who and reward top referrers
  • Real P&L per event — ticket revenue, POS sales, vendor costs, and bar share all in one view
  • Dynamic contact segments — group contacts by genre preference, attendance history, spend level, or any combination

The Five User Roles

Each role sees a curated subset of the platform. Menus that aren't relevant to a role are hidden so the UI stays focused.

Role What They Can Do Top-Level Menus They See
Executive (Maya Chen — maya.chen) Everything — all data, all settings All menus, including Sales, Invoicing, Calendar, etc. (Native Email Marketing is admin-only; all staff use the Blaqbook Email surface — see CRM & SMS.)
Event Manager (Jordan Rivera — jordan.rivera) Create/edit events, manage registrations, assign vendors, send SMS, view P&L Events, CRM, Inventory, Point of Sale, Door scanner. (Sales, Invoicing, Calendar, native Email Marketing — hidden)
Finance (Priya Nair — priya.nair) View and manage invoices, vendor bills, expenses; read-only on events Events, Sales, Invoicing. (POS, Inventory, Calendar, CRM — hidden)
Trusted Staff (Dante Webb — dante.webb) Read-only on contacts and events; can check in registrations via the door scanner Events, Contacts, Door scanner.
Door / Crew (Zara Okafor — zara.okafor) Door scanner + register POS sales Door scanner, Point of Sale. (Everything else — hidden)

Log in at https://[your-domain]/web with the username and password provided by your administrator.

Why don't I see a menu I used to see? Your role doesn't include it. Ask an admin to switch your group — don't try to install or enable the missing app yourself.


Page Read this if…
Events You create, publish, or manage events; you set up ticket tiers, promo codes, or referrals
Door Scanner You're on door duty checking guests in on event night
eCommerce You manage merch — online storefront and POS
CRM & SMS You send SMS blasts or wire up automated email rules
Finance You run P&L reports, pay vendors, or reconcile bills
Crew & HR You're an admin adding staff or assigning Blaqbook roles
Dashboards You want the high-level view for your role

FAQ — Cross-Cutting

Stripe says "Test Mode" — are purchases real?

In test mode, no real money is charged. Use Stripe test card 4242 4242 4242 4242 with any future expiry and any CVC. Contact your administrator to switch to live mode.

I changed a setting in Blaqbook Settings but nothing happened.

Settings stored in ir.config_parameter (Twilio creds, branding) take effect on the next request — no restart needed. Changes that touch Python code or XML views require an admin to either restart the container (Python) or upgrade the affected module (XML/data). If you edited via the Settings UI and nothing changed, log out and back in to refresh your session, then ask your admin to confirm the value was saved.

Can I change the accent color across the whole product?

Yes. Settings → Blaqbook → Colors → Secondary Color drives both the public website (buttons, links, highlights) and the Odoo backend chrome (navbar bottom border, focus rings, Discuss/Mail/Calendar accent surfaces). Save and reload — no restart needed. Primary Color is the dark background on the public site only; the backend keeps its dark identity regardless. Enter values as 6-digit hex (e.g. #3399ff).