Getting Started

Visit /sign-up and create an account using either an email and password, or Single Sign-On via Google or GitHub. After sign-up, you are automatically redirected to your dashboard.

Email verification

If you signed up with email and password, you will receive a verification email from no-reply@ferrufino-tech-solutions.com within 60 seconds. Click the link to confirm your address. Unverified accounts cannot create or submit cases.

Two-factor authentication (recommended)

After your first sign-in, open Account → Security and enable two-factor authentication using an authenticator app such as Authy, Google Authenticator, or 1Password. 2FA is required by default for the Admin role on the Team and Enterprise plans.

Open Settings → Organizations and click Create Organization. An organization is the top-level container for your company, division, or business unit. You become its Admin automatically.

What to enter

• Name: the full legal or operational name (e.g. "Acme Engineering GmbH").
• Slug: a short URL identifier (e.g. "acme") used in invitation links and CSV exports.
• Region: your data-residency choice. All FTS data is stored in the EU; this setting selects between the Frankfurt and Dublin regions for compliance reporting.
• Plan: Starter, Team, or Enterprise. You can upgrade later from Settings → Billing.

Inside your organization, navigate to Settings → Sites and create a Site (a physical location such as "Munich Plant" or "Hamburg Test Lab"). Then add at least one Workspace under that site (for example "Engine Test Bench A" or "Assembly Line 3").

Why this hierarchy?

The Organization → Site → Workspace structure lets you model multi-location operations. Cases belong to a workspace, so team members only see relevant cases for their context. Workspaces can also have their own taxonomy overrides.

Recommended naming

• Sites: use city or building names, for example "Berlin HQ" or "Munich Plant 2".
• Workspaces: use functional areas, for example "CNC Mill Cell 3" or "Battery Validation Lab".

Before inviting your team, head to Settings → Taxonomy and customize the categorization scheme:

• Severity levels: the default scale is Low / Medium / High / Critical. Override it with your own scale (e.g. "Minor / Major / Showstopper").
• Categories: examples include Mechanical, Electrical, Software, Sensor, and Hydraulic. Adjust to match your domain.
• Tags: create reusable labels such as "assembly-line-3", "winter-cold-soak", or specific customer names.

Changes take effect immediately on all new case forms. Existing cases are not retroactively modified.

From Settings → Members, use the Invite Member form to send invitation emails. Each invitation includes a personalized link that is valid for 7 days. Choose a role:

• Operator: can create, edit, and submit their own cases, but cannot review or approve cases. Best for technicians, shop-floor engineers, or anyone capturing observations.
• Reviewer: everything an Operator can do, plus the ability to verify, request changes on, or reject cases from any Operator. Best for senior engineers or domain experts.
• Admin: full access including settings, billing, taxonomy, member management, and invitations. Best for team leads or owners.

Click New Case in the sidebar (or press N from anywhere in the app). The case form has these fields:

• Title: a short summary, for example "Spindle vibration above 6000 RPM".
• Workspace: the location or context this case belongs to.
• Observation: what you saw, heard, or measured. Include timestamps, error codes, and ambient conditions where relevant.
• Root cause: optional at draft stage. Your current hypothesis or the confirmed cause.
• Resolution: optional at draft stage. The steps that fixed the issue, or what was attempted.
• Severity, Category, Tags: values from your configured taxonomy.

Using a template

If your Admin or a Reviewer has created templates (for example "CNC spindle fault" or "Hydraulic leak"), select one from the template dropdown to pre-fill severity, category, tags, and structured fields. Templates dramatically reduce typing for recurring problem patterns.

AI Draft (Team plan and above)

Click AI Draft and paste raw notes, log excerpts, or a brief description. Claude structures the text into observation, root-cause, and resolution sections. Always review and edit before saving — the AI is a starting point, not a substitute for your judgment.

On the case detail page, click Attach Evidence to upload screenshots, photos, PDFs, or log files. Supported formats:

• Images: PNG, JPEG, and WebP. Automatic OCR extracts text from any error messages visible in the image.
• PDFs: full-text indexed; the first page is rendered as a preview.
• Logs: plain text, JSON, or CSV up to 10 MB each. Searchable line by line.

Files are stored on EU-based S3-compatible object storage with server-side encryption (AES-256). The attachment limit is 25 per case on Starter, 100 on Team, and unlimited on Enterprise.

When your case has at least a title, workspace, and observation, the Submit for Review button activates. Click it to change the case status from DRAFT to IN_REVIEW.

All Reviewers in your organization receive an email and an in-app notification. They can:

• Verify: promotes the case to VERIFIED status, with a green badge.
• Request Changes: returns the case to DRAFT with a required comment explaining what to fix.
• Reject: marks the case as REJECTED. It stays archived but is excluded from similarity search.

Once verified, your case becomes part of your team's knowledge base. It surfaces in:

• Similar Cases sidebar: when an Operator views a new case, FTS ranks the five most-similar verified cases by text similarity and tag overlap.
• Full-text search: verified cases are weighted higher in search results across the platform.
• AI Chat Copilot: Claude cites verified cases by ID when answering questions about past incidents.
• CSV export: Reviewers and Admins can export filtered case sets for offline analysis or audit purposes.