\Aksara\Laboratory\Core->parentModule()

The documentation and cheat sheet of our framework

parentModule() sets the module name used by permission checks.

Purpose

parentModule() sets the module name used by permission checks. It lets a controller customize Aksara Core behavior while keeping the request inside the built-in CRUD, rendering, permission, validation, and response pipeline.

When to Use

Use it near the beginning of a controller method to configure how Core handles the current request.

Reference

parentModule(string $module)

Parameters

Parameter	Type	Required	Default	Description
`$module`	`string`	Yes	-	Module name or module path used for permission lookup.

Return Value

static

Returns the current controller instance so it can be chained with other Core methods.

Behavior

parentModule() stores request-level configuration on the controller. Call it before the permission, rendering, or form-processing step that depends on it.

Basic Usage

$this->parentModule('administrative/users');

return $this->render('orders');

Advanced Usage

$this->setTitle(phrase('Orders'))
    ->setIcon('mdi mdi-cart-outline')
    ->setPermission();

Complete Example

namespace Modules\Orders\Controllers;

use Aksara\Laboratory\Core;

class Orders extends Core
{
    public function index()
    {
        $this->setTitle(phrase('Orders'))
            ->parentModule('administrative/users');

        return $this->render('orders');
    }
}

Result

The controller stores the configuration and applies it later in the current request lifecycle.

Notes

This method is chainable and returns the current controller instance.
Call configuration methods before setPermission() or render() when those steps depend on the configured value.
Order matters: call parentModule() and setMethod() before setPermission() when needed.