Security
Forge works inside accounts your dealership already owns. Your store's own OEM portal login files the claim, your DMS is read-only, and a person completes every sign-in.
Last reviewed: September 9, 2026
What Forge reads
The warranty copy of a repair order, and any evidence document your store uploads when a claim needs one: a sublet invoice, a towing invoice, technician punch time.
It also reads the OEM portal your store files through, the same screens your administrator would open by hand: coverage and in-service dates, campaign and recall panels, labor time and op-code lookups. That is what turns a repair order into a claim the portal will accept.
Your DMS stays the system of record
Nothing is written back. Forge reads a repair order; it never books a line, closes a ticket, posts to a ledger, or edits a record. That is why there is no wiring project, no field mapping, and nothing for an IT vendor to schedule.
There are three ways the document can reach Forge, and they differ only in how it arrives. Most stores upload the warranty copy. Some have Forge pull it from the DMS client on the store's own machine, driving the same document search a service writer would click through, signed in as a user your dealership creates. Where a DMS offers one, an official read connection can deliver repair orders instead.
For the second path, ask for what an outside processor should get anyway: a role-restricted profile scoped to service and repair-order functions, parts lookup, and warranty coding, with payroll, banking, and vehicle sales gross left off. Your dealership owns that account, sees everything it touches, and can revoke it in a minute.
Credentials stay yours, one store at a time
Claims are filed through your own OEM portal user ID, issued by your dealership, scoped to the permissions you choose to grant. Forge does not hold a master account at any OEM and does not reuse one login across dealerships.
That is deliberate rather than incidental. Every claim Forge prepares for your store goes through your store's own portal account, so the work stays attributable to your dealership rather than to a vendor, and cutting off access is something you can do without calling us.
A person completes every sign-in
Forge never automates a portal login end to end. Single sign-on and any multi-factor or one-time passcode step are completed by a person, on purpose.
Toyota's TIS shows why the rule matters: the portal locks an account after five failed attempts. Anything that retries a stale password on its own will eventually lock out a store, so Forge does not retry logins.
Where repair order data goes
Forge is built on a small set of providers, each with a specific job. Your OEM portal is not on this list: that is your dealership's own account, reached with your own credentials.
| Service | What it handles |
|---|---|
| Document AI | Reads the uploaded repair order: VIN, mileage, labor lines, parts, and the technician's narrative. |
| Claim-building AI | Matches the repair against OEM labor operations and claim rules to build the draft. |
| Database and file storage | Repair orders, evidence documents, and claim status. |
| Backend hosting | Runs the Forge backend. |
| Website hosting | Serves forgedrive.ai. |
| Website analytics | Anonymized usage analytics on this website only. No dealership data. |
Dealer data is never sold, and never shared for advertising. A named list of providers is available to your IT team on request. See our privacy policy for how website contact information is handled.
Approval stays on your desk
Automatic submission is off until your store turns it on. Where a store does turn it on, it is deliberately narrow: a claim goes out on its own only if it passed Forge's pre-submission checks and Forge did not change anything on it. Anything Forge edited comes to a person. So does anything involving a one-shot money decision such as customer participation, where an under-claim cannot be appealed after the fact. On some OEM portals, submission is disabled in Forge outright.
Exceptions arrive with the reason attached, so the desk works judgment calls instead of retyping. Claim ownership does not leave the dealership.
Frequently Asked Questions
Does Forge write anything back into our DMS?
No. Forge reads the warranty copy of a repair order and builds the claim in your OEM portal. Where a store has Forge pull that document from the DMS client instead of uploading it, the automation only searches for and opens the document, the same steps a service writer clicks. Nothing is written back either way, so your DMS stays the system of record and none of this needs an integration project.
Does Forge use a shared login to file our claims?
No. Each rooftop files through its own dealer-issued OEM portal user ID, with the permissions your store chooses to grant. Forge does not operate one vendor account across dealerships, so the submitting user on every claim traces back to your store.
Can Forge log into our OEM portal on its own?
No. Sign-in is never automated end to end. A person completes single sign-on and any one-time passcode step. Toyota's TIS is the clearest example: the passcode step is deliberately left to a person, and because the portal locks an account after five failed attempts, Forge never retries a login blindly.
Who else sees our repair order data?
Forge uses commercial AI models to read the uploaded repair order and to match the repair against OEM labor operations and claim rules. Repair orders, evidence documents, and claim status live in a managed cloud database, and the Forge backend runs on managed cloud hosting. No dealer data is sold or shared for advertising. A named provider list is available to your IT team on request.
Do claims go out without our admin seeing them?
Not unless your store turns that on, and even then only for claims Forge did not touch. Automatic submission is off by default. When it is enabled, a claim files on its own only after passing Forge's pre-submission checks and only if Forge made no edits to it; anything Forge changed goes to your administrator instead, as does anything involving a one-shot money decision such as customer participation. On some OEM portals Forge does not submit at all, by design.
Questions this page does not answer
If your group needs something specific before a rollout, a vendor questionnaire, a review of what a store's portal user should be permitted to do, or a walkthrough of the upload path with your IT team, email stephen@forgedrive.ai and we will answer it directly.