Troubleshoot permissions and unavailable features

A hidden control or access-denied response can be correct. Identify the effective role and feature conditions before changing membership or plan settings.

1. Verify the active school.
2. Verify the signed-in account and effective role.
3. Check that the membership is active and its invitation was accepted.
4. For a sheikh, verify assignment to the relevant halqa or learner.
5. Confirm that the resource belongs to the current school and active context.
6. Check the school’s effective plan, limit, and feature state.
7. For controlled features, check whether separate rollout or platform eligibility is required.

• School administration control missing: only a school administrator can perform it.
• Sheikh sees fewer learners: assigned-halqa boundaries apply.
• Parent sees no child: the invitation may not be accepted or linked in the active school.
• Feature is unavailable: plan, feature, limit, or rollout conditions are not all effective.
• API read works but write fails: write capability and scopes are separate.
• Limit reached: remove or archive only legitimate records, or use the approved plan-change process; never alter history to evade a limit.

The school administrator should:

1. identify the minimum correct role;
2. update or re-invite the intended person;
3. assign only required halqas;
4. verify access using the person’s own account;
5. remove stale membership when it is no longer needed.

Do not promote someone to administrator merely to fix one task. Do not reuse another user’s session.

Provide the school, screen, approximate time, expected task, effective role, and visible error. Do not send passwords, invitation tokens, API keys, or another learner’s record.

See role permissions and feature availability.