Loading admin panel…
Platform Configuration
Manage features, app tiles, visibility, and knowledge base content for the Wallman Family Platform.
App tiles
Configure which apps appear in the launcher and who can see them.
Layout
Article visibility by role
Control which Cognito groups can see articles at each classification level.
| Classification | Platform Admin | Platform Developer | Community Member | Guest |
|---|
Guest access to public articles
Allow users without a Cognito account to read public-classified articles
Feature flags
Enable or disable platform features. Disabled features are hidden from all users.
Auto-publish status
Last CI run results for
publish-kb-articles pipeline job.Loading…
Auto-publish toggle
Enable or disable automatic KB article publishing on merge to main.
Auto-publish enabled
When enabled, CI publishes articles with
status: published on every merge to main.AI Agent Instructions System Prompt
Knowledge File knowledge.md
Documents Source PDFs
Drop PDFs here or click to choose files
Statutes, guidance, and framework documents only. Max 20 MB per file.
Statutes, guidance, and framework documents only. Max 20 MB per file.
Instructions (system prompt)
- Role & scope: Start with a one-sentence role definition. Example:
"You are a regulatory reference assistant for CT state IT executives." - Citation requirement: Always require citations. Example:
"Always cite the specific regulation, section, or document you are drawing from." - Boundaries: Be explicit about what the AI should NOT do. Example:
"If the answer is not in the provided materials, say so clearly. Do not speculate or draw on general knowledge." - Tone: Set expectations. Example:
"Be direct and practical. Flag when a question requires legal counsel." - Escalation: Define where users should go for sensitive topics. Example:
"For questions involving PII, PHI, CJI, or FTI processing, direct users to the DAS-BITS security office."
Knowledge file (knowledge.md)
- Start with a one-paragraph scope statement describing what this KB covers.
- Include a glossary of key terms and acronyms (CTDPA, DAS-BITS, PA 16-189, etc.).
- For each uploaded document, write a 2-3 sentence summary of what it covers and why it matters.
- Add "What this means for you" annotations for complex requirements.
- List authoritative sources with URLs so the AI can cite them precisely.
Documents to upload
- CT statutes and regulations (PDFs from
ct.gov,cga.ct.gov) - Federal guidance (NIST, CISA, IRS Pub 1075, CJIS Security Policy)
- Agency guidance documents and frameworks
- Keep total document volume under ~150 pages to stay within AI context limits
What NOT to upload
- Any document containing PII, PHI, CJI, or FTI
- Internal CT network diagrams or system architecture documents
- Non-public state contracts, procurement records, or budget documents
- Documents under attorney-client privilege
How the AI uses these
- Instructions → become the AI's system prompt (standing orders for every conversation)
- Knowledge file → provided as primary context, read on every query
- Uploaded documents → extracted to plain text, concatenated into context after the knowledge file
- All content stays within the context window (~150K tokens total). If you upload large documents, consider adding concise summaries to the knowledge file instead.