403 in Controller Subdirectory access

In this type of structure I usually use something like this:

Taking advantage of the default controller As Home and the default method index.

Code:

- Controllers
    - Admin
        - Admin (Change to Dashboard)
        - AdminControler
        - Login (Change to Home)
        - SecureThis

In routes:

PHP Code:

$routes->group('admin', ['namespace' => 'App\Controllers\Admin'], function($routes)
{
    $routes->add('/', 'Home::index');
    $routes->add('/dashboard', 'Dashboard::index');
   { ... }
}); 


So your routes would look

Code:

http://mydevsite.vhost/admin/ - To login
http://mydevsite.vhost/admin/dashboard - To after login
http://mydevsite.vhost/admin/* - All after login

Or

Code:

-   Controllers
    -   Admin
        -   Home (Dashboard)
        -   AdminControler
        -   SecureThis
    -   Auth
        -   Home (Login)
            { All login features, forgot, reset password }

PHP Code:

$routes->group('auth', ['namespace' => 'App\Controllers\Auth'], function($routes)
{
    $routes->add('/', 'Home::index');
// { ... }
});

$routes->group('admin', ['namespace' => 'App\Controllers\Admin'], function($routes)
{
    $routes->add('/', 'Home::index');
// { ... }
}); 


Routes: 

Code:

http://mydevsite.vhost/auth/ - To login
http://mydevsite.vhost/auth/forgot_password - To forgot

http://mydevsite.vhost/admin- To after login, dashboard
http://mydevsite.vhost/admin/user - After login, assuming a controller called User

I think it becomes more readable. But, just a personal opinion.