MetaPlexus Admin Panel

1. Overview

What the Admin Panel is, and what you can do with it.

The MetaPlexus Admin Panel is the central control surface for your Mytaverse world. From here, administrators configure the visual identity of the world, publish and approve new game builds, schedule and launch immersive experiences (events, demos, training sessions, hubs), manage guests and team members, and monitor usage analytics.

At a glance

The six primary sections

Every page of the Admin Panel keeps the same top-of-page navigation row. The currently selected section is highlighted with a purple border.

2. The Interface

How the Admin Panel is laid out, and how to get around.

Top header bar

• Mytaverse logo (top-left) — returns you to the home Dashboard.
• Greeting — displays your name and the prompt “What would you like to do next?”.
• Clock and date (top-right) — current time with time zone indicator (e.g. UTC-4).
• My Account (person-with-gear icon) — opens your personal account settings.
• Sign Out (door icon) — ends your admin session.

Section navigation

Below the greeting, six large cards switch between the Admin Panel's primary sections. The selected section always shows a purple glow and border. Clicking a card either navigates to the section directly (e.g., Builds & Releases, My Experiences, Manage Members, Analytics) or opens a quick sub-menu (Settings & Appearance).

Content area

Every section renders a white content card that includes:

• A title and context (for example, "Experiences Dashboard" or "UE Server Builds Dashboard").
• A search field for finding items by name.
• A primary action button in the top-right — the most common next step, such as Create Map, Add Experience, Invite Team Member, etc.
• One or more sub-tabs for related views (e.g. Maps / UE Server Builds / UE Client Builds / Releases).
• Filter pills below the tabs for narrowing the current list.
• A data table with sorting, per-row menus (⋮), and pagination.

3. My Account & Sign Out

Manage your personal admin profile and session.

Opening My Account

Click the person-with-gear icon in the far top-right of any page. A modal titled My Account opens with the following editable fields:

Click Save Changes to persist updates, or Cancel to close without saving.

Signing out

Click the door / arrow icon next to the My Account icon. You will be returned to the login screen at admin.dev.mytaverse.com/login.

4. Dashboard

The home screen. A real-time snapshot of your world.

The Dashboard is the first page you see after signing in. It summarizes everything happening across your world and gives you quick entry points to deeper sections.

Overall Statistics

Four key figures are pinned to the top of the Dashboard:

Experiences in this project

A scrolling list of the latest experiences. Each row shows a thumbnail, the experience name, the publish date (or start/end window), and a status badge. Click View Full List to jump into My Experiences. The ⋮ menu on a row reveals contextual actions (e.g. open, duplicate, delete).

Active Users per Experience

A bar chart grouped by month. Hover any bar to reveal the exact number of active users for that experience and time bucket.

Team

A compact list of your most active team members with their primary role (ADMIN, MEMBER, or both). Click View/Manage Team to jump into Manage Members.

Admin Panel Walkthrough

An interactive guided tour that explains every tool available to administrators. Launch it any time you need a refresher, or to onboard a new teammate.

5. Settings & Appearance

Customize the look, feel, and baseline configuration of your world.

Clicking the Settings and Appearance card opens a modal titled Customize Your World — What would you like to change in your world? with two options:

Click Cancel (or the ✕ in the top-right of the modal) to close without choosing.

6. Builds & Releases

The publishing pipeline: Maps → Server Builds → Client Builds → Releases.

This section is where engineering deliverables become playable content. It uses four sub-tabs to represent the pipeline.

6.1 Maps

A Map is a single Unreal Engine level — for example Map_MytaCore_ShowCase, Map_SpiralMuseum, or Map_BaseLevel. Maps are the smallest unit that an experience can point at.

What you see

• Search maps… — quick name search.
• + Create Map — register a new map in the system.
• Table with thumbnail, name, and “Created X days ago”.
• Rows per page (5 / 10 / 25 / 50 / 100) and pagination.

Common actions (⋮ menu)

• Open map details / thumbnail.
• Rename or edit metadata.
• Delete (if permitted by role).

6.2 UE Server Builds

A UE Server Build is the packaged dedicated-server binary that powers a multiplayer experience. Each build has a version, a build type, a set of maps it supports, and a lifecycle status.

Columns

Filters

• Build Type: Development · Shipping.
• Status: Ready · Deleted.
• Approved only — shows only approved builds.

The primary action is + Create UE Server Build, which walks you through registering a new server binary (typically produced by CI/Jenkins).

6.3 UE Client Builds

A UE Client Build is the client-side streaming package that guests actually see. It runs on the pixel-streaming infrastructure (for example, the PROTON (20250516) runtime). Client builds are paired with server builds and target the same version/branch.

