Understand Why a Module or Action Is Unavailable

Understand Why a Module or Action Is Unavailable

Overview

This guide will help you identify whether an unavailable action is caused by permission, subscription, settings, capacity, company, terminal, or data prerequisites.

Muhasib workspace access is an intersection of licensed features and role permissions. Some forms also hide controls or tabs based on features and data. Granting a role permission cannot enable a feature absent from the plan.

Who can do this

You need access to Use requires the rights and business authority described by the workflow. Database, licence, user, company, or system changes require the responsible administrator.

Before you start

Confirm the intended workstation, database, company/workspace, user or subscription context, and preserve any in-progress work before proceeding.

Before saving, check that the correct company is open and that you have permission to complete this task.

Where to find it

Follow the launch, wizard, login, company-selection, Back Office, or power path described in the procedure; the available starting screen depends on current installation state.

Understand Why a Module or Action Is Unavailable

Step 1: Record the missing/disabled action, current company, user, and terminal

Step 2: Check whether the parent module is visible

Step 3: Ask an administrator to verify the exact view/add/update/delete/custom role permission

Step 4: Review the active plan and feature entitlement in Licence Information

Step 5: Check whether a required setting, company assignment, location, terminal, fiscal

Check whether a required setting, company assignment, location, terminal, fiscal year, working period, account, stock record, or parent master is missing.

Step 6: If a capacity message appears, identify the named resource and

If a capacity message appears, identify the named resource and plan limit.

Step 7: After an authorized change, restart or sign in again when required

Check your work

The intended authorized action appears and succeeds for the correct role without exposing unrelated modules.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

If the expected result is not shown, stop repeated attempts, check the active database/workspace/user/licence context, preserve the exact message, and follow the related recovery article.

What to do next

Revision #0
Created 2026-09-04 09:21:09 UTC by Shah Rukh Saeed
Updated 2026-09-07 10:14:00 UTC by Shah Rukh Saeed