SKIT watches the activity logs from your Odoo system and looks for anything unusual — things like someone trying many passwords in a row, a new admin account being created out of nowhere, a server running out of memory, or a database error that keeps repeating. It flags these as anomalies so you don't have to read through thousands of log lines yourself.
You can also just ask it questions in plain English — like "Were there any login attacks today?" — and it will answer using your own logs.
Before SKIT can find anything, it needs your logs. There are two ways to get them in:
This is the first screen you see when you log in. Type a question about your Odoo logs, or click one of the ready-made questions on the left (like "Login failures / brute force" or "Prioritise for me") and SKIT will answer using your own log data — nothing made up, nothing from the internet.
Some things you can ask:
Clicking Ask AI anywhere in SKIT (for example, next to an item on the Dashboard) brings you straight to this Chat screen with that question already answered.
The Dashboard shows every unusual event SKIT has found, most serious first. Each row shows when it happened, which server it came from, how serious it is (Critical, High, Medium), and a short plain-English explanation.
Two buttons on each row:
The circle on the left side of the screen shows your overall risk score — the higher the percentage, the more your logs show serious problems.
This tab (only shown if your logs come from an Odoo database) lists every database change SKIT noticed — records being updated or deleted, timeouts, and access-denied events. Useful for tracing exactly what changed and who did it.
.log, .txt, or .csv files (100 MB each, max).web1.Uploading a file only stores it — SKIT doesn't look through it until you tell it to. Right below the upload box, you'll find a Run Collector Now section on this same page (it's also available under Settings, if you prefer):
Click Run Collector and watch the progress in the box underneath. When it finishes, check the Dashboard for anything it found.
Instead of uploading files by hand every time, install the Agent once on each server you want watched. It quietly keeps sending new log activity to SKIT in the background — no more manual uploads.
You can download it from the Settings page.
Same idea as Windows: download, run run_agent.sh, fill in the same four fields in the
window that opens, click Save & Start.
Many production Linux servers don't have a desktop at all — you connect to them with a terminal (SSH). The Agent now handles this automatically: if it doesn't find a screen to open a window on, it simply asks for the same information as plain text questions, right there in your terminal.
bash run_agent.shscreen or tmux so it keeps going after you disconnect).Next time you run it, it remembers your last answers and just asks "Use this configuration?" — press
Enter to reuse it, or type n to change something.
In SKIT, go to Settings → Log Receiver → Generate / Regenerate Key. Copy it immediately — for security, SKIT only shows it to you once.
Add and manage the people on your team. Each person gets a role:
Shows how much of your plan's allowance you're using — team members and storage — so you know when it's time to consider a bigger plan.
See your current plan, change to a different plan, or cancel. A few things worth knowing:
A record of important actions taken on your account — who did what, and when. Useful for keeping track of changes your team makes.
Change your own password here.
Generates the API Key the Log Forwarding Agent needs — see above.
Technical setting for connecting SKIT to the AI model that powers Chat and the anomaly explanations. Your administrator or SKIT support will usually set this up once and you won't need to touch it.
Download links for Windows and Linux — see above.
The same scan button described under Logs — this copy exists here too since it's also useful when you're already on the Settings page.
Uploading only stores the file — you still need to click Run Collector (on the Logs page or in Settings) to actually scan it.
An uploaded file is a snapshot of that moment only — anything that happens on your server afterward won't show up until you upload again. The Agent keeps sending new activity automatically, so detection stays current without you doing anything.
Yes. It automatically switches to asking for the same information as plain text questions in your terminal instead of opening a window. See The Log Forwarding Agent above.
Go to Settings → Log Receiver → Generate / Regenerate Key to create a new one. Any Agent still using the old key will need the new one entered too.
Contact whoever manages your SKIT account (usually your COMPANY_ADMIN) or your SKIT support contact.