Skip to content
← Services

How can we improve Services?

Services: Reporting

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Individual User ID Reporting

The merchant would like a feature to allow individual user id to pull reports that only show what that individual user id has captured in sales. We are an academic institution with certain levels of information (donors) that we don't want student employees seeing. However still want the students to have access to the reporting function. So we need them to be able to pull reports but have certain information blocked out to their specific account reports

Thank you, btw the devs for Clover are the best!

3 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Justin Heacock shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Comments are closed An error occurred while saving the comment
  • Riders Cab commented  ·   ·  Report

    Clover should provide a feature , where user can access only reports of particular device and only their individual reports. Our business has multiple terminals and those terminals are assigned to different individual user ids. we want to provide access reporting to particular user to a particular device only. Pls try to find a solution and reach us out. Some of other providers have those features.

  • ravi commented  ·   ·  Report

    We are a taxi company with over 100 owners and employees, operating under a single Clover merchant account. Looking ahead, we would like to request the development of a feature that enables transaction and report visibility to be restricted on a per-device basis.

    In our future setup, we envision that each Clover terminal (assigned to a specific vehicle) will only be able to access transactions and reports generated by that specific device. It is important that owners or employees do not have visibility into data from other vehicles or terminals.

    Because our drivers rotate frequently, we use simple, unique passcodes to manage access per vehicle (e.g., Car 1: 0001, Car 2: 0002, etc.). At present, this is the most efficient way for us to manage user access securely.

    We kindly ask Clover to consider implementing a device-level visibility restriction feature to meet our operational requirements for confidentiality and secure data segregation across a shared merchant account.

    Thank you for your time and consideration.