Dashboard
/Open the authenticated beta shell and quick-action panel.
Spectra
BetaSpectra turns documents into searchable, analyzable information. Upload PDFs and office files, extract text and tables, ask questions across document sets, and export structured results for review or downstream workflows.
Beta operating manual
Spectra beta operating manual
Use the current Spectra beta safely and distinguish verified document-processing services from interface placeholders.
Audience, scope, and prerequisites
Covers the authenticated Spectra beta shell and approved document-processing workflows when enabled for the tenant. The current dashboard contains placeholder statistics and some quick-action destinations are not implemented in the verified interface revision.
Who this is for
- Authorized document reviewers
- Beta testers
- Spectra operators and support staff
Before you sign in
- A Spectra beta entitlement
- Approval to process the document classification involved
- A retained original document and an agreed validation method for extracted output
Roles and responsibilities
| Role | Access | Responsibilities |
|---|---|---|
| Reviewer | Open the beta workspace and use document functions exposed for the tenant. |
|
| Project operator | Organize approved processing work when project and upload surfaces are enabled. |
|
| Administrator | Configure beta access and processing integrations outside this manual. |
|
Assess beta readiness
The visible dashboard is not evidence that document upload, projects, or AI chat are operational for the tenant.
Verify an available workflow
Confirm the required surface and processing service before introducing real documents.
- 1Sign in
Open Spectra with the approved tenant identity.
- 2Ignore placeholder totals
The verified dashboard revision supplies mock zero-value statistics and empty recent-status data.
- 3Open the required action
Select Upload Document, Create Project, or Ask AI only for the intended beta test.
- 4Confirm a real destination
Proceed only if a functioning, authorized page loads rather than a missing route or placeholder.
- 5Record the tested release
Capture the visible version or deployment reference in the beta test record.
Expected result
The tester knows whether the required workflow is actually enabled and does not treat placeholder dashboard data as production state.
Prepare a document-processing test
Create a controlled test case with an original, expected output, and classification decision.
- 1Classify the document
Confirm whether the tenant and beta are approved for its contents.
- 2Retain the original
Keep an immutable source copy outside the beta workflow.
- 3Define expected extraction
Identify pages, headings, tables, or fields that will be checked.
- 4Use a safe file
Prefer a sanitized representative document while the workflow remains beta.
Expected result
The test has a safe source document and objective acceptance criteria for extraction quality.
Process and validate documents
Spectra’s Cortex engine advertises PDF, Office, spreadsheet, layout, and embedding processing, but the exposed workflow must be verified per release.
Submit a document when upload is enabled
Use the tenant’s functioning upload surface and preserve a traceable processing identifier.
Before you begin
- A verified upload route and approved test document
- 1Open Upload Document
Confirm the page is operational for the current tenant.
- 2Select the approved file
Check filename, type, size, and classification before submission.
- 3Choose available options
Select only processing modes documented by the active interface.
- 4Submit once
Wait for a job or document identifier rather than resubmitting during processing.
- 5Record the result
Capture job status, processing time, and any sanitized error text.
Expected result
One traceable processing job exists for the intended source document.
Validate extracted content
Compare text, layout, and tables with the original before downstream use.
- 1Open the processed result
Confirm it belongs to the expected source and job.
- 2Check text and page order
Compare headings, paragraphs, lists, and page boundaries.
- 3Check tables and structured fields
Verify row/column alignment, merged cells, units, and missing values.
- 4Record exceptions
Mark unreadable scans, layout errors, and unsupported elements.
- 5Approve or reject
Use the project’s acceptance criteria; do not silently correct an extraction without traceability.
Expected result
The extracted output has an explicit validation decision and documented exceptions.
Use AI output and exports responsibly
Search, summaries, comparisons, and chat are derived output and require source-based verification.
Review a document answer or summary
Validate generated output against the source document set.
- 1Confirm the source set
Check which documents and versions are in scope.
- 2Ask a bounded question
Request a specific fact, comparison, or summary rather than an unrestricted conclusion.
- 3Locate supporting passages
Open the cited or relevant source content and verify context.
- 4Record uncertainty
Identify missing sources, ambiguous extraction, or unsupported assertions.
Expected result
The generated answer is either verified with source evidence or clearly marked unsuitable for use.
Export an approved result
Export only validated output and keep its source and processing context.
- 1Confirm approval
Verify the extraction or analysis has passed the required review.
- 2Choose the available export
Use only formats exposed by the current release.
- 3Preserve provenance
Store the source identifier, job identifier, validation state, and export time with the output.
- 4Protect the file
Move the export to approved storage and apply the original classification.
Expected result
The exported result remains attributable to its original document, processing job, and validation decision.
Security and data handling
- Use synthetic or sanitized documents until the tenant workflow is accepted.
- Treat extracted text, embeddings, and AI output with the source document’s classification.
- Retain an immutable original for validation.
- Do not rely on placeholder dashboard statistics.
- Verify every generated conclusion against source material.
Known limitations
Read before relying on an unsupported workflow
These limits describe the source-pinned Spectra interface 1.0.0 beta scope and must be rechecked when the product changes.
- The verified dashboard uses mock zero-value data rather than live document, project, processing, or storage statistics.
- Quick actions reference upload, project, and chat paths that are not implemented as routes in the verified interface revision.
- The Cortex README confirms extraction components, not end-to-end tenant readiness or extraction accuracy for every format.
- Beta processing, retention, deletion, search, chat, comparison, and export behavior must be confirmed per deployment.
Troubleshooting
You cannot sign in to Spectra
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
- Open the application from the approved portal and complete sign-in again.
- Confirm that the correct organizational identity and tenant are selected.
- If access is still denied, record the time and request an entitlement check from support.
A documented action or navigation item is not visible
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
- Confirm the role and prerequisites listed for the procedure.
- Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
- Ask the product owner whether the feature is enabled for the tenant before reporting a defect.
A saved change or background operation is not visible
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search for the item by its stable name or identifier.
- Do not repeat irreversible or externally visible actions until the original operation status is known.
A quick action opens a missing page
Likely cause: The interface advertises a planned destination that is not implemented in the current revision.
- Return to the dashboard.
- Record the selected action and resulting URL.
- Ask the product owner for the enabled beta workflow; do not guess a direct API endpoint.
Extracted content differs from the original
Likely cause: The format, scan quality, layout, table structure, or extraction component is unsupported or ambiguous.
- Retain the original and mark the result unapproved.
- Record page-level examples without exposing confidential content.
- Retry only with an approved alternative format or configuration.
Contact support
Contact support when
- A repeatable Spectra error blocks an approved workflow
- Expected data, permissions, or tenant boundaries appear incorrect
- A security, privacy, compliance, or data-loss concern is suspected
- A real document may have entered an unapproved beta flow
- A processing result cannot be traced to its source or job
Include
- The page, action, and expected result
- The exact error text and time of occurrence, including time zone
- Your tenant, role, browser, and a sanitized record or item identifier
- Whether the problem can be reproduced and which troubleshooting steps were tried
Never include
- Passwords, access tokens, API keys, recovery codes, or session cookies
- Unredacted personal, health, financial, or other regulated data
- Private encryption keys or complete confidential documents unless an approved channel is provided