Sign in with an authorised HOPAM account. Access is enforced by database policies, not by this page's appearance.
Do not share sign-in links. HOPAM staff will never ask for your password or one-time authentication code.
Your account is authenticated, but no active HOPAM role has been assigned. Contact the organisation owner through an independently verified channel.
Authenticated session
Independent security monitor. A separate Worker checks the public portal and Sanah AI endpoint every 60 seconds. It records service health, response headers and decoy-route probes. It does not scan personal devices or inspect private files.
These are simulated AI management roles for planning and reporting, not appointed human directors, legal officers or an incorporated subsidiary. Sanah reports to the verified HOPAM owner. High-impact actions remain approval-gated.
Private booking requests. Confirm availability and payment instructions manually; the public form does not take payment.
Advertiser enquiries are not paid campaigns. Review suitability, inventory, quotes and payment arrangements before approval.
Repository and backup architecture for HOPAM documents, policies, approved media and operational records.
Central orchestration across the HOPAM hubs and approved internal interfaces.
Sanah is read-only by default. Publishing, external messaging, spending, permission changes, financial changes and deletion require a recorded approval. Social platforms remain disconnected until their authorised OAuth/API setup is completed. The owner kill switch disables assistant-provider and external-tool calls.
Create and track budgets, milestones, risks, outcomes and visibility. New projects are private drafts.
Draft → review → approval → publish. Only approved-public content is eligible for the public knowledge interface.
Keep sources, original notes, historical claims and personal interpretations labelled distinctly.
Connection labels are not evidence of an active API. Authorise each provider separately; keep tokens server-side.
Private, authenticated AI assistance for research, teaching, institutional knowledge and planning. Sanah is read-only and uses only the active member's permitted HOPAM records.
Your private Sanah conversation will appear here.
External actions are not available. Publishing, external messages, spending, permission changes, financial changes and deletion require separate owner approval.
Record administrative actions and approval decisions. Avoid storing message bodies, passwords or tokens in audit details.
Only the verified owner can approve pending accounts and assign organisation roles.
The kill switch is enabled by default. AI and external tools remain disabled until their secure providers and policies are configured.
Review incoming commercial, institutional and delivery partnership enquiries. No enquiry creates a contract or funding commitment.
Record non-binding expressions of interest only. This is not a securities offer, investor solicitation or acceptance of funds.
Track planned, committed and actual entries by project and currency. Transfers and simulations are not profit, revenue, interest or investment returns. Never combine different currencies without an explicit conversion record.
Documents are stored in a private Supabase bucket. Only owners and administrators can upload or create signed download links in this initial release.