Needs attention now
Devices awaiting approval, unapproved members and blocks appear at the top.
Who opened what, and when,
made visible.
Set users and sign-in rules from the admin console on your own server.
Lock important documents with a password, and choose what AI may read.
The easier collaboration gets,
the more questions operators have to answer.
From the admin home,
start with what needs handling now.
Devices awaiting approval, blocked IPs and sign-in failures are the first thing you see after logging in.
Security overview
Login attempts, failures and blocked IPs as numbers.
Member status
How many members there are and how many are unapproved, at a glance.
Security check
Group login failures by User-Agent and run a security test.
From sign-up to sessions,
account rules set by the organization.
Admins decide whether sign-up is open and how long passwords must be.
Repeated attacks
are blocked automatically.
Sign-in failures are counted per account, IP and device, and the block grows longer each time they repeat.
Important documents
are locked at the file level.
Set a password and the body is encrypted, so without it the file can't be opened or searched.
- Whole Markdown documents encrypted with AES-256-GCM
- Encryption key derived from the password with scrypt
- Encrypted documents excluded from the search index and previews
- AES-256 encrypted ZIP available for shared downloads
Admins, too,
split the work by role.
Super users, system managers and security managers each reach different menus.
Separated admin duties
Security managers handle security settings and logs, system managers handle servers and background services.
Permissions in one table
A check table shows which menus each role can enter.
File permissions by team and level
Sign-up defaults set file permissions, and each user can be changed separately.
Who did what, and when,
stays on record.
Every sign-in records IP, OS and browser, and files can be rolled back to earlier contents.
Webspace operations,
in the same admin console
Request and error trends, live connections and runtime status, checked from Webspace management.
Request and error trend
Requests, server errors and refused connections over 24 hours or 7 days.
Connections and runtime
The WebSocket dispatch queue with the DB pool, storage and average latency.
API traffic
Requests, errors and average response time per database and target, in a table.
Menu and settings search
Ctrl K finds an admin menu or setting and jumps to it.
AI and servers,
checked by operators themselves.
Choose the models AI uses and the tools external AI may call, and watch disk and service status.
After release,
security testing continues.
Attack methods and environments keep changing.
SetFN retests its security checklist with every update.
Checks that permissions and data stay consistent when several people touch the same file at once.
- Simultaneous creates or moves of one file apply only once
- Overlapping duplicate requests take effect once
- No over-approval when requests pile up at a limit
- Sessions hold when token refresh and reads overlap
Confirms that file and AI tool access scope stays the same after an update.
Keeps refining concurrent sessions, token refresh limits and failed sign-in handling.
Checks that encrypted documents don't leak through previews, search or version history.
Issues found in operation logs and audit records go into the next update.
Operators set the rules,
SetFN keeps testing.
Operators choose where data is stored and who opens it.
Issues found in operation go into the next update.