UI and Access Management

Summary
During DAL activation, the interface may appear to require selecting a Launch project even when Launch is not in use. This creates deployment uncertainty.

Root Cause
The issue could not be reproduced; likely caused by client-side caching.

• Clear browser cache.
• Retry activation.
• Validate in an incognito session.

Verification
DAL activates without requiring Launch selection.

Summary
User provisioning for Lytics may be delayed when required administrative approval is unavailable. This impacts onboarding timelines and prevents team members from accessing the platform.

Root Cause
User addition requires explicit organization-level approval and backend provisioning that may not be automated for all account types.

• Obtain written consent from the account owner or authorized stakeholder.
• Escalate the request to Lytics engineering or support for manual user provisioning.
• Verify that the user's email domain matches the approved organization list.

Verification
New users can log in and access Lytics features successfully.

Summary
A user added to Lytics via DAL (Data Access Layer) may be unable to authenticate successfully. This prevents access to segmentation capabilities and platform tools.

Root Cause
The user lacks sufficient organization-level role permissions, or the authentication handshake was not properly completed during the initial setup.

• Validate the assigned Organization Role to ensure the user has "Member" or "Admin" status.
• Generate an OAuth login link or password reset if the standard login flow fails.
• Check for SSO (Single Sign-On) requirements if the organization has them enabled.

Verification
The user successfully authenticates and gains access to the Lytics dashboard.

Summary
Behavioral or interest scores may fail to appear in the Lytics browser extension during testing. This prevents developers and marketers from accurately validating audience segmentation and user profiling in real-time.

Root Cause
The required data fields for scoring were not included in the Public API field configuration, causing the extension to receive incomplete user profiles.

• Access the Lytics dashboard and navigate to the API settings.
• Add the specific score fields (e.g., behavioral, affinity, or custom scores) to the Public API field whitelist.
• Refresh the browser extension to sync the updated configuration.

Verification
User scores are visible and update correctly within the Lytics Dev Tool extension.

Summary
Field mapping behavior during ingestion may cause uncertainty regarding whether configuration should be automatic or manual. This ambiguity can lead to data silos or incorrectly attributed user attributes during the ETL process.

Root Cause
Inconsistent mapping expectations arising from the structural differences between default data streams (which often utilize auto-mapping) and custom data streams (which require explicit schema definition).

• Confirm the specific data source type (e.g., Webhook, S3, or Javascript tag) to determine mapping capabilities.
• Utilize Schema Copilot or the auto-mapping toggle where applicable to streamline field identification.
• Manually define high-priority identity identifiers (email, user_id) to ensure cross-stream stitching.

Verification
Data fields are correctly mapped to the master user profile and are visible within the Lytics profile viewer.