Portal User Workflow
What it is
The Portal User workflow covers the complete journey from receiving a compliance requirement set to submitting evidence and obtaining assessment results. This guide walks through each stage of that process.
Scenario: A subcontractor submits compliance evidence for a project requirement set.
When to use
Use this workflow when:
- You need to demonstrate compliance with a defined set of requirements
- You have evidence documents ready to upload
- You want to identify gaps before formal submission
Do not use when:
- You are configuring the platform (see Admin Workflow)
- You need to modify requirements or criteria (Admin function)
- You are debugging system issues (Admin function)
Prerequisites
Before starting, ensure you have:
- Platform access URL
- Evidence documents in supported formats (PDF, DOCX, XLSX, CSV, TXT, or ZIP)
- Understanding of which requirements your evidence addresses
- Sufficient time to upload and wait for processing (🧩 Template: timing varies by deployment and document size)
Step-by-step
Step 1: Access the portal
- Open your browser and navigate to the platform URL
- Navigate to the Portal (served at
/cmin this repo) - Verify you see the three-panel layout:
- Left panel: Requirements list grouped by criteria
- Center panel: Document management
- Right panel: AI copilot and assessment details
Step 2: Review the requirement set
Before uploading evidence:
- Expand each criterion in the left panel
- Read through the individual requirements
- Mentally map which of your documents address which requirements
- Note any requirements where you lack evidence
Step 3: Prepare your evidence
Organize your documents before uploading:
- Name files descriptively (e.g., "Access-Control-Policy-v2.1.pdf")
- Ensure documents are not password-protected
- Verify PDFs have extractable text (not just scanned images)
- Consider bundling related documents in a ZIP file
Step 4: Upload evidence documents
- Click Upload in the top toolbar
- Select one or more files from your computer
- Observe the upload progress indicator
- Wait for each document to reach READY status
Processing stages:
- UPLOADED → EXTRACTED → PARSED → INDEXED → READY
Step 5: Start an assessment run
Once documents are READY:
- Click Run Assessment in the toolbar
- Confirm the action when prompted
- Monitor the run progress indicator
- Wait for the run to reach COMPLETED status
Expected duration: 🧩 Template — Timing varies by deployment, document count, and system load.
Step 6: Review assessment results
For each requirement:
- Click the requirement in the left panel
- View the assessment status: COMPLETE, PARTIAL, or MISSING
- Read the AI reasoning explaining the assessment
- Review citations pointing to specific evidence locations
Step 7: Address gaps
For requirements marked PARTIAL or MISSING:
- Review the AI reasoning to understand what's lacking
- Check generated tasks for remediation guidance
- Either:
- Upload additional evidence that addresses the gap
- Note the gap for remediation before final submission
Step 8: Generate exports (optional)
Once satisfied with coverage:
- Locate the Export option
- Select the desired export format
- Download the compliance report for submission or records
Example
Scenario: Uploading an access control policy and running assessment.
Input:
- File:
Access-Control-Policy-v2.1.pdf(12 pages) - Requirements: 5 requirements under "Access Management" criterion
Process:
- Upload the PDF → Status progresses to READY
- Start assessment run → Run completes
- Check results: (🧩 Template — example values below)
- Requirement "Documented access control procedures" → COMPLETE (0.94 confidence)
- Requirement "Privileged access management" → PARTIAL (0.62 confidence)
- Requirement "Access review schedule" → MISSING (0.15 confidence)
Output:
- 1 requirement fully satisfied with high confidence
- 1 requirement partially addressed—additional detail needed
- 1 requirement not covered—evidence required
Troubleshooting
Document processing is slow
Symptom: Documents take unusually long to reach READY.
Causes and fixes:
- Large file size: Split into smaller documents
- Complex formatting: Simplify or re-export as plain PDF
- System load: Wait and try again during off-peak hours
Assessment confidence seems wrong
Symptom: AI marks requirement as MISSING but you know evidence exists.
Causes and fixes:
- Evidence is in an image without OCR: Re-export with text layer
- Terminology mismatch: The AI looks for specific phrases—check if your document uses different terminology
- Evidence is indirect: The AI expects explicit statements, not implied compliance
Run fails repeatedly
Symptom: Assessment runs fail without completing.
Causes and fixes:
- Service unavailable: Wait and retry
- Specific requirement causes crash: Report to administrator with details
- Session expired: Refresh page and re-authenticate
Cannot see previously uploaded documents
Symptom: Documents you uploaded earlier are not visible.
Causes and fixes:
- Different tenant context: Verify you're in the correct tenant
- Documents were deleted: Contact administrator
- Page not refreshed: Hard refresh the browser
Export fails or produces empty file
Symptom: Export action fails or downloads an empty file.
Causes and fixes:
- No completed run: Ensure an assessment run finished successfully
- Run has no assessments: Check that requirements were evaluated
- Browser blocking download: Check popup blocker settings
UI is unresponsive
Symptom: Clicking buttons has no effect.
Causes and fixes:
- JavaScript error: Check browser console for errors
- Session timeout: Refresh the page
- Network issue: Check your internet connection
Wrong requirements displayed
Symptom: The requirements shown don't match your expected pack.
Causes and fixes:
- Wrong pack assigned to tenant: Contact administrator
- Criteria not imported: Contact administrator to verify setup
Assessment shows unexpected citations
Symptom: AI cites documents that seem unrelated.
Causes and fixes:
- Vector search matched on tangential content: Review the cited passage for context
- Multiple documents cover similar topics: This is expected behavior—AI considers all evidence
Gotchas and edge cases
-
ZIP files create parent-child relationships: When you upload a ZIP, extracted files show as children of the ZIP. Deleting the parent deletes all children.
-
Re-uploading the same file: The platform uses SHA256 hashes for deduplication. Identical files won't be reprocessed, but modified versions will.
-
Running assessment with IN_PROGRESS documents: Only READY documents are included. Documents still processing are excluded from the current run.
-
Concurrent runs: Only one run can be IN_PROGRESS at a time per tenant. Wait for completion before starting another.
-
Assessment results are point-in-time: If you upload new documents after a run, those documents won't affect past assessment results. Start a new run to include them.
-
Image files: PNG/JPG files are processed but typically contain minimal extractable text unless they're scanned documents with OCR.
Related links
- Evidence Submission and Mapping - Deep dive on evidence preparation
- Reviewing Results and Responses - Understanding assessment output
- Runs, Snapshots, and Replay - How assessments work
- Evidence, Requirements, and Assessments - Core data model
- API Reference - Programmatic access
- Quickstart - Condensed getting-started guide