Skip to main content

Resolve Muhasib Sign-In Problems

How to Resolve Muhasib Sign-In Problems in Muhasib ERP

You will identify the likely sign-in failure and restore access through an authorized administrator without weakening security.

Overview

This article applies to the Muhasib lifecycle workflow named in its title on the inspected 2.0.0 build 12 baseline; production availability and labels require runtime confirmation.

Sign-in succeeds only when the credential matches an active, login-enabled, non-deleted administrator record. Permission and company problems may appear after authentication rather than as a credential error.

Purpose / Outcome

You will identify the likely sign-in failure and restore access through an authorized administrator without weakening security.

Permission Required

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

Before You Begin

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

🚨 Important
Make sure you are working in the correct company and have the required permission before you continue.

Navigation

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.

Resolve Muhasib Sign-In Problems

Step 1: Confirm Muhasib is connected to the intended database

Confirm Muhasib is connected to the intended database.

Step 2: Enter both User ID and Password; blank fields cannot authenticate

Enter both User ID and Password; blank fields cannot authenticate.

Step 3: Check Caps Lock and keyboard layout, then retry once

Check Caps Lock and keyboard layout, then retry once.

Step 4: If access still fails, ask an authorized administrator to locate

If access still fails, ask an authorized administrator to locate the user record and verify:

  • the User ID is correct;
  • Active User is enabled;
  • Allow Login is enabled;
  • the account has not been removed;
  • a valid role and company assignment exist.

Step 5: If the password must be changed, follow the approved user-management

If the password must be changed, follow the approved user-management process and communicate it securely.

Step 6: Sign out/restart when role or licence changes require the session

Sign out/restart when role or licence changes require the session to reload.

Result

Sign-in succeeds only when the credential matches an active, login-enabled, non-deleted administrator record. Permission and company problems may appear after authentication rather than as a credential error.

Verify the Outcome

The user reaches the correct company selection/workspace and can access only the intended modules and actions.

💡 Tip
Check the saved record or updated screen before you close the window.

Best Practices

  • Read each field before you enter or change information.
  • Check names, dates, amounts, and selections before you save.
  • Keep the confirmation or reference number when Muhasib shows one.

Common Mistakes and Troubleshooting

  • Do not reveal whether a guessed User ID exists to unauthorized people.
  • Do not enable a deleted or disabled account without confirming why it was restricted.
  • Do not share passwords through tickets, screenshots, or group messages.

Frequently Asked Questions

What should I check before I start?

Read Before You Begin and make sure the correct company is open. You also need the permission shown in Permission Required.

How do I know the task is complete?

The user reaches the correct company selection/workspace and can access only the intended modules and actions.

What should I do if my screen looks different?

Stop before saving. Check your Muhasib version, company, permission, and enabled features. If you are still unsure, ask your supervisor or Muhasib support.

Next Step

✅ Next Action
Continue with Sign In to Muhasib ERP.

Product: Muhasib ERP