Who are you signed in as

Standing in for login. The brief rules out real authentication, so a role is one cookie and one click — but the portal genuinely answers differently depending on which of these people is using it.
This exists because of a real finding. The Product Module function list assigns bundle authoring to the Product Manager (F-B-01, F-B-02, F-B-09) and bundle benefits and sign-off to the Pricing Manager (F-B-06 … F-B-08, F-B-10). The Relationship Manager appears against none of them, so an RM being unable to create a bundle is the rule working, not a gap. F-E-03 then requires four-eye approval on every bundle change — which needs two different people, not two permissions on one.

Relationship Managersigned in

Nguyen Van A · RM001

Prices deals, tracks revenue and profit. Reads the bundle catalog but cannot author it.

Pre-Deal SimulationRevenue TrackingProfit per Account

You are using the portal as this person.

Product Manager

Do Thi E · PM001

Defines bundles and their components, and submits them for sign-off.

F-B-01F-B-02F-B-09

Pricing Manager

Vu Van F · PRM001

Sets up pricing scopes, base/floor/ceiling prices and volume tiers. Configures bundle benefits and activation conditions, and approves what the Product Manager submits.

PS-01 … PS-11PS-15F-B-06F-B-07F-B-08F-B-10

What is simplified, and what is not

  • Simplified: no password, no user directory, no permission matrix. A cookie holds one role id.
  • Not simplified: the checks are enforced in the server actions, not by hiding buttons. Switching role changes what the server will actually accept — posting a create-bundle request as the RM is refused with the function-list reason, not silently ignored.
  • Not simplified: maker and checker must be different people. The Product Manager who submits a bundle cannot approve it, even though the Pricing Manager role is one click away.
  • Inconsistent on purpose: bundles need two people, but pricing setup needs one. The Pricing Manager takes a price from draft to live alone. That is the specification's doing — its function inventory names no actor for PS-01 … PS-11 and records that the approval mechanism “may be external/future” — so rather than invent an approver, the difference is left visible.