Additional columns vs. server builds

• Name or ID — both a human label and internal ID.
• Runtime environment — e.g. PROTON (20250516).
• Application — internal pixel-streaming application ID (e.g. a-krl70ij0B).
• Created — absolute timestamp (date and time of day).

Filters and the primary action mirror Server Builds: + Create UE Client Build.

6.4 Releases

A Release binds an Event (experience) to a specific server version and client version, producing a deployable stack that guests can join.

Columns

Filter pills

Active · Initialization · Failed · Deleted. Combine pills to build any subset.

7. My Experiences

Create, configure, schedule, and run the interactive experiences your guests will enter.

My Experiences is the operational heart of the Admin Panel. An Experience is a joinable instance of your world — think of it as a scheduled event, on-demand hub, or one-off demo.

The Experiences list

Top bar

• Search experiences…
• + Add Experience — the primary action.
• View Past Experiences — toggle to show historical events.

Filter pills (Build Type)

Scheduled · MultiPlayer · OnDemand · SinglePlayer · SCHEDULED · FullTimeHub · ON_DEMAND · plus any custom tags you've created (e.g. nado-teg, sate-ed).

Columns

Creating a new Experience — the wizard

From the Experiences list, click + Add Experience to open the creation dialog. You'll be asked first whether to Create New from scratch or Clone Existing. The sections below cover the full Create New path; cloning is documented in the next section.

Cloning an existing Experience

Cloning produces a copy of an experience with a (Clone) suffix on its name. All runtime settings — 3D space, avatar system, tags, invite slots, customization images — carry over. The clone is a brand-new record with its own ID, machines, and lifecycle.

Inviting Participants — step by step

You can invite participants in two places: during the Create Experience wizard (Step 4), and from Participants in the Experience Dashboard at any time afterwards.

From the Experience detail page

1. Open the experience via Setup on the Experiences list.
2. Click the Participants tab.
3. Click + Invite Member (top right). A side panel/dialog slides in.
4. Type a name to match an existing world member, or a full email address for an external invite.
5. Optionally assign a role — FACILITATOR (moderates chat / media) or EXPERIENCE_MEMBER (standard guest).
6. Press Enter or click Add to queue the invitee. Repeat for more people.
7. Click Send Invites to dispatch email invitations and update the participant list.

Statuses and what they mean

• Confirmed Presence ● — invitee accepted and will appear in attendance totals.
• Pending Confirmation ● — invitation sent but not yet accepted. You'll see them in Pending counters until they confirm.

Bulk invites

Need to invite dozens or hundreds at once? Use Manage Members → Invite Team Member to add people to the world first, then select them by group in the experience's invite panel. You can pre-assign everyone in a Member Group (e.g. Sales Team) to an experience through the group selector.

7.1 Experience Dashboard (Setup)

Click Setup on any row — or the three-dot menu → Open — to enter the per-experience control surface. Seven tabs appear below the experience's title and ID:

What's on the Dashboard tab

• Experience Statistics: current status, invited participants count, start date, end date.
• Server Machines: regions active, with a Configure action.
• Rooms list (preview): each room's name and map, with Configure.
• Participants list (preview): names, emails, and View Full List.
• Experiences List back-link returns to the main list.

7.2 Rooms

A Room is a specific map instance inside an experience. A simple experience contains one room; a campus or conference contains many. Each room shows its map, default / active status, and a Customize button that opens the room's look-and-feel editor.

7.3 Participants

Displays every person invited into this experience.

Views

• All Participants (default)
• Confirmed Presence — attendees who have confirmed.
• Pending Confirmation — invites not yet accepted.

Actions

• Invite Member — adds a person to the experience. Can target existing world members or external email addresses.
• View user info (per row) — opens the participant's details and role for this experience.

Experience-level roles

• FACILITATOR — moderates chat, media, and attendees.
• EXPERIENCE_MEMBER — standard participant.

7.4 Customization

Override the global Design for this single experience.

General Imagery

Each asset has an Upload Image button and, when populated, a Delete control.

Loading Screen Settings

• Media Type — e.g. YouTube Video.
• YouTube URL — the video shown while guests wait for the server.

Navigation Settings (PC)

• Navigation mode — e.g. Keyboard + Mouse.
• WASD — press and hold W/A/S/D to move.
• Right-mouse drag to look around.

These settings affect PC devices only — mobile navigation is predefined by the platform.

Additional Assets

Upload images, videos, audio, and 3D assets consumed by the experience. Filter by Image · Video · Audio · 3D and use + Add Asset to upload new files. Each asset has Name, Type, Asset Type, Section (placement hint), and Tags.

