Traffic, last 30 days
Requests and blocks reported by your nodes
Open alerts
Needs attention
Offline nodes and nodes with alerts
Customers
Created when a customer's first node enrols with a valid WEES Warden licence. Licence details come from the licence server or the nodes' reports.
Reports
Every site visited, by user, IP address and device, from every node: rolled up per hour with the first and last visit and how many requests. Click any name to see only that user, device, IP or site. Exact per-request times are in each node's own dashboard (Search).
Custom report
A branded PDF of the filters above (customer, node, user, IP, device, site and dates) with the sections you choose. Pick a period here or set the dates above.
Include
Requests over time
Managed policy
Nodes with cloud.managed_policy: true take the most specific policy: their own, else their customer's, else global. Network, AD and listener settings always stay on the node. Every publish is a new version; roll back from the history.
Some customers have their own detailed policy (shown as Custom below). It's kept as it is; edit it in Advanced.
Groups
Who gets which policy, the same on site, on cloud nodes and for roaming laptops. Add security groups, users, device names (wildcards like IT-*), IP addresses or networks, and VLANs: matching any of them puts someone in the group. Works with or without Active Directory: without it, use device names, IP addresses and VLANs (and, for roaming laptops, the computer's own users and groups). Groups are checked from the top and the first one someone is in decides their policy.
Customers on the cloud node
Each customer (tenant) on a cloud node gets the policies below, unless you pick one for them here. New customers start on the node's default policy.
Policies: what each group gets
Someone in no group gets the first policy whose own AD groups, networks or VLANs match, else the default policy below.
Every policy
These lists are added to each node's own (which always allows Windows Update, Microsoft 365 and RustDesk). Enter sites as names, e.g. youtube.com; pasted web addresses are trimmed to the site.
Download cache
Big downloads (Windows and Office updates, consoles, game stores) come from the internet once, then from the site's own cache. Each site needs a cache server set on its node; nodes without one ignore this.
Public blocklists
Lists maintained by others, the kind pfBlockerNG and Pi-hole use. Each node downloads the ticked lists daily. Tick a list here, then block it in a policy above.
Your own lists
A name and the sites in it, one per line. Each list appears as a category in the policies above.
History
DNS
How nodes running the DNS server look names up, kept apart from web policy. Each site's own settings (domain controllers, the secondary, forced DNS) are in the node's /etc/wees-warden/dns.yaml. A change here is published as a new version for the scope, and nodes apply it within a minute.
Nodes' DNS servers
What each node in this scope reports: how it resolves, whether it's answering, its AD domains and secondary, and (cloud nodes) the customer sites allowed to use it.
Upload a release
Sign on the build machine first: make sign VERSION=v1.4.0 in wees-warden, then paste the signature from the .sig.json. Unsigned builds are refused here and on every node.
Releases
Users and roles
Who can sign in to WEES Cloud, and what they can do. Give a customer's own staff an account limited to their company: they see only its nodes, policy, reports and alerts. Anyone with a @wees.uk address is WEES staff and always sees every customer and node.
| Role | Can do | For |
|---|---|---|
| Viewer | Read-only: dashboards, reports (who went where, blocked sites), alerts and policy | Customer managers, safeguarding leads |
| Operator | Everything a viewer can, plus change and publish policy, acknowledge alerts, quarantine and node commands | A customer's IT admin |
| Admin | Everything for every customer, except managing users | WEES staff |
| Owner | Everything, including users and the WEES Cloud licence | WEES staff |
Add a user
Blocked-site alerts are raised only for sites people choose to visit that they shouldn't (adult, drugs, violence, gambling, dating and similar) and security risks. Background blocks (encrypted DNS, VPN detection, apps without SNI, ads) are in Reports, not here.
WEES Cloud licence
This controller's own licence (product wees-cloud)
Users
Users and their roles, including customers' own staff, are on the Users tab.
API tokens
For automation (PSA/RMM, scripts). Needs the api_access licence feature.