Help Center: In-App Guidance and Tutorials

Quartyl carries its own help: the Help & Feedback item in the application sidebar. This page is the map of that surface — what is in it, where each in-app topic leads in this manual, and how the two stay in sync.

The in-app help tab

The Help page has three tabs, labelled Documentation, Feedback and Support:

• Documentation — the in-app guide set, grouped the way the work is grouped: Getting Started, Analyst Guide, Manager Guide, Partner Guide, Intelligence & Assurance, and Support. Each entry is a short, role-scoped summary of one capability, rendered in place from markdown shipped with the app build.
• Feedback — the product channel: a subject, a category (Bug Report, Feature Request, Product Feedback, Documentation, Billing & Plan, Something Else), and the detail. Submitting posts a JSON payload to the deployment’s configured feedback webhook, carrying the subject, category, message, your name and email, the page you submitted from, and a priority flag. Where the firm holds priority support, that flag is set on the payload. See Contact Support.
• Support — the contact surface: the standard support card for every firm, and, where the firm holds the priority_support plan feature, the priority card instead. The contact strings and badges on those cards are frontend display defaults, not a contracted service level — the support terms you hold are the ones in your engagement agreement.

The eleven in-app guides, and their manual pages

Every in-app topic has a full page in this manual. The mapping is one-to-one by topic: the in-app doc is the summary, the manual page is the long form.

In-app group	In-app topic	Full manual page
Getting Started	Welcome to Quartyl	What is Quartyl, with the quickstart and the workspace tour
Getting Started	Studies & Workflow	Study lifecycle
Analyst Guide	Upload Wizard & Data Ingestion	Uploading your data file
Analyst Guide	AI Screening & Comparables	AI screening
Analyst Guide	Statistical Benchmarking	Statistical results
Analyst Guide	Results & Reports	The Excel report
Manager Guide	Review & Approvals	Manager review
Partner Guide	Sign-off & Archive	Partner sign-off
Intelligence & Assurance	Evidence Repository & Audit Trails	Evidence repository
Intelligence & Assurance	Industry Diagnostics & Risk Engine	Industry diagnostics
Support	Troubleshooting & FAQ	Troubleshooting

Two properties of the in-app docs:

• They are role-scoped. The Analyst Guide covers the work surface (screening, benchmarking, results); the Manager Guide covers review; the Partner Guide covers sign-off. A guide does not walk you through a step your role does not perform.
• They end where the manual begins. The in-app doc is the working summary; the manual page carries the full rules, the limits, and the edge cases. When a quick fix is not enough, follow the mapping above out of the app and into the long form.

The legal documents in the app

The in-app help also carries the firm’s legal documents. The application serves its own bundled copies at two routes — legal/privacy and legal/terms — rendered from markdown shipped in the app assets and linked from the claim-account checkbox and the login re-consent view. The links below are this site’s published copies of the same documents:

• Privacy policy — what Quartyl collects, how the data is handled, the AI data policy, and your data rights.
• Terms of service — the contract of the Service: accounts, your content, acceptable use, the no-professional-advice clause, termination.

The terms document is not decorative: Quartyl enforces a terms version at login. The deployed version is a configuration value, and a user’s stored acceptance is compared against it. When the version changes, login pauses at a consent step until the user reads and accepts the current version before a session is issued.

How in-app help stays in sync with this manual

The two surfaces are one content system with two lengths:

• The in-app docs ship with the application build — they are static documents rendered inside the Help tab — so every user sees the same help without a network fetch, and nothing goes stale between visits.
• This manual is the long form: the same topics at the depth a reviewer, an auditor, or a Firm Admin needs.
• Both sets live in the same product repository and are updated in the same release. When a capability changes, its in-app guide and its manual page are revised together. The mapping in the table above is the contract: an in-app topic with no manual page, or a manual page with no in-app entry point, is a documentation defect to report through feedback or support, not a user problem to work around.