Accounts and projects
This is the path through the browser workspace. If you are a developer running only Godot, see Installation instead.
Sign in or create an account
Open the RODENT portal. Sign in with your email and password, or choose Create an account. The hosted portal uses Supabase Auth. If it asks you to confirm your email, complete that step before signing in. Request password reset sends a recovery link in hosted mode; follow that link to set a new password. The local development account is separate from a hosted Supabase account.
Do not make a second account with the same email to work around a missing profile or project. Ask the project administrator to check the profile and database migrations. If you see Failed to fetch, first confirm that the portal and Supabase service are reachable; this message alone does not prove your password is wrong.
Create a project
Any active account may start a project and becomes its lead for that project. On Your projects, choose + New project. The popup keeps the starting arena and project details together:
- Choose an available arena template. The current integration branch has six validated presets: MCSF, Open Field, Light/Dark Box, T-Maze, Four-Room Arena and Complex Habitat. A deployed version may have fewer until updated. Cards marked planned cannot be selected.
- Enter a project name and optional description.
- Set Project modules. All modules leaves the full set available. A narrower choice, such as Odour only, limits what anyone in that project may customize. Custom modules let you choose several areas.
- Choose Create project. The first experiment is a baseline made from the selected template. Its name can be edited later in Setup.
The project module list is a ceiling, not an automatic permission grant to every member.
Open an experiment
Select a project card. The detail area shows its experiments and team. Choose an experiment card or Open workspace in new tab. The dedicated tab keeps the 3D arena and experiment controls together; the project list remains available in the original tab. If the browser blocks the new tab, the app can open the workspace in the current tab.
An experiment card displays its name, version, status and starting template when the saved configuration includes a template ID. A custom experiment may not have that label.
Add a member and set permissions
The person must already have an active account. In the selected project's Project team section, the lead chooses + Add member, enters the account email, selects a project role and, for a researcher, ticks the modules they may edit. Choose Add to project to save.
| Role | Intended access |
|---|---|
| Project lead | Manages the team and may edit all modules enabled for that project. The account that creates the project starts as lead. |
| Researcher | May edit only the selected modules within the project's allowed modules. |
| Observer | May inspect the project but should not change experiment configuration or save a new run. |
An instructor account has broader course-level access. Project roles are contextual: the same person can lead one project and be a scoped researcher in another. Changing the current lead's role requires appointing a new lead first.
The browser hides controls a member cannot use, but that is not the security boundary. The local backend and hosted database rules must also reject unauthorized writes. If Add to project reports a missing database function, the application migration has not been applied; repeatedly clicking the button will not fix it.
What is not an upload yet
The project detail has labelled places for future rat, sound, light, odour, temperature and treatment models. Dropping a file there currently shows a message only. It is not saved, validated or run. See System Design for the intended model-adapter boundary.
AI Attribution: This guide was drafted with OpenAI Codex assistance from the current website and database interface. The team should check it against the deployed build.