Designated Driver Apps

Designated Driver Admin Roles: Own-Company Data vs Subordinate Companies

If you run one designated-driver company, almost any admin login looks fine. The trouble starts when you add a second company, or a third branch that should not read the first branch’s orders. Head office still needs a view that includes subordinates. Branch staff should see their own books. If you solve that with a shared password and a verbal “just don’t click the other menu,” you do not have a permission model. You have a leak waiting for a busy Friday.

Ptaxi’s designated driver app documents this under permission management. Company management lets you add and edit companies and company business information. User management is where you set backend administrator account information. Role management sets two things for those administrators: data permissions and operation permissions. Data permissions have two documented scopes: own level, which can only see the administrator’s own company data, and own level and below, which can see the administrator’s own company and subordinate companies. Operation permissions control which features a backend administrator can use.

Company records come first

Before you argue about roles, you need company records that match the way you actually operate.

Company management lets staff add and edit companies and company business information. Use that to create the head-office company and each branch or subordinate company you intend to keep separate. The form is not published field by field, and neither is the depth of the tree or what happens if you delete a company that already has orders. Walk the form in staging, write down the fields you will require, and decide who is allowed to create a new company.

Do not skip this step and hope a role will invent a company boundary later. Data permissions are described in terms of “own company” and “subordinate companies.” If those companies do not exist as records, the scopes have nothing to attach to.

If your group only has one company today, still open this screen once and confirm that every admin you create will belong somewhere.

Two data scopes, and no third one on the list

Role management’s data permissions are the procurement question most buyers actually care about.

Own level means the administrator can only see their own company’s data. That is the branch clerk, the local dispatcher, or the city manager who should not browse another company’s orders, drivers, or books.

Own level and below means the administrator can see their own company and subordinate companies. That is the head-office role: the person who needs the local books and the branches underneath.

Name them that way in training. Do not invent a third documented scope such as “all companies on the platform,” “every franchise in the country,” or “peer companies at the same level.” Those options are not given here. If a person needs to see a company that is not their own and is not a subordinate, that is not a role you can honestly describe from this module. You may need a different company tree or a different login — confirm it in staging, and do not print “global admin sees everything” on a slide unless the build actually shows a scope that was never named.

“Subordinate” only means what your company tree says it means. If two city companies are siblings under a holding company, an own-level admin at city A should not see city B. An own-level-and-below admin at the holding company should see the holding company and the cities beneath it. Draw that tree on one page before you click save on the first role.

Data permissions are about seeing data. They are not, by themselves, a promise about exporting ledgers, masking salary fields, or hiding a single column on an order. Field-level access control is not described here.

Operation permissions are a feature checklist

The second half of a role is operation permissions. These control which features a backend administrator can operate.

You are deciding whether this login can open a given back-office function — maybe company management, maybe a finance menu, maybe a campaign screen. You are not being handed a documented matrix of every checkbox in the product. The menus are not itemized in the feature description.

So the work is practical. In staging, create a role, walk every permission group the screen actually shows, and write down the checked items. Then log in as a user who has only that role and try the two or three actions you care about: opening orders, editing a company, or creating another admin. If a button is visible and should not be, uncheck it and try again. If a button is missing and the person needs it, check it. The role is what you verified, not what a brochure guessed.

Keep operation permissions and data permissions in the same conversation, but do not collapse them. A person can have a wide feature set and still be limited to own-company data. A person can have own-level-and-below data and still be blocked from a dangerous feature. Those are two knobs. Set both.

User accounts sit on the role, not the other way around

User management lets you set backend administrator account information. This is how a person gets a login. The role is how that login is limited.

Create users after you have at least one carefully checked role, not before. If you create five logins first and then invent roles later, you will spend a week retrofitting access. Give branch staff the own-level role you already walked. Give head-office staff the own-level-and-below role you already walked. If someone needs a narrower feature set, make a third role with the same data scope and fewer operation permissions, then assign it.

Drivers and passengers do not use this same role model. These tools are for backend administrators. A driver app login is not an admin role. A passenger account is not an admin role. Do not brief your operations team as if a driver can be granted “own level and below” and start reading subordinate company ledgers. If single sign-on, IP allowlists, or an audit-log export matter in your market, ask for them as a separate requirement and confirm what the build actually offers.

What not to promise in an access review

Do not promise a third data scope that sees every company on the platform. Two scopes are documented: own level, and own level and below. Do not promise field-level access control — hiding one column or one amount inside a screen the user can otherwise open. Do not promise single sign-on, IP allowlists, mandatory multi-factor authentication, or a downloadable audit trail as features of this role module. Do not say that drivers and passengers inherit these roles. Do not claim you already know which exact menus are in operation permissions; you will know after you walk the role in staging and write down the checked items. And do not treat company management as a decorative org chart. It is the structure data permissions rely on.

A short ops checklist before you issue the first branch login

  • The company tree is drawn on one page: head office, subordinates, and no informal “ghost” branches that exist only in a group chat.
  • Those companies exist in company management, and someone has edited the business information you actually need.
  • Two data-permission roles are named in your internal language the same way the product means them: own level, and own level and below.
  • Each role’s operation permissions have been walked in staging. The checked features are written down. A test login has tried the critical actions.
  • Backend admin accounts are created in user management and assigned those roles. No shared password is treated as a permission model.
  • Drivers and passengers are not described as using this role module.
  • A request for “access to all companies” is either redesigned into a true parent-and-subordinate tree, or it is refused until the build shows a scope this module does not name.

If a branch manager can open another branch’s books after that checklist, you have a tree problem or a role problem. Fix it before you add more users.

Close

Multi-company designated-driver operations usually fail in a boring way: the wrong person can see the wrong books, or the right person cannot see a subordinate at all. The product handles that with company records, backend admin accounts, and roles that split data scope from feature access. Own level stays on one company. Own level and below includes subordinates. Operation permissions limit what that person can actually do.

That is a procurement fact you can test. Look at permission management in Ptaxi’s designated driver app. If you want a demo, bring a simple tree — one parent, two branches — and walk an own-level login and an own-level-and-below login through the same order list. The useful test is whether each administrator sees the companies they should, and none of the companies they should not.

Frequently asked questions

What data can a designated driver admin actually see?

Role management offers two data-permission scopes. Own level can only see the administrator’s own company data. Own level and below can see the administrator’s own company and subordinate companies. A third scope such as all companies on the platform is not documented. Draw the company tree first, then assign the matching role.

What do operation permissions control?

Operation permissions control which features a backend administrator can use. The product does not publish a menu-by-menu list in the feature description. Walk the role in staging, write down the checked items, and log in as a test user to confirm the critical actions.

Do drivers or passengers use these same admin roles?

No. User management and role management are for backend administrators. A driver app login and a passenger account are not this role model. Do not brief operations as if a driver can be granted own level and below and start reading subordinate company ledgers.

Where do company records and admin logins get set up?

Company management lets you add and edit companies and company business information. User management is where you set backend administrator account information. Create the company tree first, define roles with data and operation permissions, then create user accounts and assign those roles.

Related articles

Designated Driver Account Managers and Referral Rewards

Night-time designated-driver volume often comes from a person, not a billboard: a venue host, a regular rider, or a driver who brings a friend. The product has an account-manager path for promoters and a separate invite-and-earn campaign tool. If you never configure a campaign, the refer-and-earn screen is only a download link.

· 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.