There is a possible way that you use CustomBoard. You create series of custom board, each customboard for each of your old report. Inside the view of custom board, you use iframe to load the old report. The only problem is how to make the iframe has full width and the the height is flexible. I think this is the quickest way.

The example of CustomBoard is here. The HomeBoard is extended from CustomBoard. The CustomBoard will have a view which you can provide custom html/css or code.

Yes, I totally understand your need. I am sorry for giving you very general instruction. The hack way that I thought that will work is to use iframe within custom board to load old reports. But after consulting with Karl, he suggested that you should hold on moving old reports to dashboard as it is not designed yet to be compatible. Our dev.team will take your requirement for future improvement as we believe there will be the need for this from other customers as well. We thank you very much for your patience and we will keep you update on this.

I also have the same believe as you for users with old reports. Btw, I change your topic title for better description and mark your topic as suggestion. Thank you very much for your trust and your continuous supporting us through years. We are very appreciated! We promise to give you working solution on this.

May I know in your authentication in your current system. How do you provide login and authenticate user and prevent unauthorized people from accessing reports?

The simplest way I think of is that, inside the authenticate() of Login, (refer to Authentication#login). you do:

            ->authenticate(function($username,$password){
                //You can make database connection in here to authenticate $username or password
                //Return User class when it is authenticated

                if($username==="johndoe" && $password==="johndoe") {
                    //This is when your user is valid,
                    $_SESSION["login_id"] = 1; // it is up to you
                    return User::create()
                        ->name("John Doe")
                        ->id(1)
                        ->roles(["guest"]);
                }
                return null;
            });

The idea is that .. when user is authenticated succesfully, you assign $_SESSION["login_id"] to id of user who login. And then, inside the report page (loaded inside iframe) you check permission:

if(isset($_SESSION["login_id"]))
{
    $report = new YourReport;
    $report->run()->render();
} else
{
    echo "Unauthorized";
}

Hope that you get my idea.

Please let me know if my explanation is still unclear.

Sure, there will be another step but let complete this first, I will guide you next.

That's great. The next step is when user logout, as you see when dashboard user logout, we need to clear the $_SESSION["login_id"]. We do it by following:

1) Create your own MyLogin page which inherited from our Login page and adding further actionLogout

class MyLogin extends \koolreport\dashboard\pages\Login
{
    protected function actionLogout($request, $response) {
        parent::actionLogout($request,$response);
        $_SESSION["login_id"] = null;
        // unset($_SESSION["login_id"]); // or this code
    }
}

2) Now in your App of dashboard, you use MyLogin instead of our Login inside login() method:

protected function login()
{
    return MyLogin::create()->authenticate(...);
}

So basically, when user hit logout, the session value will be removed and user could not access the report inside iframe directly.

Hope that helps.

You are welcome :)