Carsharing System

Carsharing Companies, Agents, and Admin Roles

A platform with more than one operating company, plus agents, should not dump every order into one undifferentiated admin login. Someone has to create the companies, decide what a role can click, and still see which company an order belongs to. Ptaxi’s carsharing system documents a compact permission set: staff can create companies and create agents, create operating roles and set function permissions, and create system administrators. Orders are attributed according to the company that owns the vehicle.

This article stays on that hook. It does not import a permission model from another product line, and it does not invent a default data scope for agents. If someone on the call has already seen a designated-driver or taxi permissions walkthrough, ask them to set that language aside. The carsharing list has its own, shorter permission section, and borrowing scope phrases from those other products is how a script gets ahead of the docs.

Companies and agents

Under PC permission settings, company management lets staff create companies and create agents. That is the documented structure: companies, and agents, as create actions on this screen.

The list does not spell out a franchise contract workflow, an agent commission rate, or an agent-only dashboard. A buyer should confirm in a demo what an agent can see versus a company, because the list says you can create agents and roles with function permissions, but it does not spell out the default agent data scope. Write down what the build shows. Do not sell a regional franchise pack as if it were already in the list.

Do not borrow “own-company data versus subordinate companies” wording from other mobility lines. That scope language is not in this carsharing permission section. If a demo later shows a data-scope toggle, label it as a demo observation, not as a documented default.

The pain this feature is meant to solve is the single shared login. The capability is a place to create companies and agents, then attach people through roles and system administrator accounts. The tradeoff is immediate: function permissions are only as good as the role you build, and if the list does not document a default data scope for agents, you should not sell one.

Roles and system administrators

Role management lets staff create different operating roles and set different function permissions. Function permissions are only as good as the role you build. A role with every function turned on is just another superuser. A role with the wrong functions hidden will send people to a screen they cannot use, or hide a screen they need.

The list does not publish a catalog of the function names. In a demo, create two roles with different function permissions, then log in as each and write down which menus appear. That is the training, not a slide that pretends the function tree is already printed here.

User management lets staff create system administrators. Keep that as the login side of the same story: a company and an agent are operating units; a role is a set of function permissions; a system administrator is a user you create to work under those settings. The list does not say every admin must be bound to one company, or that an agent login is a different user type with a pre-built dashboard. Confirm the binding in a demo.

When you brief this, keep the words tight. “Agent” in this list is something you can create under company management. It is not, by itself, a documented commission plan. “Role” is a set of function permissions. It is not, by itself, a documented data filter. If a buyer uses those words to mean a franchise contract or a regional report pack, slow the conversation down and go back to the create actions and the function permissions you can actually set.

It is fine to say you do not yet know the default agent scope. That sentence is more useful than a confident guess. The list gives you the hooks — create the agent, create the role, set function permissions — and leaves the data boundary for the demo. A function permission can hide a menu. It may or may not limit the rows inside a menu you can still open. Only the first of those is clearly documented here.

Orders follow the vehicle’s company

The PC order list lets staff view all platform orders and open order details. Orders are attributed according to the company that owns the vehicle. Order details include basic information, the order log, fee details, the trip track, complaint records, and push logs.

Attribution is the documented link between the permission set and daily work. When two companies operate on one platform, an order is not “whoever opened the admin that morning.” It belongs to the company that owns the vehicle. Train that sentence out loud. Then open an order detail and walk the documented blocks: basic info, log, fees, track, complaints, and push logs.

The list says you can view all platform orders. Combined with the earlier caution about agent data scope, do not assume a role or an agent automatically sees only their own company’s orders. “View all” is what the order list documents. If a role should see less, that is something to confirm in a demo when you assign function permissions, not something to invent as a default scope.

This is also why vehicle ownership has to be clean before you argue about admin access. If a vehicle is sitting under the wrong company, the order will follow that wrong company. The permission screens will not fix a bad vehicle record. In a demo, place one job on a vehicle owned by company A and one job on a vehicle owned by company B, then open both orders and point to the attribution. That is more useful than a diagram of agents.

