Appfy

See all cases

Large toll-tag company

Thousands of partners in one portal, each seeing only their own.

Fuel stations, car parks, drive-throughs and car washes: the owner, the finance person and the operator of each one come in through the same door.

The problem
The partners that accept a large toll-tag company's tag needed one portal, where each person signs in alone and sees only what is theirs. Estimate: 3,100 sites × 1 access request a month × 20 minutes of support ≈ 1,033 hours a month, about 5.9 people. The site total is a rounded Forbes Brasil count, not a portal user count. Requests, minutes and a 176-hour month are assumptions. This is not a measured saving.
What Appfy did
The specified access work keeps what each person sees, kept apart from what they can do. The proposed portal was to synchronize the CBILL registration and allow a synchronized partner to be enabled for operation.
The gain
Email and password are the documented entry. On first access the person changes the password and then reaches the profile-driven menu. Assignment to a group makes the person inherit that group's permissions. Gains were not measured.

  1. Scene 1 of 8The company

    Four businesses, one way in.

    A large toll-tag company is also accepted at fuel stations, car parks, drive-throughs and car washes. These partners needed one portal to see the sales paid with the tag.

  2. Scene 2 of 8The problem

    Very different people through the same door.

    Through the same door would come the company's staff and each partner's owner, finance person and operator. Each one could see only their own, like a key to their own room.

  3. Scene 3 of 8The goal

    First, get right who comes in and how.

    The portal started with access: user groups, sign-in and password recovery. Partners already registered came into the portal, but only operate once enabled, like a badge that has to be activated.

  4. Scene 4 of 8The choice

    Seeing is one thing; being allowed to act is another.

    Appfy split access into two parts: a map of the businesses a person sees and a profile of what they can do. Each group joins one map and one profile.

  5. Scene 5 of 8What Appfy did

    Nine paths, from sign-up to menu.

    One example: the administrator puts a person in a group and they inherit the group's permissions. At first access, they change the password, pick the business and see only their own menu.

  6. Scene 6 of 8What Appfy did

    Two proposals, custom authorization or Cognito.

    The two architecture figures dated 18 August 2020 are explicitly labeled Proposal 1 and Proposal 2. Proposal 1 names customAuthorizer. Proposal 2 introduces Cognito. No selected option is established. Final architecture remains unresolved. The annotation about validating permissions on each request does not prove that a Cognito post-authentication trigger handles every later API request.

  7. Scene 7 of 8What changed

    Each person signs in and sees only what is theirs.

    Now a person is registered once, in a group, and signs in seeing only their own sites and their own menu. First access and password changes do not depend on anyone at the company.

  8. Scene 8 of 8And in your company?

    Many different people in one system? Start with access.

    A portal for resellers, clients or partners? Appfy separates what each person sees from what each person can do first. Start with a free 30-minute conversation.