Administration
Manage task publishing and platform configuration with server-checked administrator access.
Administrator sign-in
The app owner is the first administrator. Sign in with the account that owns this app. Roles are resolved by a server function, not by the address in your browser.
Safe setup, honest status
This version is not a production cash-rewards system. Personal data stays in built-in key-value storage. A managed relational database is a Pro feature; the editor’s Database panel offers an upgrade or connection to your own Supabase project for free. No provider has been switched automatically.
The app owner is the initial administrator, determined on the server by the platform’s ownership claim. The owner can grant an administrator role through account management when supported by their plan. No administrator password or credential is bundled in the application.
Capability checklist
Authentication & password reset
The prebuilt authentication service handles registration, sign-in, password reset, and sign-out. Live account flows still require testing on the published app.
Private profiles & Nigerian bank details
Saved to account-scoped built-in key-value storage. Phone identity and bank account ownership are not verified.
Task catalogue & private proof
Task publishing uses administrator validation and storage ownership. Proof saves privately. Cross-account review, capacity enforcement, and tamper-proof reward snapshots are not available.
Transactional wallet & rewards
No cash credit, balance adjustment, reward approval, withdrawal reservation, or refund operation is exposed. KV does not supply the relational transactions required for safe settlement.
Referral validation & crediting
Codes and unverified referral attribution are saved. Verified relationships, abuse detection, qualifying events, and unique referral reward credits need the financial backend.
Payment completion
A payout provider and verified server-to-server payment confirmation must be integrated before marking any payment Completed. No payment provider is connected.
Cross-account administration & permanent audit
Owner-only authentication account controls work through the platform. Private financial records, review queues, investigations, and an append-only audit ledger require a protected server data layer.
Required acceptance tests before launch
| Scenario | Required result | Test status |
|---|---|---|
| Register, sign in, reset password, sign out | Unique account; session and password reset work | Not live-tested |
| Save profile and bank details; sign in on a second device | Same private records; another account cannot read them | Not live-tested |
| Create, edit, pause, activate, delete tasks | Owner mutation persists; ordinary user action rejected | Not live-tested |
| Submit screenshot, link, or text proof twice | One accepted immutable submission; duplicates rejected server-side | Not live-tested |
| Approve reward concurrently and replay the request | One ledger credit; no duplicate reward | Not live-tested |
| Qualify referral, self-refer, and repeat the event | Only one eligible non-self referral credit | Not live-tested |
| Request withdrawal concurrently; reject and retry | One reservation; no negative balance; one refund | Not live-tested |
| Approve and confirm an external payment | Only confirmed settlement can become Completed | Not live-tested |
| Alter URL, browser amount, account role, and storage key | Protected server mutations reject unauthorized access | Not live-tested |
Compilation checks are not end-to-end payment, permission, or authentication tests. The financial scenarios are blocked pending transactional backend implementation.