Release Notes & Known Limitations¶

Overview¶

This document records intentional gaps, roadmap items, and platform constraints as of the current Nigall codebase—so customers and implementers set correct expectations.

Purpose¶

Prevent surprise when a documented enterprise feature is plan-gated, unimplemented, or web-only.

Who should use it¶

Sales and customer success
Organizers evaluating fit
Developers planning integrations

Benefits¶

Transparent roadmap signaling
Reduced escalations on unsupported workflows
Clear web vs mobile boundary

N/A — reference document. Related setup paths in linked articles.

Prerequisites¶

N/A

Known limitations (current codebase)¶

Not implemented¶

Feature	Status	Notes
Judge panels / judging	❌ Not implemented	No judge models or views. Speaker review is organizer/staff only. Roadmap for talent/speaker contexts.
Multi-coupon campaigns	❌ Not implemented	Single `coupon_code` per event.
Mobile survey on RSVP	❌ Not implemented	Documented in survey custom questions article.
Self-serve Exhibitors plan	✅ Complete (`complete`)	Enterprise remains sales-only for custom contracts.

Recently implemented¶

Feature	Status	Notes
Venue Management (Growth+)	✅ Core + roadmap	Profiles, directory, booking pipeline, VenueMembership, Spaces + holds, CRM quotes/activity, Stripe deposits, portfolio roll-up, opt-in public page with upcoming public events. Roadmap: e-sign, BEO PDF, labor roster, public venue directory.
Speaker & talent public pages	✅ Opt-in	`/speakers/<slug>/` and `/talent/<slug>/`. Free to publish. Upcoming programs only when the owner opts in and the event is public. No public VIP pages. Talk catalogs, testimonials, and embeds are not built.
Native attendee mobile app + push	✅ Implemented	Expo app in `mobile/`; device register + Expo Push; agenda + notifications inbox. Session reminders via `process_program_notifications`.
Co-organizer / org roles	✅ Implemented	`EventOrganizer` model; host manages team at `/events/<pk>/<tag>/team/`. Co-organizers use `can_manage_event` / `managed_events_queryset`.
Venue team roles	✅ Implemented	`VenueMembership` (manager / sales / staff); owner invites at `/events/venues/<pk>/team/`.
Venue spaces & holds	✅ Implemented	`VenueSpace` + `VenueHold`; calendar at `/events/venues/<pk>/calendar/`; inquiries place 72h soft holds.
Venue booking CRM	✅ Implemented	Activity feed, quote line items, quote expiry; confirm auto-creates/links Event + venue owner as EventOrganizer.
Venue Stripe deposits	✅ Implemented	Organizer Checkout for deposits; webhook `venue_booking_deposit`; portfolio at `/events/venues/portfolio/`.
Multi-venue portfolio	✅ Implemented	Roll-up leads, occupancy, revenue, deposits across managed venues.
Organizer REST API	✅ Implemented	`/api/organizer/v1/events/` — JWT or session auth; scoped to managed events.
Mobile full registration	✅ Implemented	Mobile API: registration info (tiers), register, and Stripe checkout endpoints.
Unified analytics dashboard	✅ Implemented	`/events/<pk>/<tag>/analytics/` aggregates per-module analytics.
Auto-post to social networks	✅ Organizer tool	Excel-scheduled publishing at `/social-publishing/` for organizers and staff (`dry_run` / webhook / selective API). Per-user credentials. Essentials plan. See Social Publishing.

Partial / flag-only¶

Feature	Status	Notes
SMS reminders	⚠️ Flag only	`sms_reminders_enabled` on Event; email is primary channel. Vendor SMS logs to console without `SMS_PROVIDER`.
Per-event subscription billing	⚠️ Enum exists	`BILLING_CYCLE_PER_EVENT` in model; prices $0 in `SUBSCRIPTION_PLAN_PRICES`.
Refund UI	⚠️ Partial	Refunds processed in Stripe Dashboard; manual sync in Nigall.
Social sharing AI	⚠️ Optional	Works without AI via template fallback; set `OPENAI_API_KEY` for tailored copy. See Social Sharing.

