Personal dashboard

Your URS control room starts at the account layer.

This shell keeps the first view centered on the signed-in person, then separates the related identity layers so account, avatar, character, and faction do not blur together.

Identity layers

Separate the objects before adding project workflows.

Account

Verified login and ownership

The account is the authenticated person layer. It holds email confirmation, subscription state, and access control.

Avatar

Second Life identity surface

The avatar is the in-world identity layer. It can be linked to an account, but it is not the same as the account.

Character

Roleplay persona and history

Characters live inside a project context. Drafts, approvals, and character history belong here, not on the account.

Faction

Scoped group authority

Factions are project-local groups with explicit permissions. They should never become global admin shortcuts.

Launch checklist

What the first usable dashboard should guide next.

  • Confirm email before full access
  • Finish personal profile and avatar links
  • Create a first character draft
  • Join or manage a faction inside a project
Reserved tools

Space for project operations without crowding the home view.

  • Project switcher and tenant context
  • Membership management and approvals
  • Faction administration and scoped roles
  • Export, deletion, and reporting workflows
Next step

Build the signed-in dashboard around confirmed email and profile completion.

This shell is intentionally generic until the auth flow, account state, and project membership data are wired in.