Logging is an opt-in setting. Enable it in the plugin's options so the log table accumulates rows for SleekView to chart. The retention window should be long enough to cover the time range the dashboard visualises, typically the trailing 30 or 90 days for monthly quota tracking.

Yes. Configure the Number card's target value to match your account's daily or monthly Gmail send quota. The card renders progress as a percentage and turns the number a different colour as you approach the cap, giving a clear quota-aware view of sending health.

Failed sends show up as failed rows in the log with an error indicating the token problem. A Donut spike combined with a string filter on the error column surfaces token issues immediately so the admin can re-authorise Gmail SMTP before customers report missing mail.

Yes. Gmail SMTP supports both personal Gmail accounts and Google Workspace mailboxes with the appropriate OAuth scope. SleekView reads whatever the plugin logs regardless of which account class is configured, so Workspace customers and Gmail personal users get the same dashboard layout.

Yes. If the site uses aliases or multiple authorised from-addresses on the Gmail account, the from_email column on the log table can be charted as a groupBy dimension on a Bar card. That breaks total sends down by sender and surfaces any single alias eating disproportionate quota.

No. SleekView queries the log table on-demand when the dashboard renders, with indexed columns and pagination. The plugin itself adds the row at send time using the existing Gmail SMTP write path, so end-user requests are not affected by the chart layer at all.

Yes. Each chart card exposes its underlying log rows for CSV export with the active filters applied. That gives a clean handoff to Google support or an upstream investigation when a quota incident needs proof across a specific date range and status.

Yes. Each subsite has its own Gmail SMTP log, and SleekView reads the current subsite's table by default. Network-wide dashboards can be configured explicitly when reporting needs to span multiple subsites that share a single Google Workspace domain.