Architectural constraints¶

Constraint	Detail
Host + co-organizers	Host owns billing; co-organizers manage via `EventOrganizer`
RSVP OR Registration	One `registration_type`; attendees module supersedes RSVP UI on registration type
Django monolith	No microservice per module
Staff bypass	`is_staff` sees all tools — not customer feature
Planner CRM ownership	CRM rows hang off the planner user (`EventPlannerProfile.planner`); Organization only affects billing unlock
Planner CRM ↔ Venue directory	Venue Contacts / Partnership Agreements are not linked to Nigall Venue profiles
Planner CRM public API	No public REST API for CRM entities in v1
Planner CRM e-sign / BEO / Excel	Client contract is upload + manual signed status; no DocuSign, BEO PDF generation, or budget spreadsheet import yet

Plan gating summary¶

Tool	Minimum plan
attendees, program, communications, social_publishing	Essentials (`basic`)
speakers, talent, venues	Growth (`plus`)
volunteers, vendors, sponsors	Operations (`pro`)
planner_crm	Growth+ and Planner CRM add-on (`planner_crm_addon`)
exhibitors	Complete (`complete`) / Enterprise for custom contracts

Free tier: create events, no paid Tools hub modules.

Platform fee summary¶

Organizer plan	Ticket platform fee
Free, Essentials	5%
Growth, Operations Suite	3%

Sponsor payments use separate sponsor_platform_fee_percent on event (default 5%).

Web vs mobile matrix¶

Capability	Web	Mobile API
Discover	✅	✅
Event detail	✅	✅
RSVP	✅	✅
Survey questions	✅	❌
Attendee registration	✅	✅
Stripe checkout	✅	✅
Tickets / QR	✅	✅ list
Module management	✅	❌ (organizer REST for events)
Talent CRM	✅	❌ (separate REST API)

Business rules¶

Documented limitations are intentional product boundaries unless marked roadmap.

Validation rules¶

N/A

User permissions¶

N/A

Workflow¶

Examples¶

Need judge scoring for CFP: Not available — use organizer review queue; external judging spreadsheet.

Need co-host: Add co-organizers by email from the event team page (/events/<pk>/<tag>/team/).

Need exhibitor on Pro plan: Upgrade to Enterprise via sales.

Best practices¶

Review this doc during RFP/scoping
Quote Enterprise for exhibitor halls
Assume email-first comms unless SMS provider contracted

Tips¶

Talent API is production-ready for CRM integrations
Mobile API supports discover, RSVP, registration, checkout, and ticket wallet
Organizer API at /api/organizer/v1/ for managed event CRUD

Common mistakes¶

Assumption	Reality
Judges included	Not built
SMS blasts from Communications	Email only in hub
API to create events	Organizer REST API + web
Any paid plan unlocks exhibitors	Enterprise only

FAQs¶

When will judges ship?
No committed date — listed as roadmap in speaker/talent context.

Will co-host roles arrive?
Available now via EventOrganizer team management (host-only invites).

Troubleshooting¶

If a feature is listed here as not implemented, no configuration fix exists — use workaround or contact product.

Screenshot placeholders¶

N/A

Administrator notes¶

Do not enable is_staff for customers as co-host workaround — use EventOrganizer invites
Track limitation requests in product backlog

Developer/API notes¶

Verify limitations before integration SOW:

# No judge references in codebase (grep confirms)
# EVENT_FORM_FIELD_TOOL_KEYS maps toggles to plans
# mobile_api/urls.py — discover, RSVP, registration, checkout, tickets
# organizer_api/urls.py — managed event CRUD

Version alignment¶

Last updated: July 2026
Aligned with: Nigall event-platform Django monolith (apps: events, attendees, payments, communications, program, speakers, exhibitors, vendors, sponsors, talent_management, mobile_api, organizer_api, users, social_publishing)