7.5 Avatars

Enable avatar systems guests can use inside this experience. Current options:

Each provider has an Information button that explains what guests see and how to configure it.

7.6 Machine Scheduler

Reserve and orchestrate the cloud GPU machines that power live sessions.

General Information

• Stream Class (e.g. gen4n_ultra) and overall status ACTIVE.
• Always On count vs. On Demand count.
• Ready / In Use / Allocated live gauges.

Per-region capacity

For each AWS region (e.g. N. Virginia, Ohio), see:

• Always On Capacity: Provisioned, Ready, In Use, Allocated.
• OnDemand Capacity: Provisioned, Allocated.

Calendar

A full calendar (Agenda / Month / Week / Day / Logs) shows scheduled machine blocks by the hour. Use Schedule Machine in the header to book additional capacity for a window.

7.7 Experience Settings

The most granular control surface in the Admin Panel.

General Settings

• Disabled keys — keyboard shortcuts that should be ignored in this experience.
• Tags — freeform and system tags (e.g. ON_DEMAND, MultiPlayer). Save with Save Tags.
• Invite Slots Tags — tag-based slot gating.
• Max Participants — hard cap. Locked after publish.
• Expected Percentage Of Participants — drives Always-On capacity (default 100%).

AI Assistant

• Virtual Assistant Name — default Noa.
• Base language — primary spoken/written language of the assistant.
• Additional languages — choose any subset of: Arabic · Chinese · Czech · Danish · Dutch · English · Finnish · French · German · Hindi · Icelandic · Italian · Japanese · Korean · Norwegian · Polish · Portuguese · Romanian · Russian · Spanish · Swedish · Turkish · Welsh.
• Use user profile language — auto-matches each guest's preferred language.
• Test voice audio — preview the synthesized voice using Engine, Language, and Voice selectors (e.g. Engine: generative, Voice: Ruth).

Timers

• Idle Timer — auto-disconnects inactive guests after a threshold (off by default).
• Average Event Load Time to 100% — historical load times, broken down by GPU allocation (0–75%), UE client start (75–90%), and asset loading (90–100%).

Server Configurations

• Suspend After Publish — if enabled, the experience starts in a suspended state after publishing (useful for rehearsals).

8. Manage Members

People, groups, and permissions across your world.

Manage Members is the people-layer of the Admin Panel. It has three tabs:

Team Dashboard summary

Pinned to the top: Total Population · Administrators · Confirmed Members · Pending Members · Member Groups. The primary action is Invite Team Member.

8.1 Members

Filters and search

• Search by name or email…
• All Participants dropdown — filter by state (e.g. confirmed, pending).

Columns

8.2 Member Groups

Groups bundle members so you can manage their access and invitations in bulk. Each group row shows:

• Participant Group name and status (e.g. ACTIVE).
• Members count.
• Invited Experiences — which experiences the whole group is automatically invited to.
• Configure — edit membership, invitations, and tags.

Use Create Group (top-right) to start a new group.

8.3 Roles & Permissions

Roles are divided into two families: Admin Roles (platform-level) and Experience Roles (per-experience).

Admin Roles — platform management matrix

Experience Roles — participant permissions matrix

Adding a new role

Click + Create Role in either family, enter a name, and toggle each capability to Full, Partial, Write, Read, or None. Use Compare to see how your draft stacks up against the existing roles.

9. Analytics

Usage, sessions, devices, and GPU allocation trends.

Overall Numbers

• Session Time — Max Time: the longest single session recorded in the window, plotted over time.
• Session Time — Average Time: mean session length, plotted over time.
• GPU Allocation — Max Time: longest GPU reservation.
• GPU Allocation — Average Time: typical GPU reservation length.

Users / Device

Breakdown of guests by device class — Mobile, Desktop, Tablet — expressed as percentages. (Example at time of writing: Desktop 99.8%, Mobile 0.2%, Tablet 0.0%.)

Active Users per Experience

Bar chart grouped by month. Use the experience and month selectors above the chart to drill in. Hover any bar to see the exact user count.

10. Row Actions & Modals Reference

Every kebab (⋮) menu, confirm dialog, and per-row modal captured directly from admin.dev.mytaverse.com on 2026-04-23. Each subsection has its own Try-it-live launcher.

10.1 My Account modal

Triggered by the top-bar avatar + gear icon. Modal title My Account. Editable fields: User Name, E-mail Address, Gender (Male/Female radio pair — Male shown with purple-outlined pill), Password (masked, with inline Reset Password link). Footer: Cancel / Save Changes.

