Use the Rivya dashboard to check credits, recent generations, chats, notifications, quick actions, account state, and the next workspace.

Use this dashboard guide after login when you need to check credits, recent work, notifications, quick actions, and the next workspace to open.

Rivya's dashboard is not where you do the work. It is where you regain the picture.

That matters because Rivya is carrying several kinds of state at once:

wallet state
recent generation state
recent chat state
notification state
where the fastest next click probably is

The dashboard exists so you do not have to reconstruct all of that by opening five separate pages.

For most users, the first useful dashboard scan is very short.

Check these in order:

how many credits do I have right now?
what needs attention?
what did I work on most recently?
should I continue an old thread, reopen a generation, or start fresh?

That is the real reason the dashboard combines:

credits
quick actions
recent generations
notifications
recent chats

What the Top Stats Are Really Telling You

The current stat row is more than a vanity summary. It is a quick answer sheet.

It currently surfaces:

current credit balance
recent generation count
recent chat count
number of models used recently

Those numbers answer different questions:

credits: can I start another paid workflow comfortably?
generations: how active has the production side been?
chats: am I mostly still in planning and prompting?
models used: am I exploring broadly or settling into a narrower workflow?

The dashboard matters most when those answers change what you do next.

The quick-action area is the clearest expression of what the dashboard is supposed to do.

It gives direct access to:

chat
image
video
audio
generation history
chat history

That mix is important.

It means the dashboard is not assuming every next step is “start a new task.” Sometimes the right move is:

jump straight into a workspace
reopen recent generation work
reopen the conversation layer first

So quick actions are less like a menu and more like a way to regain momentum.

Recent Generations: “What Happened to My Last Runs?”

The recent generations section is the fastest place to answer:

did the last run finish?
which model was it on?
do I want to reopen that workflow?

It is intentionally not trying to replace History. It is the short operational layer, not the long archive.

Use the dashboard version when you want:

the latest few runs
a fast reopen path back into the workspace
a quick sense of whether the recent work went well

Use full history when you want broader review, filtering, and deeper re-entry into older work.

Recent Chats: “What Was I Thinking About?”

The recent chats section solves a different problem from recent generations.

It helps you remember:

what you were planning
which conversation already has context
whether a recent tool thread is worth continuing

That matters because a lot of Rivya work starts in chat before it becomes:

an image task
a video task
an audio task
a structured reasoning thread

This is one of the clearest places where the dashboard works as a way back into context instead of a generic homepage.

Notifications Preview: “What Needs Attention Right Now?”

The notifications preview exists because the next action is often driven by operational events, not by creative intent.

For example:

a payment failed
credits ran low
a generation failed
a generation succeeded

The dashboard preview is the short version. Notifications Center is the longer record.

Use the dashboard when you need:

a fast “do I need to handle something?” answer
unread awareness
a quick jump into the related page

Use the full notifications page when you need the more complete event history.

Dashboard vs Studio Is Really “Orient” vs “Work”

This is still the cleanest split:

dashboard helps you orient
studio helps you work

Use the dashboard when you need the current product picture.

Use studio when you already know the workflow and want to stay inside the task.

Three Good Dashboard Habits

The dashboard becomes more useful when you use it for the right moments.

If you are not already deep inside a specific project, start at dashboard after login. It is the fastest way to catch up on wallet state, unfinished threads, and recent outcomes.

Habit 2: Return after a heavier run

If you just finished a costly image or video session, coming back to dashboard is a clean way to see:

what the balance looks like now
whether the recent task settled cleanly
whether anything else needs attention

Habit 3: Use it to decide between “continue” and “start fresh”

The dashboard is most useful when you are deciding:

continue a recent chat
reopen a recent generation workflow
or start a brand-new workflow from a quick action

A Better Mental Model

The dashboard is not the center of the product because it does everything.

It is the center because it answers one important question very quickly:

What should I do next, given the current state of this account?

That is the level to read it on.

Dashboard Flow Checklist

This checklist clarifies what the signed-in home screen is responsible for:

Use Dashboard for orientation: recent work, wallet state, notifications, and next actions.
Send model-specific creation into Studio, not the Dashboard itself.
Use History for completed or failed outputs.
Use Notifications when the issue is asynchronous status or billing events.
Use Settings when the task is account, billing, security, or credits management.

Recheck When The Next Action Is Unclear

Recheck if Dashboard is open but the actual issue belongs to history, notifications, settings, payment, or a specific Studio. The dashboard is a routing surface, not the whole workspace.

Rivya Dashboard Guide