Eden Omni Training — FAQ
Do we need to buy seats for everyone?
No. Most stakeholders should be Viewers (consume dashboards, export, schedule, alerts). Keep Standard seats for the people who truly build charts/dashboards. Keep Developer seats limited to platform/model owners.
Why does seat type matter?
Capabilities differ:
- Viewer: consumption + operational workflows (exports, schedules, alerts)
- Standard: building + AI + context editing
- Developer: modeling, connections, permissions
Who should get AI features?
Start with:
- builders/analysts who will use AI regularly and can sanity-check outputs
- a small number of power stakeholders if they will actually use it
AI usage consumes tokens from a monthly budget (does not roll over).
What are tokens?
Standardized units of AI consumption (e.g., natural language questions, AI summaries). Tokens are budgeted monthly.
What is a Topic?
A Topic is a curated dataset (joins + definitions + governance). It’s the foundation for self-serve charts and reliable AI.
Can different teams have different metric definitions in different Topics?
Avoid it. Keep core definitions consistent across Topics. Different “starting points” by team are fine; conflicting definitions are not.
How do we keep familiar dashboards during Tableau → Omni?
Prioritize the dashboards used daily (P0). Validate that they match expectations first, then iterate.
What does “turning snapshots into a workflow” mean?
Replace screenshots and manual Slack posts with:
- scheduled PDF/CSV deliveries to Slack/email
- alerts when thresholds are crossed
This improves reliability and can reduce seat pressure.
If someone can’t export/schedule, what do we do?
It’s usually a permissions or seat-type issue. Confirm whether they are a Viewer vs Standard and whether deliveries/exports are enabled in your Omni settings.