> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ferrufino-tech-solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Quickstart
> Sign in, create a workspace, capture your first case in under five minutes.
This guide assumes you already have an FTS account. If not, ask your administrator for an invite or start a free trial at [ferrufino-tech-solutions.com](https://ferrufino-tech-solutions.com).
## Step 1 — Sign in
Open [app.ferrufino-tech-solutions.com](https://app.ferrufino-tech-solutions.com) and sign in with the email your administrator invited. First-time users are guided through a short onboarding that sets up your name, preferred language, and initial workspace.
**This is not single sign-on.** An earlier version of this step promised SSO via Google, Microsoft and passwordless email links. Sign-in is handled by Clerk with **email and password** — the same statement [Security](/en/account/security) makes, where SAML SSO is listed as not available today (open item #102). Which additional sign-in methods are switched on in our Clerk instance is a setting outside this repository and is not stated here until it has been checked (open items #63, #93).
## Step 2 — Pick your workspace
A **workspace** is the container for a team or project. Cases and their evidence belong to one workspace. **Members and tags do not.** A member joins the **organisation** and carries one role across all of its workspaces, and tags live in a single list shared by the whole organisation — the *Popular tags:* row is built from every case your organisation has, not from the workspace you are looking at. An earlier version of this step said cases, evidence, tags and members were all "isolated from other workspaces"; two of those four were wrong. You will see a workspace switcher in the top-left of the sidebar.
If you are the first person from your organisation, a default workspace has already been created for you. **You cannot rename it** — the product has no such function (this line said "You can rename it" until 06.08.2026). Adding more does work: click **Settings** in the sidebar, then
**+ Add Workspace** in the **Organizations** section. The settings page has no
"Workspaces" section — this line said **Settings → Workspaces** until it was
corrected (06.08.2026). The only label in the product that reads exactly
"Workspaces" is a counter tile on the **Admin** page, which is a different
screen; the settings page groups workspaces under their organisation.
## Step 3 — Create your first case
Click **New Case** in the sidebar. The form opens with these fields:
1. **Workspace** — required; which workspace the case lives in.
2. **Title** — a short, specific description (e.g. "Connector X7 burned at 120 A load test"). Required.
3. **Observation / Symptoms** — what you saw. Required.
4. **Root cause** and **Resolution** — as far as you know; both may stay empty.
5. **Severity** and **Category** — chosen from the taxonomy lists.
6. **Tags** — typed freely, with suggestions from tags already in use.
7. **Language** — English or German.
**An earlier version of this step described a different form, and none of it was
real.** It named four fields — Title, *Summary*, *Details* and Tags. There is no
Summary field and no Details field; the case text lives in the three fields
above, and the German version of this page has listed them correctly since an
earlier round. It also promised that Details could be formatted "with Markdown
and embed images": Markdown is **not** rendered anywhere in the product — not in
the case view, not in the PDF export — and text cannot embed images at all;
pictures are attached separately as evidence in the next step. And it said tags
were picked "from your workspace taxonomy (component, failure mode, site,
severity)". Tags are free text that anyone can create by typing, they have no
groups, and *component*, *failure mode* and *site* are exactly the invented
dimensions that [Concepts](/en/concepts) already withdraws. Severity and category
are separate fields, not tags. (Corrected 06.08.2026.)
There is **no** automatic saving. The case does not exist until you click **Save as Draft** at the bottom of the form — if you close the tab before that, the text is gone. Once saved, it stays a **Draft** until you change the state.
## Step 4 — Attach evidence
Every verified claim needs evidence. Click **+ Upload File** in the Evidence panel — or drag the files onto it — and add:
* **Photos** of the part, defect, or setup — JPEG, PNG, GIF or WebP, up to 5 MB each
* **PDFs** of reports, specs, or procedures — up to 20 MB each
Nothing else is accepted: video, Office documents, CSV, log files and ZIP archives are refused at upload.
FTS stores evidence in an EU-hosted object store (Cloudflare R2). On the **Team** plan and above, FTS runs automatic text recognition on images and PDFs in the background, and you can read the text it finds at the evidence itself. **It does not become searchable** — an earlier version of this sentence said it did, but the search index holds only the four text fields of the case. For that one recognition step the file is sent to Anthropic in the United States.
Do not upload customer-identifying data unless your workspace is configured with the right retention policy. See [Security](/en/account/security).
## Step 5 — Send for review
When the case is complete, click **Submit for Review**. You do not pick a reviewer: every member of your organisation whose role is **Reviewer** or **Admin** sees the case in the review list and is notified, in the app and by email. In very large organisations the number of notifications sent per submission is capped; the review list still shows the case to everyone entitled to review it. Whoever opens it first decides, and there are exactly two decisions:
* **Verify ✓** → case moves to `Verified`
* **Request Changes** → case returns to `Draft` with their comment
**There is no third *Reject* decision, and no approval threshold.** One review
decides; nobody has to be assigned and no second reviewer has to agree. An
earlier version of this page promised a reviewer picker and a *Reject* that
marks the case `Deprecated` — neither exists. `Deprecated` is the archive state
a case reaches when someone deletes it, never the outcome of a review.
Once approved, you can optionally **Publish** the case. **This does not change who can see it** — every member of your organisation sees the case in every state, drafts included; publishing marks it as the canonical version (and hands it to the AI assistant, if you opt in). Until 06.08.2026, this line read "makes it visible to everyone in the **workspace**" — a per-workspace boundary that does not exist.
## Step 6 — Find it again
Open **Cases** and type into the field labelled **Search cases** above the list. It matches four fields of the case: title, observation, root cause and resolution. To narrow by tag, click the tag under *Popular tags:*; the select boxes above the list narrow by state, severity, category and workspace, and one switch limits the list to your own cases.
**`Cmd/Ctrl + K` is not a case search.** An earlier version of this step said it was, and that you could find cases by keyword, tag, component or the text extracted from attachments. `Cmd/Ctrl + K` opens a **navigation** palette over a fixed list of destinations (New case, Cases, Dashboard, Reviews, Settings, Billing, Profile) and matches nothing but those labels. There is also no *component* field, no filter by date, author or reviewer, and neither filenames nor extracted text are in the search index.
## Next
The model behind workspaces, cases, and reviews.
A fully-worked example.
Add reviewers and operators.
Use the AI assistant to draft and find cases.