Rivya Pages, Sign-In, and Saved Work
Learn what you can do before signing in to Rivya, how to protect a draft during login, and how to upload, run, and resume work in the right account.
Last reviewed on September 9, 2026
You can explore Rivya without an account, then sign in when you are ready to send a message or run a generation. A public page can also contain a working form: after sign-in, supported forms run on that same page. Studio is the account workspace, not a required detour for every request.
What You Can Do Before Signing In
Browse Chat, Image, Video, and Audio, compare the model catalog, or look through tools. Where a form is provided, you can prepare text before signing in. Browsing and typing do not submit a generation or use generation credits.
The prompt library and showcase offer starting points and examples. Copying a prompt saves its text to your clipboard; using a template opens its starting page. Neither action automatically runs a paid task. Check the selected model and any prefilled content yourself, because a template is not a complete saved project or a promise to reproduce its example.
What Requires an Account
| Action | What to expect |
|---|---|
| Send a chat message or run a generation | Sign-in, model availability, valid inputs, and sufficient credits are checked |
| Upload a supported reference or chat attachment | Sign-in is required; the current model and form determine accepted files |
| Open Studio, History, notifications, or settings | These are signed-in account areas |
| Resume a saved conversation | Use the account that owns it and open the matching conversation |
Signing in does not unlock paused models or coming-soon tools. The availability guide explains those states; account access covers the supported sign-in methods.
Protect Your Draft Before Signing In
A return link tells Rivya which page to open. It is not a backup of everything you have typed or selected. Login can reload the page, and some public forms return to the page path without keeping all query details. Unsent text, parameter choices, and files should not be assumed to survive.
Copy your prompt or message to a local note before opening sign-in. Note the model and important settings, and keep the original files.
Complete sign-in with the account you intend to use. If you land on a different page, reopen the original model or tool page.
Check the selected model, paste any missing text, and restore the settings you need. Do not assume login has submitted the request.
Upload any required files using the signed-in form, wait for completion, and confirm the displayed references. Follow the upload requirements for that model.
Review the estimated credits, then send once. The credit guide explains reservations and final settlement.
A browser reload or an interrupted return does not establish whether a request already submitted earlier succeeded. Check saved work before sending it again.
Choose the Public Form or Studio
Stay on a supported public form if you have found the model or tool you want and are ready for a first request. Use Studio when you want the account workspace for ongoing work and model selection. Both require the same signed-in account context for execution; changing pages does not create a separate credit allowance.
Moving into Studio may carry a prompt or a supported reference through a link, but it does not transfer every parameter, attachment, or result. Check the new form before submitting. Likewise, opening a category can choose an available default model rather than restore your previous session. Read the getting-started guide for a focused first run.
Resume the Work You Actually Saved
Use History to find the relevant task or conversation. For chat, open the saved conversation and wait for its messages to load before sending a follow-up. A generic chat or tool page is not the same as your saved conversation; the saved-session guide explains how to continue it.
For a media task, check its status before retrying. Reopening an input form is preparation for another task, not proof that the earlier one failed. Keep important files locally using the download guide: saved history is not permanent storage for every output or unsent draft.
If Login or the Return Page Gets in the Way
Your draft is missing: reopen the intended page and paste your local copy. Sign-in does not recover text that was never saved.
An attachment control is missing or unavailable: confirm you are signed in and that the current model supports that input. Changing pages does not add file support.
A saved conversation is missing: check that you used the original account and opened the correct conversation. A private session link is not a public sharing link or access to another account's work.
You are unsure whether a submitted task ran: inspect History and your credits before retrying. Do not create a duplicate merely because the browser returned somewhere unexpected.
For persistent errors, follow troubleshooting. Keep the page address and any task or session identifier when asking for help, but do not send passwords, verification codes, or API keys.