Profile Panel: Shows your email and org role for quick confirmation of access level.

Integrations (Google/Meta/Bing): Connect or reconnect Google Business Profile, Meta (Facebook Pages), and Bing Places. Meta offers Diagnostics; Bing supports manual "Sync Now". Google uses the standard Connect button for tokens.

Store Locator Widget: Configure the embeddable store finder (search + geolocation) for your website. Each store card now displays a cover image (satellite map pin of the exact location) and top review snippets. The detail view shows up to 5 recent reviews with star ratings, reviewer avatars, dates, and comments.

Review Perks Branding: Use Settings > Review Perks Branding to choose whether the logo appears on public perks pages, select brand logo mode (domain whitelabel logo) or account logo mode (custom URL), configure overrides per GBP account for multi-account organizations, and set Customer Satisfaction submission notification recipients.

Partner Agency Domain Verification: In Admin > Partner Agencies, domain status is now system-managed. Managed subdomains under profilepilotapp.com are auto-verified, and external custom domains are verified against Firebase Hosting using the "Verify with Firebase" action.

Billing User Notifications Access: bookkeeper users can access Settings and update their own notification preferences from Settings > Notifications, while broader integration/admin settings remain hidden for that role.

Notification Preferences: Per-user controls for review alerts (with star rating filters), weekly reports, email alerts, and product updates.

Daily review digests are sent by email when Review Alerts, Email Notifications, and the Daily Review Digest toggle are enabled. Digests are filtered by your selected star ratings.

In-app notifications are generated when new reviews are synced; ensure review syncs are running to see updates in the notifications center.

Review.new notifications are now generated by the reviews insert trigger to avoid duplicate event writers; sync routes no longer create a second new-review event for the same review.

The review-event backfill cron now skips legacy-equivalent rows (including Store-code title variants) so it does not recreate duplicate review.new events after cleanup.

If older data still contains duplicate review.new rows with different non-null keys (for example legacy:* plus google:*), run the cross-key cleanup migration to normalize obsolete keys and remove twin rows.

Notification digest emails exclude review.reply.imported entries to keep mail summaries focused on actionable items while those events remain visible in-app.

Digest emails now use an executive-style layout with a "Your daily digest" heading and "View Reviews" CTA while preserving the full per-review detail list in the email body.

Digest layout refinements: reduced grey spacing, centered summary heading block, "New Reviews" section label, centered CTA with more padding, and smaller footer disclaimer text.

Digest delivery is role-aware: for example, bookkeeper members receive finance/system digest content only.

Email digests are scoped per user: each user receives their own unread events plus organization-level events (not other users' private events).

For troubleshooting, cron digest routes support targeted runs with query params such as orgId, userId, sinceHours, period, and maxEvents.

If you haven't saved preferences yet, digest emails default to enabled. Turning off Email Notifications or Weekly Reports disables digest sends for that user.

Subscription Toggle: Enable or pause your Paystack subscription from Settings; shows current status and handles enable/disable calls.

Scoped Manager Assignments: In Settings > Permissions > Bulk Invite and Admin > Team, admin/customer/customer_manager/campaign_specialist can grant or update region/store scope IDs for existing customer_region_manager and customer_store_manager users.

User Management (Admin > Team): Admins can view all current organisation members in Admin > Team. Each row shows the member's name, email, role, active/deactivated status, and last sign-in date.

Deactivate a User: Click the Deactivate button next to any member to immediately block their dashboard access. Deactivated users are redirected to an Account Deactivated page when they try to log in. The member record is preserved — you can reactivate at any time.

Reactivate a User: Click Reactivate next to a deactivated member to restore their access instantly.

Remove a Member: Click the trash icon to permanently remove a member from the organisation. A confirmation prompt prevents accidental removal. This cannot be undone.

Self-Protection: Admins cannot deactivate or remove their own account from the member list.

Scoped Manager Invites: customer_manager can invite customer_region_manager and customer_store_manager users for day-to-day delegation. Inviting customer_manager itself remains restricted to admin/customer/campaign_specialist.

Campaign Specialist Invites: Creating campaign_specialist invitations is handled in Admin > Team. Settings > Permissions > Bulk Invite intentionally excludes campaign_specialist from role options.

Location-Only Scope IDs: Region/store manager scope assignments now use location resource IDs only (accounts/{accountId}/locations/{locationId}) selected via account-first location pickers.

Scoped Reputation Visibility: Region/store managers now only see Google Account / Brand filters and reputation data that map to their assigned scoped locations.

Store Scope by Name: Scope can be selected by location name (with store code/city context) so teams do not have to manually type raw location IDs.

Account-First Scope Picker: For large datasets, select the account first, then search/select locations by name to avoid long unfiltered lists.

Region Scope Source: Region manager assignments now use location-based selection mode (manual geo-key mode removed).

Address Quality Audit: Admin > Address Quality flags locations missing country/region/city/suburb fields to help clean and standardize geo data for scope governance.

Local vs Prod Base URL: Dev calls use NEXT_PUBLIC_BASE_URL (e.g., http://localhost:3001); prod uses NEXT_PUBLIC_APP_URL.