10.2 Sign Out

The right-most top-bar icon (door + arrow) ends the session immediately — no confirm dialog. You land on the login page.

10.3 Maps — row kebab & modals

Each row ⋮ exposes Edit and Delete.

Update Map modal

Title Update Map. Fields: Map Name * (placeholder Room name), ueIdentifier *, Map path *, Map Thumbnail (Upload Image + Delete), Teleport previews with Manage button (disabled when no preview data). Footer: Cancel / Save.

Create Map modal

Same schema as Update Map, with the thumbnail placeholder reading "No image selected" and no Delete button for the thumbnail.

Delete Map dialog

Title Delete Map. Body: "Are you sure you want delete {Map Name} Map?" (known copy issue — missing "to"). Buttons No / Confirm.

10.4 UE Server Builds — Gamelift modals

Row ⋮ exposes only Edit. The Update / Create Gamelift Build modal contains: Build Name *, Build type (DEVELOPMENT / SHIPPING), Approved (checkbox), Linux Type (AL2023 (x86) / AL2023 ARM), Region *, Status *, Server Changeset *, Instance Type *, Launch Path *, Build URI *, Tags (chip input), Maps (chip input). Footer: Cancel / Save.

10.5 UE Client Builds — Pixel Streaming Client modals

Row ⋮ exposes only Edit. The Update / Create Pixel Steaming Client modal (typo in the live UI: "Steaming" — logged for engineering) contains:

• Top: Client Type, Event ID, Build type, Approved, Client Changeset, Name, Description.
• Client Params: Runtime environment type (e.g. PROTON), Runtime environment version (e.g. 20250516), Build URI, Executable Path (e.g. Mytaverse.exe), Application ID + REMOVE APPLICATION button, Region, Stream Class (e.g. gen4n_win2022).
• Chip inputs: Maps, Additional Launch Args, Log locations, Tags.
• Resources: read-only list of runtime resource paths (Update modal only).

10.6 Releases — row kebab

Row ⋮ exposes Activate, Republish, Delete. The Delete release confirm dialog uses the release UUID in the copy (e.g. "Are you sure you want to delete 8d7aa3ac-21c9-46bb-8143-2c72ef21c3fa release?"), with NO / YES buttons.

Filter chips on this tab: Active · Initialization · Failed · Deleted. Status pills: ACTIVE (green ✓), INITIALIZATION (yellow), FAILED (red ⓘ), DELETED (grey •••).

10.7 Members — row kebab actions

Row ⋮ exposes five actions: Edit member, Change Role, Change Password, Assign Groups, Remove User.

• Edit member → Update Member modal — Participant Email, Participant Name, Gender (Male/Female radios), Navigation Mode combobox, WASD illustration with copy: "Press and hold W to move forward…", "Click and drag using the right button of the mouse…", "The settings above affect only PC devices. The navigation for mobile is pre-defined."
• Change Role → four selectable role cards: SUPER_ADMIN, ADMIN, MODERATOR, MEMBER (no Guest).
• Change Password → Update Participant Password modal with header "Change password for {email}", Generate Password purple CTA, Password + Confirm Password inputs.
• Assign Groups → multi-select checkboxes for all 5 groups (Myta UE Team, Myta Web Team, Facilitators, Attendant, Material handler).
• Remove User → Remove Member confirm dialog: "Are you sure you want to remove {email}?" with Cancel / Remove (purple). Copy inconsistency: menu label says "Remove User" but dialog title says "Remove Member".

View user info drawer

Opened from the Actions column link. Read-only User Information dialog with: avatar + display name, Status (Inactive/Active/Pending), Email (with copy icon), Gender, Role, and User ID UUID.

10.8 Invite Team Member modal

Horizontal row with Email (required), Name, Gender (Male/Female). + Add another member link to extend the list. Footer: Cancel / Invite Members.

10.9 Member Groups — Create & Configure

Create user group

Modal: Group Name (text) + Status select (ACTIVE default, with ⓘ tooltip). Cancel / Create Group (disabled until name populated).

Configure: {Group Name}

Three sub-tabs:

• Group Details — Group Name (pre-filled) + Status (ACTIVE) with ⓘ tooltip.
• Members — Add Member CTA, table with MEMBER/ROLE/ACTIONS columns, role select options SUPER_ADMIN/ADMIN/MEMBER, pagination Rows per page: 10 | 1–1 of 1.
• Experiences — Add Experience CTA; empty state "This group is not invited to any experience yet."

Persistent footer: Cancel / Save Changes.

10.10 Dashboard — captured widgets

Canonical widget order (left→right, top→bottom):

