Dashboard overview
The DNotifier dashboard at app.dnotifier.com is your control center for apps, monitoring, and plan management. This page describes each major section conceptually so you know where to look as you build.
Apps
The Apps section is where you create and manage DNotifier applications.
Each app represents one product or environment (for example, "Production Chat", "Staging AI Assistant"). Every app has:
A unique appId β public identifier used in SDK configuration
An app secret β private credential used during authentication
Optional settings and metadata visible in the dashboard
You typically create at least two apps in production: one for production traffic and one for development or staging. Never share secrets between environments.
See Create an app for the step-by-step flow.
Logs
The Logs section shows AI session activity when you enable logs: true on the SDK constructor. Event types you may see include:
AI session start and completion events
Token usage summaries
Model used for the call (
sendAI/ agent override, or project default)
Logs help you debug assistant behavior, audit usage, and correlate SDK calls with user sessions.
β How to enable session logs
Workflows
The Workflows section visualizes multi-step AI pipelines that use DNotifier's workflow and agent APIs.
When you run a workflow with observability: true, the dashboard shows:
Workflow name and description
Individual execution runs (
executionId)Steps inside each run (AI calls, searches, custom steps)
Status (running, completed, failed) and timing
Provider / model on AI steps when set
This is especially useful for intent routers, RAG pipelines, and multi-agent content workflows where you need to see what happened inside a single user request.
β How to enable AI workflow observability
AI Studio β Providers
Open a project, then go to AI Studio β Providers. Thatβs where provider connections live β OpenAI keys, Anthropic, Gemini, Hugging Face, Perplexity, Azure endpoints, Bedrock creds, Ollama URLs, and subscription-backed options when your plan has them.
Path: Projects (pick the project) β AI Studio β Providers β (OpenAI, AWS Bedrock, β¦).
Once a connection is saved, code just passes provider and model on sendAI. Keep secrets out of the repo.
More detail: multi-model docs.
Usage
The Usage section tracks consumption against your plan:
Message volume (realtime sends and related traffic)
AI requests and word/token consumption
Knowledge-base storage
Active users or rows, depending on plan tier
Usage updates as your SDK connects and sends data. Check here regularly during development to avoid surprise limit errors in production.
Plan & limits
The Plan & limits area (sometimes grouped under billing or settings) describes what your subscription allows:
Message hard limit
Maximum messages per billing period
Message size
Maximum payload size per message (also returned at connect time)
AI enabled
Whether sendAI and related APIs are available
AI requests / words
Monthly AI call and word quotas
Knowledge base words
Total indexed content capacity
Max users / rows
User or data-row caps per app
When your SDK calls connect(), many of these limits are returned in the auth response and exposed via getPlanLimits() in JavaScript and Dart. The dashboard is the source of truth for billing; the SDK mirrors limits for runtime checks.
How the sections work together
You create an app and copy credentials into your project.
The SDK connects and receives plan limits.
Your app sends messages, AI requests, or runs workflows.
Usage increments; Logs and Workflows capture optional telemetry.
Next steps
Create an app β Generate credentials for your first app
Credentials & environment β Store
appId,secret, anduserIdsafelyInstall an SDK β Add DNotifier to your project
Last updated