DOCUMENTATION FAQ
Direct answers about using Anabhix documentation.
These answers apply to public guidance. Account, institution, contract, or environment questions require the authorized support or product channel.
Is all Anabhix documentation public?
No. Public documentation covers safe product concepts, tasks, and integration planning. Tenant-specific information, internal runbooks, privileged administration, security findings, credentials, and private API contracts are excluded.
Why am I asked to set up a school after sign-in?
The account flow must resolve an authorized school association. It checks signed tenant context and the accessible-school service before offering a new setup. If an existing active school is not recovered, do not create a duplicate; contact support with non-sensitive context.
Does a visible feature mean my plan includes it?
Not necessarily. Module availability, configuration, integrations, and support scope depend on the selected plan and approved implementation.
Where are API keys and production endpoints?
They are not published as universal values. Approved integration credentials and environment details are issued through the authorized integration process.
How do I report a documentation problem?
Use the contact path and include the page URL, the unclear or incorrect section, and the expected correction. Do not include private records or credentials.
Scope and limitations
- The visible answers are not a substitute for a customer agreement or institution policy.