Skip to content
MICROBA — Return to Origin.

MANUAL / GUIDE

MICROBA PROFILE USER MANUAL

Version 3.2.0 Public access Updated August 21, 2026

knowledge_id: 47443625-dce1-44ab-a6b3-7a2a1959e39d type: USER_MANUAL title: "MICROBA PROFILE --- USER MANUAL" slug: membership-and-profile version: 3.2.0 revision: 4 status: published visibility: public authority: manual language: en canonical_language: en summary: "Member guide for PROFILE v3.2.0: canonical MID, Sponsor and referral identity, saved Places, settings, integrated module views and referral-aware Product entry." pathways:

  • profile
  • user-manual

topics:

  • profile
  • user-manual

source: "MICROBA PROFILE v3.2.0 + HIVE v1.7.0 coordinated architecture release · 2026-08-21" supersedes: "MICROBA PROFILE User Manual prior revisions through Rev 03" sources: [] related_knowledge:

  • KNW-EE495D1D
  • KNW-EC324ADA
  • KNW-2ED02249

MICROBA PROFILE --- USER MANUAL

Canonical runtime baseline: MICROBA PROFILE v3.2.0

Documentation release: 21 August 2026

Architecture: PROFILE is the canonical authority for MID, Sponsor MID and referral identity. HIVE consumes MID-based projections and does not appoint Sponsors or own referral links.

1. What PROFILE is

MICROBA PROFILE is the canonical member identity and member-settings domain. It owns your MICROBA Member ID (MID), registration identity, Sponsor identity, referral identity, saved Places, avatar/profile information, preferences and applicable PROFILE consent records.

PROFILE also provides the member shell in which HIVE, Visitor, Commerce and Knowledge may be presented. Showing another module inside PROFILE does not transfer that module's business authority to PROFILE.

2. Member navigation

The canonical PROFILE member navigation is:

  1. Preview
  2. HIVE
  3. Visitor
  4. Commerce
  5. Knowledge
  6. Settings

The global MICROBA Theme Header remains separate above the PROFILE member area.

3. Your MID

Your MID is your canonical MICROBA member identifier.

  • It is created and owned by PROFILE.
  • It is not an ordinary editable field.
  • HIVE, Product, Commerce and other modules should use the canonical MID rather than inventing another member identity.
  • A referral alias is only a friendly routing identity for the same MID.

4. Registration and Sponsor

Registration may be completed with or without a Sponsor.

If registration begins from a valid PROFILE referral link or MID referral route, PROFILE resolves that route to the canonical Sponsor MID and stores the Sponsor MID as part of registration truth.

Registration success does not depend on HIVE being synchronously available. HIVE receives the committed MID/Sponsor projection afterward.

Sponsorless registration

Sponsorless registration remains valid.

A genuinely never-sponsored member may later receive a first-time Sponsor appointment through an authorized PROFILE Admin workflow.

Once a valid Sponsor has ever been established, ordinary Sponsor replacement is prohibited. A first-time Sponsor appointment is not a Sponsor-change facility.

If a historical HIVE relationship later ends because of Dormancy, the historical Sponsor evidence remains protected and does not become a new appointment opportunity.

PROFILE owns your referral identity.

Your canonical referral identity may include:

  • a MID-based referral route; and
  • one active friendly referral alias.

Example:

bina.microba.co/your-alias

The alias resolves to your same canonical MID. Changing or resetting an alias never changes your MID, Sponsor, HIVE Network, qualification or Nectar history.

Alias confirmation and correction

A member may confirm one alias in the current available alias cycle. After confirmation, ordinary self-service replacement is locked.

Authorized PROFILE Admin governance may reset, directly change or delete an alias where the approved workflow permits it. Historical aliases remain reserved to the same MID so an old shared link cannot later be reassigned to another member.

A referral link can be used by either a visitor or an existing member to enter the Product journey.

The purchase flow is:

PROFILE referral route
→ PRODUCT
→ COMMERCE paid Order
→ HIVE 9% Nectar consequence

PROFILE resolves the link to a canonical referral_mid. The purchase attribution is transaction-specific.

For an existing member, using another member's referral link for a purchase does not rewrite the buyer's fixed Sponsor MID or Direct Sponsorship relationship.

7. Preview

Preview is the member landing view. It may summarize PROFILE-owned identity information and read-only indicators from integrated domains such as HIVE, Commerce, Knowledge and Visitor.

A displayed value remains owned by its source module.

8. HIVE inside PROFILE

The HIVE view may show:

  • HIVE lifecycle status;
  • qualification and qualifying tenure;
  • one-level Direct Network;
  • Nectar Wallet balances and activity;
  • redemption information;
  • HIVE activity; and
  • Promotional Banner information.

PROFILE does not calculate HIVE qualification, lifecycle or Nectar.

Referral alias editing and Sponsor appointment are PROFILE-owned even when HIVE displays the resulting MID/Sponsor information read-only.

9. Visitor

Visitor provides referral/visitor analytics. Visitor analytics do not create membership, Sponsor relationships or HIVE Network positions.

10. Commerce

Commerce shows commercial history such as Orders and transaction state. Commerce owns checkout, Order, payment and refund truth.

PROFILE identity and referral routing may supply trusted MID context, but PROFILE does not rewrite an Order after Commerce commits it.

11. Knowledge

Knowledge presents controlled MICROBA knowledge materials and meaningful engagement/progress. Knowledge remains its own domain.

12. Settings

Settings remains one consolidated page and may contain:

  • Personal Information
  • Contact Information
  • Address Repository
  • Referral
  • Security
  • Preferences
  • Privacy & Consent
  • Account Information

Referral settings are PROFILE-owned. HIVE business settings such as Nectar redemption and HIVE banner operations remain HIVE-owned.

13. Address Repository

PROFILE supports five reusable saved Place slots:

  • Home
  • Billing
  • Process 1
  • Process 2
  • Process 3

You may use Search Address or Enter Manually. A valid manual address remains valid even if latitude, longitude or timezone cannot be resolved.

System-resolved location metadata is read-only.

14. Shared Location Context

The Theme is the single Shared Location Context resolver.

Priority:

  1. Device Location
  2. PROFILE Home Address fallback

PROFILE must not create a competing global location resolver.

15. Deletion and account support

Normal member deletion uses a governed request/review process. Other modules may retain records they independently require for historical, commercial, reward, audit or compliance purposes.

Exceptional Force Delete is an administrative/testing bypass and is not the ordinary member deletion path.

16. Key rules to remember

  • PROFILE owns MID.
  • PROFILE owns Sponsor MID and first-time Sponsor appointment.
  • PROFILE owns referral link/alias resolution.
  • HIVE does not appoint or change Sponsor.
  • HIVE calculates Network, qualification, lifecycle and Nectar by MID.
  • A referral purchase can earn 9% for the referral MID whether the buyer is a visitor or member, subject to HIVE order-time eligibility.
  • Purchase referral attribution never rewrites an existing member's fixed Sponsor.
  • Alias changes never rewrite MID, Sponsor, Network, qualification or Nectar history.