Welcome
Your client at a glance.
Devices
Every managed endpoint, live.
| Device | Status | Actions | |||||
|---|---|---|---|---|---|---|---|
Alerts
Only problems that persist. Grouped, quiet, and they clear themselves when the problem goes away.
Patches
Windows updates across the fleet. Approved updates install inside each client's maintenance window.
Missing updates
| Update | PCs | Approval | Actions | |
|---|---|---|---|---|
MeshGo approvals
| ID | Ability | State / expiry | ||
|---|---|---|---|---|
MeshGo remote sessions
| Agent | Session | State | Expiry | Recording |
|---|---|---|---|---|
Maintenance windows
Each client follows the default unless it has its own window. Nothing installs by itself until patching is turned on. "Declined" always wins over auto-approval.
| Client | Patching | Actions |
|---|
Operations
Endpoint checks, maintenance windows, rollout visibility and remote-support groups. Facts are read from Fixon; peer approvals and sessions stay with their owners.
Software rollout detail needs the software-deploy permission. Patch activity and endpoint checks remain visible.
Endpoint check status
| Device | State | Actions | ||||
|---|---|---|---|---|---|---|
Maintenance windows
| Client | Patching | |||
|---|---|---|---|---|
Software and patch rollouts
| Rollout | Type | State | Actions | ||
|---|---|---|---|---|---|
Remote support groups
| Group | Devices | Online | Actions | ||
|---|---|---|---|---|---|
Parity gaps
- Loading documented gaps…
Automation
Saved fixes and schedules — with a clear target and a real run record.
| Script | Progress | Actions | ||
|---|---|---|---|---|
A schedule runs the script's current version as a normal rollout (5 PCs at a time, offline PCs wait). It runs as the person who last saved it and stops if they lose access.
| Script | Runs on | Actions |
|---|
Clients
The companies Cyber7 supports.
| Name | Status | Domain | Actions | |
|---|---|---|---|---|
Approvals
What Claude asked to do. Nothing changes on a device until a person approves it here.
Approving runs exactly the text shown, as the agent (SYSTEM / root). Requests expire after 15 minutes. Every request, decision and result is in the audit log.
| Request | Status | Actions | ||
|---|---|---|---|---|
Users
Cyber7 technicians. Client users are managed from Clients → Users.
| User | Role | Clients | Status | Actions | |
|---|---|---|---|---|---|
Team
People who can sign in to your client.
| User | Role | Status | Actions | |
|---|---|---|---|---|
Activity
Recent changes recorded for your client.
| When | Action | |
|---|---|---|
Software
Approved software you can install on managed PCs.
Only software listed here can be installed. Each PC checks the file's fingerprint and the publisher's digital signature before running it, and a small pilot goes first.
| Software | Version | Actions | ||
|---|---|---|---|---|
Deployments
| Software | Status | Progress | Actions |
|---|
Audit log
Append-only and hash-chained. Nothing here can be edited.
| When | Who | Action | ||
|---|---|---|---|---|
Service Desk
The live C7NTAX ticket queue. Fixon reads it; C7NTAX owns it.
| Updated | Ticket | Subject | Status | ||
|---|---|---|---|---|---|
Report center
Governed exports and saved operational views. No second data warehouse.
Fleet health
Devices, client mapping, online state, OS, last seen and tags.
Alert register
Severity, state, check, message, count and timing for linked devices.
Patch job register
Windows scan/install jobs, state, summary, reboot flag and timing.
Data sources
Every figure names its owner; Fixon does not invent a second source.
Exports are scoped by the same permissions as the list they come from. Saved views and scheduled packs are the next report slice.
Settings
The remote access engine and AI access.
AI access
Let Claude look at devices, and ask you before it changes anything.
Claude connects through MCP with a personal token. It can look around on its own. Anything that changes a device shows up here in Fixon as an approval prompt with the exact command, and runs only if you approve it.
- Look at clients, devices and hardware details
- Ask to run a command, if the token allows it
- Ask to restart, shut down, sleep or wake a device, if the token allows it
- Approve anything, including its own requests
- Touch users, passwords, settings or tokens
- Use remote desktop, terminal or file transfer
- Ask for commands that touch passwords, accounts or credentials, or that hide or download code. Those are blocked before you see them.
Your tokens
| Token | Status | Actions | |||
|---|---|---|---|---|---|