The order-detail blocks are also a good place to keep the training honest. Basic information, the order log, fee details, the trip track, complaint records, and push logs are documented. That is already a full record for support and disputes. It is not a company P&L, and it is not an agent settlement report. If a buyer wants commissions or a franchise invoice at this point, take them off this card. Attribution tells you which company the order belongs to. It does not, in this list, calculate what an agent is owed.

One more practical habit: after you create the second company, assign at least one vehicle to it before you start the order demo. An empty company will not help you show attribution. You want two vehicles, two companies, and two orders you can open side by side.

What not to promise on companies and roles

Do not invent agent commission rates, agent-only dashboards, or a franchise contract workflow. Do not sell a default data scope for agents, and do not write “own-company versus subordinate companies” as if it were in this list. Do not import another product line’s permission model. Do not assume the order list is already filtered by company or by agent; it documents a view of all platform orders, with attribution by the vehicle’s company. Do not pretend the function-permission tree is published here.

A short ops checklist before you brief the admin

Keep this to one page.

  • In permission settings, open company management and create a second company and an agent. Write down only the fields the build actually asks for.
  • Open role management and create two operating roles with different function permissions. Do not invent function names on the slide; copy what the screen lists.
  • Create system administrators for those roles, then log in as each and record which menus appear.
  • Ask, in the demo, what the agent login can see versus the company. If the answer is not in the list, label it as a demo observation.
  • Open the order list. Place or find one order per company, using vehicles each company owns. Point to attribution by the vehicle’s company.
  • Open one order detail and walk basic information, the order log, fee details, the trip track, complaint records, and push logs.
  • Keep commission plans, franchise contracts, and imported scope language off this card.

If a script starts promising an agent dashboard or a default data scope, cut it back to create actions, function permissions, and order attribution by the vehicle’s company.

Close

Carsharing admin work on a multi-company platform starts with a small set of create actions. Staff can create companies and agents, create operating roles with function permissions, and create system administrators. Orders are attributed according to the company that owns the vehicle, and the order detail holds the basic record, the log, the fees, the track, complaints, and push logs.

That is enough to stop using one shared login for every operator, if you actually build the roles you need. It is not enough to sell an agent commission plan, a franchise workflow, or a data scope the list does not write down. Look at these permission settings on the carsharing system product page. If you want a walkthrough, ask for a demo and bring two companies plus one agent, then log in under two different roles and open one order for a vehicle each company owns.

Frequently asked questions

What can staff create under company management and role management?

Company management lets staff create companies and create agents. Role management lets staff create different operating roles and set different function permissions. User management lets staff create system administrators. The list does not spell out a default agent data scope, an agent-only dashboard, or a franchise contract workflow. Confirm in a demo what an agent can see versus a company.

How are platform orders attributed to a company?

Orders are attributed according to the company that owns the vehicle. The PC order list lets staff view all platform orders and open order details. Details include basic information, the order log, fee details, the trip track, complaint records, and push logs. Do not brief attribution as “whoever opened the admin that morning.” It follows the vehicle’s company.

Does an agent automatically see only their own company’s orders?

The list does not spell out the default agent data scope. The order list documents the ability to view all platform orders, and roles are defined by function permissions you set. A buyer should confirm in a demo what an agent can see versus a company. Do not sell a pre-built scope, and do not import own-company versus subordinate-company wording from another product line.

Is this the same permission model used on the designated-driver product?

No. This article uses only the carsharing permission section: companies, agents, roles with function permissions, and system administrators, plus order attribution by the vehicle’s company. Do not import another product’s permission model, and do not write own-company data versus subordinate companies as if it were documented here. If a demo later shows a data-scope toggle, label that as a demo observation.

Related articles

Carsharing Referral and Sign-up Rewards: Campaigns You Can Add and Track

A carsharing network that grows only by word of mouth still needs a campaign you can turn on, edit, and retire. The marketing center lets you add, edit, and delete referral campaigns for new users and drivers, and sign-up reward campaigns for new users and drivers. Invitation statistics and registration statistics then show detailed reward data for those activities. Reward form, amount, and fraud rules are not fixed here — confirm them in a staging build and in your own policy.

· 7 min read

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.