Configuration

Overview

The Configuration page (/{tenant}/settings/configuration) lets you manage tenant-wide settings for violation notifications and privacy. Changes apply to the current tenant only.

Breadcrumbs: Settings → Configuration

URL

Configuration: /{tenant}/settings/configuration

Replace {tenant} with the tenant slug.

Email Notifications

Configure how violation email notifications are sent and who receives them.

Email notification mode

Choose one of:

Option	Value	Description
Send email with photo	SEND_EMAIL_WITH_PHOTO	Include violation photos in email notifications
Send email without photo	SEND_EMAIL_WITHOUT_PHOTO	Send notifications without including photos
Do not send email	DO_NOT_SEND_EMAIL	Disable email notifications for violations

Recipients per location

For each location, you can select one or more recipients (tenant users).
Recipients are team members (tenant users) who will receive violation emails for that location.
Use the location selector and user picker to add or remove recipients per location.
Recipients are stored as tenant user IDs per location ID.

Privacy Settings

Configure how violation photos are handled in the system.

Option	Value	Description
Keep photo	KEEP_PHOTO	Retain violation photos in the system
Remove photo	REMOVE_PHOTO	Automatically remove photos after processing

Saving

The page uses a single configuration form that includes both cards (Email Notifications and Privacy Settings).
Submit the form to save all settings; they are sent to the backend as tenant settings (e.g. update tenant settings API).
Data loaded for the form: tenant settings, locations (for recipient-per-location), tenant users (for picking recipients).

Data model (for agents)

Tenant settings include: emailNotificationSettings (enum), privacySettings (enum), recipientsPerLocation (location ID → array of recipient objects with tenantUserId, email, firstName, lastName).
Update DTO: recipientsPerLocation is sent as Record<string, string[]> (location ID → array of tenant user IDs).