Shared trips on the toto desk

Mobility is the toto desk at mobility.lawazia.tech. A person asks for a ride. Another person can be on that same ride. The desk shows one card for the trip, and it only does this for people it has registered. Two profiles already name the work: how trips are combined, and how the desk limits who can use it and what the toto is called.

One card for one trip

Suraj Kumar Yadav's profile says three things about a trip. Requests for the same trip combine into one card. Cancelling a trip frees the other request. Sharing a ride puts people on the same trip. Read those as one rule with three moments.

Two people want the same trip. Before this, a desk can show two cards and a person can treat them as two rides. His line says those requests become one card. The card is the trip. The people are on it together because someone shared the ride, which is the third sentence: sharing a ride puts people on the same trip. Cancel is the middle sentence. If the trip is cancelled, the other request is free again. It is no longer held inside the cancelled trip. The other person can be placed on a different trip. The diagram on this page is that shape: two requests, one card. It uses the words from the profile. It is not a screenshot of a live booking, and it has no fare on it.

Om Kumar Choubey's profile says the desk is limited to people we register, and it names the logo and the toto transport name. On 10 October 2026 the mobility repo gained the admin panel for user approval, roles, and account status. That is the same idea as a desk that only works for people it has registered: someone is approved, they have a role, and the account can be on or off. The logo and the toto name are what the screen says the service is. A reader looking at the desk should see the toto name, not a generic label, and the logo that belongs on that desk.

By 13 October 2026 the desk was taking toto bookings. Those booking commits are the desk ringing when a toto is booked. They are a different change from the trip card and from the register. This note keeps them separate so the profile lines stay the source.

Two requests for the same trip join one card.

Who changed it

Walk a shared ride with only those sentences. A registered person asks for a trip. A second registered person shares that ride. The desk puts both on the same trip and shows one card. The admin looking at the desk sees the toto name and the logo, and sees only people the desk has registered. If the trip is cancelled, the other request comes free. The first person's cancel does not leave the second person stuck on a dead card.

The register is the gate in front of that. Om's line is who may appear on the desk at all. Suraj's line is what happens to the requests once those people are on a trip. Approval, role, and account status are the admin tools that match a desk limited to registered people. The logo and the transport name are the words on the screen while that work happens.

A company reading the two profiles can open the live desk and look for three checks. One card when two people share a trip. A cancel that frees the other request. A desk that shows the toto name and the logo, and that is for people it has registered. Fares, driver names, and trip counts stay on the desk. They are not copied here.

The desk shows registered people, the toto name, and the logo.

A desk day

The day starts with who is allowed on the desk. A person who is not registered does not get a card. That limit is Om's line, and the admin panel from 10 October is where approval, role, and account status are handled. Once two registered people share a ride, Suraj's line takes over. The requests stop being two cards. They are one trip. The toto name and the logo stay on the screen, so the desk reads as that transport.

Cancel is the part a reader can miss. Sharing puts people on the same trip. Cancelling that trip has to put the other request back on its own. If cancel only removed one person and left the other inside a cancelled card, the second sentence on his profile would be missed. The check is simple. After cancel, the other request can be placed again.

Who drove, what the fare was, and how many trips ran in a day stay on the desk. The profiles do not state them, so this note does not either. The diagrams are the combination of two requests into one card, and the three labels the desk shows: registered people, the toto name, and the logo.

What you can open

Requests for the same trip combine into one card. Cancelling a trip frees the other request.

Open Mobility

The date on this note is 10 October 2026, the day the admin panel for approval, roles, and account status landed. That is the commit that matches a desk limited to people we register. The trip-card sentences are the ones on Suraj's profile. The desk was taking toto bookings by 13 October 2026, which is context for the product, and those booking lines are not claimed as the trip card.

This note adds no client beyond the toto desk and no placement. The proof is the live desk and the two sentences already stored on the profiles.