Skip to content

Organization Task Workflows

These workflows reflect the current organization-console behavior even where the test environment did not provide a working organization-linked browser login during this refresh.

A. Authentication and Context

OF-01 Resolve organization context after login

Route: /login -> /app

  1. Sign in with an organization-linked account.
  2. Confirm the portal resolves organization context before rendering the main workspace.
  3. Verify the user lands on /app rather than /forbidden.

Expected result: the console loads a live organization workspace only after context resolution succeeds.

OF-02 Handle missing organization context

Route: /forbidden

  1. Attempt the org console with an authenticated but non-org-linked account.
  2. Confirm the portal redirects to /forbidden?reason=missing-org-context.
  3. Use this outcome to separate auth success from organization-context failure.

Expected result: context failures are explicit and do not masquerade as generic auth issues.

B. Transactions and Float

OF-03 Review transactions within assigned scope

Route: /app/transactions

  1. Open the transactions page.
  2. Apply date and transaction-type filters.
  3. Confirm that only data for the resolved organization scope appears.
  4. Drill into /app/transactions/:txnId from a visible row.

Expected result: transaction review remains limited to authorized organization scope.

OF-04 Review the selected-unit float snapshot

Route: /app/float

  1. Open the float page.
  2. Select an assigned organization unit where multiple units are available.
  3. Confirm the current balance, journal snapshot, and unit transaction history all refresh for that same unit.
  4. Verify the agent profile shown on the page matches the unit you selected.

Expected result: float evidence is clearly unit-scoped.

OF-05 Top up float for the selected unit

Route: /app/float

  1. Open the float page for an agent-backed unit.
  2. Choose the funding bank and enter the amount.
  3. Submit the top-up request.
  4. Refresh the page and confirm the unit-scoped float evidence updates.

Expected result: the top-up is treated as a unit-context action, not a generic organization-wide adjustment.

OF-06 Record a customer deposit through agent operations

Route: /app/float or /app/agents/:agentId

  1. Open the float or agent detail workflow for the relevant agent-backed unit.
  2. Enter the customer MSISDN, amount, and reference.
  3. Submit the deposit.
  4. Verify the action appears in subsequent transaction evidence for that unit.

Expected result: customer deposit handling stays tied to the agent and unit in scope.

C. Agent Operations and Hierarchy

OF-07 Review the agent directory with live identifiers

Route: /app/agents

  1. Open the agent directory.
  2. Search or filter to narrow the agent list.
  3. Confirm that till and shortcode identifiers are visible directly in the directory experience.
  4. Use the list to navigate into an agent detail page.

Expected result: the agent directory exposes operational identifiers without forcing a second lookup.

OF-08 Open agent detail and inspect mapped tills

Route: /app/agents/:agentId

  1. Open a live agent detail route.
  2. Review status, float, tills, and shortcodes.
  3. Follow a mapped till into its ledger if the till row provides a ledger action.

Expected result: the detail page is the operational handoff from directory search into till-level investigation.

OF-09 Review child agents for a super agent

Route: /app/agents/:agentId/children

  1. Start from an agent that is tier SUPER or MASTER.
  2. Open the child-agent route.
  3. Confirm child count, total child float, till coverage, and the child rows render.
  4. Check that child rows expose till numbers directly and surface shortcode chips where present.

Expected result: the hierarchy page summarizes a super agent's network in one place.

OF-10 Troubleshoot a missing hierarchy action

Route: /app/agents/:agentId

  1. Open the agent detail route.
  2. Confirm whether the agent is actually SUPER or MASTER.
  3. If not, do not expect the child-agent navigation path.
  4. If the tier is correct but the action is absent, verify the hierarchy endpoint and frontend role guard.

Expected result: operators diagnose hierarchy issues by tier and data, not by guesswork.

D. Organization Structure and Governance

OF-11 Review organization units and branches

Route: /app/organizations, /app/branches, /app/branch-comparison

  1. Open the unit and branch directories.
  2. Review how units and branches are segmented.
  3. Use detail routes and comparison routes to inspect unit- and branch-level metrics.

Expected result: structure review stays consistent with the resolved organization hierarchy.

OF-12 Use approvals, team, and settings routes

Route: /app/approvals, /app/team, /app/settings, /app/security/2fa

  1. Open approvals for pending work.
  2. Review team management where the signed-in role allows it.
  3. Open settings and security routes for account and policy maintenance.

Expected result: governance and self-service routes honor both role checks and organization context.