FAQ: Why Can I Not See a Feature?
Work through package access, module activation, event setup, and role permissions when a page or button is missing.
Article guidance
Missing features usually come from one of four places: the organisation package, the event module setup, your role permissions, or the current event state.
Check these first
- Check your organisation package: Some features, such as Ticketing, Stage Manager, Site Plan, Transport, team management, recurring events, open applications, SMS, or White Label, depend on package access.
- Check your role: A feature can be available to the organisation but hidden from users without the right permission.
- Check the event module: Ticketing, Stage Manager, Site Plan, and Trader Manager may need to be set up on the event before their event-specific pages open.
- Check event or form status: Draft, paused, closed, archived, or not-ready states can hide or disable public-facing actions.
- Ask an owner or admin: They can review billing, package, team role, and module setup.
What to tell support
- The page or action you expected to see.
- The event name, if it is event-specific.
- Your role name.
- Whether another user in the same organisation can see it.
Common examples
- Ticketing is hidden because the event has not been set up as a ticketed event yet.
- A billing or White Label page is hidden because your role is not owner-level or the feature is not in the package.
- A public action is disabled because the event, form, or checkout is still Draft, Paused, Closed, Hidden, or not ready.