Admin Console for Complete Control

A visitor experience admin console is the administrative workspace used by authorized venue teams to manage supported parts of their digital visitor experience. In Pigeon Suite, the admin console can bring together functions such as content management, user administration, configuration, analytics access, and supported operational settings in one place.

The exact tools depend on the deployment. Supported areas may include visitor-facing content, locations, events, media, navigation items, feature settings, administrative users, and analytics or reporting access. The implementation should clearly define which modules each venue can manage directly.

The Admin Console is the broader administrative environment. Content Management is one capability within that environment and focuses specifically on creating, organizing, editing, and publishing visitor-facing content. Other admin functions may include user access, configuration, analytics, and operational controls.

The Pigeon Suite Admin Console is intended to give authorized venue staff a practical way to manage supported functions without working directly in application code. The exact workflow, training, and permissions depend on the modules enabled for the organization.

Yes, multiple authorized users can be supported when user administration and role-based access are configured. Each person should receive only the permissions appropriate to their responsibilities.

Many content and configuration changes can be delivered through the platform without requiring a new binary app-store release when those items are designed for dynamic management. Changes to native application code, operating-system requirements, or certain features may still require a formal app release.

Where Visitor Analytics is included, authorized users can access the supported dashboards and reports made available for their deployment. The exact metrics depend on the analytics events and data sources configured for the experience.

Administrative access should be limited to authorized users and governed by the security, authentication, roles, and permissions configured for the deployment. Organizations should define who can view, edit, approve, or publish information as part of implementation.