Understand plans, limits, and features

A school’s subscription plan supplies default limits and feature values. An authorized school-specific override can change the inherited result. The effective value is still evaluated alongside role and record permissions.

Use the school dashboard or settings area to compare current usage with each displayed limit. Depending on the configured plan, limits can cover resources such as students, halqas, staff, storage, API keys, requests, or exports.

• A soft limit is a warning or operating threshold.
• A hard limit blocks additional use when reached.
• Current usage may count only records considered active by that resource’s rule.

Before adding a record near a limit, review inactive or duplicate records through the supported management screen. Do not delete history solely to avoid a limit.

A feature can be:

• enabled or disabled by the plan default;
• changed for the school by an authorized override;
• optional and still require school configuration;
• subject to a separate rollout or eligibility check.

For the current public matrix, see Feature availability. The displayed effective value for the active school takes precedence over a generic plan description.

These are separate questions:

1. Does the user’s role permit the action?
2. Does the record belong to the active school and fall within the user’s assignment or link?
3. Is the feature enabled?
4. Is capacity available?
5. Does any controlled rollout permit the action?

A school administrator role cannot bypass a disabled export or hard limit. A feature shown as available does not grant a sheikh or parent administrator permissions.

Capture the school name, displayed plan, feature or limit name, effective value, current usage, and time of observation—without including personal data or credentials. Ask the authorized platform contact to review the subscription or override. Do not infer the current state from an old invoice, announcement, or legacy feature name.