The admin dashboard is the only one with a full sidebar that exposes all eight role modules. Every other role sees only their module. The admin gets a global health overview: revenue today, orders pending, inventory alerts, and support ticket count, all above the fold.

The color accent is Terracotta (brand ember), the same color used for the most important calls-to-action on the consumer store. This creates a subconscious hierarchy: the admin sees the brand's signature color as their primary indicator of urgency and importance.

The designer dashboard is the most visual of all eight. It was designed to feel like a mood board tool as much as a workflow manager. New collection proposals are submitted with color swatches, fabric references, and reference imagery. Approvals happen within the platform, with no email chains.

The dashboard surfaces which collections are in production, which are pending approval, and which have been rejected with feedback. The timeline view is borrowed from project management tools but styled to match the brand, not Jira.

The inventory dashboard leads with a stock health bar: a full-width indicator showing what percentage of SKUs are healthy, low, or critical. This is the first thing the inventory manager sees when they open the platform. No hunting through tables.

Products below reorder threshold are flagged in amber. Out-of-stock products are flagged in red and automatically shown first in the table. The reorder action is a single click, not a five-step form, because the most common action in this role should be the easiest action.

The logistics dashboard is built around a dispatch queue: a prioritized list of orders that need to be packed and shipped today, ordered by promised delivery date. The most time-critical orders surface first. The interface is dense and information-heavy by design: this role does not need visual breathing room, it needs scan speed.

Shipment status uses a five-state pipeline (Pending, Packed, Dispatched, In Transit, Delivered) with color-coded badges. Courier partner assignments are shown inline. The entire dashboard is optimized for keyboard navigation and bulk actions, as the logistics team is processing dozens of orders daily.

Finance dashboards are often overloaded with charts. The Shoonya Finance dashboard was designed on a different principle: clarity over comprehensiveness. The top four numbers (Revenue Today, Pending COD, Returns Value, and Net Receivable) are shown as large typographic values, not sparklines. The chart is below the fold.

COD collection tracking was a specific pain point surfaced during initial conversations. The dashboard has a dedicated COD section with delivery-partner-wise breakdowns and expected settlement dates. Reconciliation discrepancies are flagged automatically with a diff view.

Marketing was the one role where visual data density was appropriate and expected. The dashboard leads with a campaign performance overview in a four-stat hero row: active campaigns, ROAS, email open rate, and conversion rate. Below that, a channel breakdown compares organic, paid, and email performance side by side.

Campaign creation is accessible from the dashboard header. The workflow was designed to match how the marketing manager actually plans: concept first (with copy and creative fields), then channel selection, then scheduling. Not the other way around.

The operations dashboard is the second widest in scope after Admin. The ops manager needs to see the health of every team without having the edit permissions of any of them. The design mirrors a control room: all eight departments visible as health tiles on a grid, with drill-down access to read-only detail views.

A daily ops briefing at the top auto-generates yesterday's summary: orders shipped, stock alerts, tickets closed, campaigns running. No more opening eight tabs every morning.

Support carries the weight of every other team's mistakes. The ticket queue sorts by SLA breach risk, not arrival time - the most common support failure is FIFO handling that lets urgent tickets go cold. Closest to deadline = top of the queue.

Order history, shipment status, and return eligibility are visible within the ticket panel. The support agent never needs to leave the ticket to look up an order. Refund initiation is a single action, gated by a confirmation modal that shows the refund amount and method before executing.