1. MYTA-DEV Analytics header (world name + "Analytics" subtitle).
2. Overall Statistics 2×2 KPI block: 36 Total Population · 5 Active Servers · 5 Active Experiences · 23 Inactive Experiences.
3. Experiences in this project — scrollable list with View Full List link; each row: Status pill + thumbnail + title + date + ⋮.
4. Active Users per Experience bar chart — Experience selector + Month selector; hover-tooltip copy "Hover each bar to see the exact amount of active users."
5. Team — avatar rows with role labels (e.g. MEMBER, ADMIN, MEMBER+ADMIN); footer link View/Manage Team.
6. Admin Panel Walkthrough — dark video thumbnail + CTA; footer link "Still need help? Contact Support".

11. Common Workflows

Step-by-step recipes for the tasks administrators do most often.

Publishing a new release to an experience

1. In Builds & Releases → UE Server Builds, confirm the intended server build is present, correct version, and marked Approved.
2. Switch to UE Client Builds and verify a matching client build (same version, same branch) exists and is Approved.
3. Go to Releases and create a new release, binding the experience to the selected server + client builds.
4. Wait for status to move from INITIALIZATION to ACTIVE. If it FAILS, open the release and review logs.
5. Open My Experiences → the experience → Machine Scheduler and confirm regional capacity is provisioned for the event window.
6. Invite participants from Experience → Participants → Invite Member.

Adding a new team member

1. Open Manage Members.
2. Click Invite Team Member.
3. Enter the email address, select the appropriate Role (SUPER_ADMIN, ADMIN, MODERATOR, or MEMBER).
4. Optionally assign one or more Member Groups.
5. Send the invite. The new member appears in Pending Members until they accept.

Rebranding an existing experience

1. Open the experience's Setup page.
2. Go to Customization and upload new Banner, Stream Panel Background, Agenda, and/or Custom Logo.
3. Under Loading Screen Settings, paste a new YouTube URL if the wait-video should change.
4. Save any Additional Assets the experience uses.
5. Verify the update by launching the experience in a test session or by previewing the room via Rooms → Customize.

Scheduling a one-time event

1. From My Experiences, click + Add Experience.
2. Choose a Build Type (e.g. Scheduled · MultiPlayer), give it a name, and set a start and end datetime.
3. Set Max Participants before publishing (this value is locked after publish).
4. On Machine Scheduler, reserve enough Always-On capacity for the opening minutes.
5. Assign a Release (see workflow 1) so the experience has a server+client version to run.
6. Invite participants and, if needed, assign a FACILITATOR.

11. Glossary

Concise definitions for the vocabulary used throughout the Admin Panel.

12. Troubleshooting & FAQ

Answers to the most common problems and questions.

A release shows FAILED. What now?

• Click the release to view its logs.
• Confirm both the server and client builds are Approved and compatible (same major/minor version).
• Retry. If it fails again, delete the failed release and create a fresh one.
• If many releases fail in a row, check the Machine Scheduler for capacity issues in the target region.

My experience is SUSPENDED. What does that mean?

A suspended experience is intentionally paused — either because Suspend After Publish was enabled in Server Configurations, or because an administrator suspended it manually. Resume it from the experience row ⋮ menu.

I changed the Max Participants but the field is locked.

After an experience is published, Max Participants becomes read-only. If you need a different cap, create a new experience from the same Release and migrate invites.

The AI Assistant panel says "Disabled" even after I configured it.

The AI Assistant stays disabled until at least one script or context entry is added under its Assistant tab. Open the assistant's own tab, add a script, and return here.

A guest says they can't find an experience.

Check Participants on the experience — the invite may be in Pending Confirmation. Re-invite or forward the confirmation link.

Mobile analytics look unusually high/low.

Remember that analytics are aggregated. If a single on-device test session ran with many reconnects, it can skew Mobile percentages. Compare against the per-experience view for a cleaner signal.

Who can see Analytics?

All four Admin Roles can view analytics. SUPER_ADMIN and ADMIN have full access; MODERATOR and MEMBER have Write-level access.

13. Getting Help

When you need a human.

On the home Dashboard, two explicit entry points to support are always available:

• Admin Panel Walkthrough — interactive product tour. Great for onboarding new administrators.
• Still need help? Contact Support! — opens the Mytaverse support channel.

When reporting an issue, include:

• Your world name (e.g. MYTA-DEV) and the current URL.
• The experience name and ID (visible at the top of the Experience Dashboard, e.g. #12450).
• Any release ID (e.g. myta-dev-demo-12479-0bh6) involved.
• Server/client versions in play.
• What you were trying to do, what happened, and what you expected to happen.