Car Rental Software

Car Rental Admin Roles: Own-Company Data vs Subordinate Companies

A car rental group that runs more than one store often starts with one shared admin login. Everyone can see every booking, every deposit, and every payout. That is convenient until a clerk at Store A refunds a deposit that belongs to Store B, or a regional manager cannot see yesterday’s numbers because the password lives in someone else’s chat. Ptaxi’s car rental software documents a more ordinary setup: backend user accounts, roles that combine data permission and operation permission, and company management to add or edit companies and their business information.

This is not store onboarding, and it is not the corporate renter path. Store certification already covered how a store applies and gets reviewed. Enterprise approval already covered company bookings. Today’s card is who on your staff can see which company data, and which screens they can use.

Why a shared login stops scaling after the second store

The rental desk has real money on the screen: vehicle deposits, violation deposits, extra fees at return, store income, and platform commission. Order details also show renter information, store information, and payment status. If every account sees all of that, a store dispute becomes a group-wide leak. If you try to solve it by keeping one laptop in the back office, the regional team works blind.

The documented path starts in user management, where backend staff accounts are set up. Role management then sets two permission types for those accounts.

Data permission has two documented scopes:

  • This level — staff can see only their own company’s data.
  • This level and subordinates — staff can see their own company’s data and the data of lower companies.

The feature list’s label is “this level and own,” and the description is own company plus subordinate companies. Use that meaning in the brief. Do not invent a third scope such as “all companies in the country” unless the demo shows it.

Operation permission controls which functions those staff can use. That is the difference between a clerk who can open an order and a supervisor who can cancel one, refund a deposit, or review a store. The list does not name the default role titles, and it does not itemize every function flag. In a demo, open a role and copy the function list you actually see.

Company management can add or edit companies and company business information. That is how the tree those data scopes walk is maintained. The list does not say a company record is the same thing as a store record. Stores have their own list, with store information, vehicles, and a ban action. In a demo, create or open one company and one store. Write down how they relate, and do not brief “company equals store” until you have seen that join.

The tradeoff in each scope

A tight this-level role is the right default for a store team that should not browse another branch’s renters or deposits. It also blocks a regional manager who is supposed to compare two cities. If you give that manager the wider scope, they can see own-company plus subordinate data. They can also see more personal and financial records than a single store needs.

That is the tradeoff to say out loud. Wide data scope is convenient for a head office. It is leaky if the same role is handed to a front-desk account. Narrow scope protects stores. It is frustrating if your only regional role cannot run a combined report.

Operation permission has a similar tradeoff. If every function is turned on, the role is just a second shared login. If you turn too many functions off, staff invent workarounds in a spreadsheet. The list lets you control which functions a person can use. It does not publish a packaged maker-checker, such as “one person requests a deposit refund and another must approve it.” If you need two people on a refund, confirm whether two roles can express that, or treat it as an operating rule outside the screen.

Do not invent field-level access. “Hide the ID number but show the plate” is a reasonable wish. It is not what the list describes. Function-level control is the documented lever. In a demo, pick one sensitive action — deposit refund, store ban, or invoice handling — and see whether you can keep it off a clerk role.

Neighbors to keep off this card

Store onboarding and certification is how a store gets onto the platform. A store list then shows store information and vehicles, and staff can open vehicles or ban a store. That is not role management. Mention it only so a buyer does not treat “ban store” as a role setting.

Vehicle upload and review, return settlement, deposit records, and store finance already have their own posts. Those screens are often the functions you will turn on or off for a role. Do not retell how deposits move or how a return is settled.

Enterprise approval is the corporate renter path: employees, pre-trip or post-trip approval, and enterprise invoicing. An “enterprise” in that walkthrough is a customer company. A “company” in role management is part of your own operating tree. Keep the words distinct in the brief so a sales call does not mix them.

Version updates, ad graphics, and system switches such as payment or withdrawal controls are settings, not roles. A person still needs operation permission to open those settings. That does not make this an ads article or a payments article.

What not to promise

Do not name default roles such as “super admin,” “store cashier,” or “finance only” unless you saw those labels in the demo tenant. The list lets you create roles. It does not publish a starter pack.

Do not promise single sign-on, directory sync, or field-level ACL.

Do not promise a two-person approval engine. Confirm whether operation permissions can approximate it, and say so honestly.

Do not import designated-driver or ride-hailing role wording as if it were this rental list, even when the data-scope idea looks similar. Brief the car-rental document: user management for staff accounts, roles with this-level versus this-level-and-subordinates data permission, operation permission over functions, and company management to add or edit companies and business information.

Do not describe China-only booking channels. This card is backend access for a rental operator.

A short ops checklist before you brief the app

Keep this to one page.

  • Open company management. Add or open two companies in the demo tenant, and write down what “company business information” includes. Note how a company relates to a store, if it does.
  • Open role management. Create one this-level role and one this-level-and-subordinates role. Copy the operation-permission flags you will actually use.
  • Create two staff accounts in user management and assign those roles. Log in as each account and write down which orders, stores, deposits, and finance screens appear.
  • Try a sensitive function on the narrower role: cancel an order, refund a deposit, ban a store, or open invoice management. Record whether the function is hidden, visible but blocked, or still available.
  • Log in as the wider role and confirm subordinate-company data appears, and that it includes only the companies you expect.
  • Open store certification and the enterprise-approval path only to keep them off this card. They are neighboring workflows, not role settings.
  • If you need two people on a refund, test whether two roles can express that. If they cannot, write the gap into the launch brief instead of inventing a workflow.

Close

Car rental admin roles are how you stop using one shared login across a store group. Staff accounts get a role. The role has a data scope — own company only, or own company plus subordinates — and an operation scope for the functions that person can use. Companies can be added or edited in company management. The list does not publish default role names, field-level access, or a packaged approval chain. Those are demo items, not brochure items.

If you run a multi-store rental business and every clerk can still see every deposit, walk this path in a car rental software demo. Bring one store-level account, one regional account, and one action you do not want a clerk to use. Then write the role set you will launch with, and the gaps you will handle as process. For how a store gets certified, use the store onboarding post. You can also contact Ptaxi when you want that demo scheduled.

Frequently asked questions

What permission types does car rental admin use?

Role management sets two kinds of permission for backend staff. Data permission has two documented scopes: this level, which can see only that company’s data, and this level plus subordinates, which can see that company’s data and lower companies’ data. Operation permission controls which functions those staff can use.

Can I create multiple admin accounts for different stores?

User management is where backend staff accounts are set up. Roles carry the data and operation permissions. Company management can add or edit companies and company business information. The list does not publish a packaged ‘one account per store’ wizard, or named default roles such as ‘store cashier.’ Confirm the screens in a demo and write down the role set you actually need.

Is this the same as store onboarding or enterprise rental accounts?

No. Store certification is how a store applies and gets reviewed. Enterprise approval is the company-booking path for corporate renters, including pre-trip or post-trip approval. Admin roles are about who on your team can see and operate the rental backend. Keep those cards separate.

Does the list define field-level access, such as hiding deposits from a clerk?

No. Operation permission is described as control over which functions a staff member can use. The list does not describe field-level access inside a screen, single sign-on, or a two-person approval chain. If you need a clerk who can see orders but cannot refund a deposit, confirm whether a function-level split can express that in a demo.

Related articles

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.