Event Settings is where you configure the core details for each event — things like the event name, client information, session limits, security options, and launch controls. This article walks through every setting so you know exactly what each one does.

Basic Event Details

At the top of Event Settings, you'll find the essential fields that identify your event:

Event Name — the name of your event. This appears in your dashboard, analytics, and any client-facing links.
Client Name — the client or organization this event is for. Useful for keeping events organized when you're running multiple events.
Description — an optional internal description for your own reference.
Start / End Date — the scheduled dates for your event. These are informational and help with organization; your event can still be launched outside these dates.

[Screenshot: Basic event details fields]

Security and Access

These settings control who can access your event and how:

Password

Set a password to protect your event from unauthorized access. When enabled, anyone launching the event on a device will need to enter this password first. This is especially useful for events at shared venues or when your iPad is unattended during setup.

Max Sessions

Set a cap on the total number of sessions (photo captures) allowed for this event. Once the limit is reached, the booth will stop accepting new sessions. This is helpful for managing token usage or limiting activity at an event with a fixed deliverable count.

Data Management

Pictor gives you control over what happens to event data after the event wraps up:

Auto-Scrub Data

When enabled, Pictor will automatically delete captured session data (photos, videos, AI outputs) after a set period. This is useful for privacy-conscious events or clients who require data to be purged after a specific timeframe.

Delete Sharing Data

This setting controls whether guest contact information (email addresses, phone numbers collected at the sharing station) is deleted along with session data. Enable this if your client requires full data cleanup, including guest PII.

Event Code

Every event gets a unique Event Code. This code can be used to quickly load your event on a different device — just enter the code instead of logging in and navigating to the event manually. This is particularly handy when setting up multiple iPads for the same event.

Launch Pad

The Launch Pad section provides everything you need to get your event running on a device:

QR Codes

Pictor generates QR codes that link directly to your event. You can display these on a screen, print them on signage, or embed them in event materials. Guests or staff scan the code to instantly access the event on a device.

Launch Options

From the Launch Pad, you have several ways to start your event:

Simulate — runs a preview of the event workflow without consuming tokens. Use this to verify your setup looks right before going live.
Test — runs the full event experience including AI processing, but marks sessions as test sessions. Tokens are consumed, but test sessions are flagged separately in analytics.
Virtual — launches a virtual booth that guests can access remotely via a shared link. Ideal for hybrid or fully virtual events where guests aren't physically present.

[Screenshot: Launch Pad with QR code and launch buttons]

Control Panel

Once your event is live, the Control Panel gives you a real-time operational view:

Session counter — see how many sessions have been completed in real time.
Active status — confirms the event is running and accepting sessions.
QR code display — a scannable QR code for quick device setup or guest access.
Quick actions — stop the event, view the gallery, or jump to analytics.

The Control Panel is your home base during a live event. Keep it open on a laptop or secondary device so you can monitor activity without interrupting the guest-facing booth.

[Screenshot: Control Panel during a live event]

Tips

Always Simulate first. Before going live, run a Simulate pass to verify your workflow, overlays, and sharing settings all look correct.
Set Max Sessions for token-sensitive events. If you have a fixed token budget, setting a session limit ensures you don't exceed it.
Use Event Codes for multi-device setups. Instead of logging in on every iPad, just enter the Event Code to load the event instantly.
Enable Auto-Scrub for privacy compliance. If your client has data retention policies, configure Auto-Scrub before the event starts.