Installation & User Guide

Installation & server requirements

Use a supported PHP environment, MySQL or compatible MariaDB, HTTPS and a web server configured for the application’s routing rules. Confirm the PHP extensions required by your hosting environment, including database connectivity and ZIP support when using the updater.

1. Back up any existing website files and database before replacing or upgrading a deployment.
2. Upload the application archive and extract the project files into the intended web root.
3. Create a dedicated database and database user with only the permissions the application needs.
4. Open /install.php for a fresh installation, enter the database details and complete the administrator setup wizard.
5. After installation, verify that public pages, admin login and member login load over HTTPS. Restrict or remove installer access if the installer indicates that it is no longer needed.

Admin panel & platform configuration

The admin panel is the central place to maintain platform settings and review operational activity.

• Settings: configure site identity, branding, contact information, supported payment options and other available platform defaults.
• Plans: create and maintain packages, prices, activation requirements, MLM model, levels, commission rules, qualifications and caps.
• Users: add members, review account details, update permitted fields and inspect sponsor/package information.
• Activations: review package activation activity and related records.
• Withdrawals: review requests and approve or reject them according to your documented business rules.
• Wallet Transactions & Reports: reconcile recorded transactions and review available income and commission summaries.
• Content: maintain public-page copy such as About, FAQ, Privacy, Terms and this documentation page where CMS editing is enabled.

Registration, profile & account access

1. Open the public registration page and enter the requested details.
2. Provide a valid sponsor/member ID when required. Confirm the sponsor shown before submitting.
3. Sign in using the account credentials and keep them private.
4. Review My Profile and update available contact or account details.
5. Choose an available package and complete the activation or payment steps shown by the platform.
6. Use the dashboard, My Team, Genealogy, Income and Wallet pages to review the records available to your account.

Menu visibility and earning-related actions can depend on account status, package activation, administrator settings and the rules assigned to a package.

MLM models, sponsor links & genealogy

The platform can be configured for the compensation models available in the installed build, including Unilevel, Binary, Matrix, Generation and Single Leg. The model and its settings determine how qualifying activity is represented and calculated.

• Sponsor relationship: identifies the referring member and supports team reporting.
• Placement relationship: where supported, determines where a member appears in the configured tree or leg structure.
• Genealogy: visualizes stored parent/child relationships. It cannot show descendants that are not recorded in the database.
• Commissions: depend on the package configuration, eligibility, transaction status, levels, caps and any qualification rules.
• Audit: use the available reports and transaction history to investigate discrepancies rather than editing balances directly.

Wallets, deposits, transfers & withdrawals

Use the relevant wallet and transaction screens to track recorded balances and requests. A displayed balance should be reconciled against its transaction history.

• Deposits: follow the configured payment workflow and wait for server-side confirmation before treating a payment as complete.
• Transfers: verify recipient details and amount before confirming. Transfers may be subject to platform rules or limits.
• Withdrawals: provide payout details through the designated secure form and review the request status after submission.
• Admin review: reconcile payment references, wallet entries and withdrawal decisions before resolving a dispute.
• PayPal: configure credentials in the admin settings when available; test using Sandbox before enabling Live credentials.

Never share payment-provider passwords, private keys or authentication codes. Payment availability and supported currencies depend on the configured provider account.

Franchisee operations

Where franchisee access is enabled, franchisees can use their dedicated area to review members and the operational actions granted to their account.

• Review franchisee dashboard summaries and member records.
• Add a member using the required profile and sponsor information.
• Use the available purchase-wallet or deposit workflow for eligible actions.
• Complete member activation only through the approved flow.
• Review commission/report records and submit withdrawal requests where supported.

Access is role-based. Do not share franchisee credentials or use another person's session.

System Update: install a release ZIP

Use Admin → System Update when the updater is present and accessible in your installed build. A release ZIP should include a valid manifest.json, a version newer than the installed version, and only the intended project-relative files.

1. Back up both the website files and database independently before starting.
2. Prepare a release archive with a manifest listing the product, version, PHP requirement, changed files, migrations and release notes.
3. Sign in as an administrator and open System Update.
4. Select the ZIP and let the server validate its manifest and paths.
5. Review the release notes, then start installation and wait for the final server result.
6. After success, verify the version, sign in to the public/member/admin areas and test the changed features.

Keep config/database.php, uploaded files, user-generated content and installation locks protected. Database migrations should be explicit, reviewed and safe to run against the production schema.

Security, backups & troubleshooting

• Use a unique administrator password and sign out on shared devices.
• Keep PHP, the database server and hosting software patched to supported versions.
• Enable HTTPS and protect backups, database exports, logs and uploaded documents from public access.
• Never place database credentials or payment secrets in publicly accessible files or share them in support screenshots.
• Before every release, create a restorable file backup and database backup; periodically test restoration on a separate environment.
• If a page fails, note the URL, time and visible error; check server logs and verify database connectivity and file permissions.
• If an update fails, preserve the error message and backup paths, avoid repeatedly uploading the same release, and restore from a verified backup if necessary.
• After a deployment, check login, registration, package listing, wallet history, admin navigation and any feature changed by the release.

Support & operational checklist

When contacting the site administrator, include the affected page, approximate time, steps to reproduce and the exact non-sensitive error message. Never send passwords, payment secrets, complete identity documents or private database exports through an ordinary support message.