Field guide / Admin
Ultra Thunder Admin Access
The backend page explains the system. This page is about the responsibility that comes with administrative access, and the questions every new admin should ask before touching anything.
Definition
What Ultra Thunder admin access is
When operators say "Ultra Thunder admin" they usually mean oversight-level access in the backend: the ability to manage accounts within a defined scope rather than just operate a single account. Admin access is not a separate website. It is reached through the same Ultra Thunder backend portal as other operator accounts.
Authorized credentials are required. The word "admin" in a search result or message does not grant anything; access comes only from an account issued to you.
Scope
Administrator account levels and scope
The single most important question for any admin is: over what? Admin access always has a scope, the set of accounts you are responsible for. In a layered business, a distributor may administer its own agents and stores, while a higher-level account oversees several distributors.
Responsibility
Account, agent and store management
Where your access includes managing accounts below you, you become the person others rely on when something goes wrong. That means knowing who holds each account, how to reach them, and what you set up for them. A short private register of every account under you, its owner, its purpose and the date it was created will save hours later.
Balances
Credit controls
Admins are frequently the people moving credits between accounts. Whatever tools your account includes, the discipline is the same: record each movement, reconcile your log against the backend at a fixed time, and investigate differences the same day. See Ultra Thunder credits for more on balances.
Oversight
Reporting
Oversight is only as good as the records behind it. We have not verified which reports the current backend provides, so ask your provider what history views come with your access, and keep your own independent records regardless.
Structure
Account hierarchy
It helps to sketch your structure on paper: who supplies you, which accounts you oversee, and who those accounts serve. That sketch is the map you will use to answer support questions quickly and to explain the setup to anyone new.
Non-negotiable
Security for admins
- Admin credentials should belong to one person. Do not share them with staff; ask for separate accounts if you need help.
- Sign in only at fmubk.ultrathunder.mobi. Never through a link someone sends you.
- Never share passwords, authentication codes or recovery codes publicly or in group chats.
- Sign out on any device that is not yours alone.
- Report a suspected compromise to your provider immediately.
Comparison
Admin vs. distributor vs. agent
| Admin | Distributor | Agent | |
|---|---|---|---|
| Focus | Oversight of accounts within a scope | Supplying and supporting downstream operators | Day-to-day work with player accounts |
| Typical question | Which accounts am I responsible for? | How do I support my agents and stores? | How do I serve my players? |
| Where they sign in | fmubk.ultrathunder.mobi | fmubk.ultrathunder.mobi | fmubk.ultrathunder.mobi |
Legacy