Cloud Portal overview
Navigate the Trustity Cloud Portal and use its deployment, policy, device, event, user, and audit areas safely.
Cloud Portal overview
The Trustity Cloud Portal at https://trustity.io is the organization-scoped management surface for deployment, policy, endpoint visibility, and security operations. The pages you see depend on your portal role and enabled modules.
For air-gapped environments, the same portal stack can run on your Linux servers as TCP On-Prem.
Scope
Use this guide for an administrator's first portal walkthrough and as a map for common operational tasks. Product labels can evolve; if a page is not visible, check role and entitlement before treating it as a fault.
Prerequisites
- An accepted portal invitation or organization-owner account
- Multi-person ownership of the onboarding plan
- Confirmed module entitlements
- An approved method for handling the organization license key
Core areas
Home and module dashboards
The dashboard summarizes the enabled product areas and recent organization activity. Module pages provide the authoritative operational views for their own events:
- GenGuard for browser and endpoint DLP events, Shadow AI, Warn/Block policy
- FileGuard for file labels, discovery findings, and classified-file blocks in the browser
- VisionX for camera DLP policy and detections
- Vault / PAM for managed devices, local-account rotation, timed local accounts on the station page, and vault workflows
- HostGuard IPS for endpoint failed-logon protection events
Do not use the general dashboard as the only health check. Validate endpoint state in Managed devices and detections in the relevant module page.
Deployment
Deployment is the customer source for:
- The organization license key used for endpoint or extension enrollment
- Current Windows and Linux TAO downloads when an entitled module requires TAO
- Published version, channel, availability, signature status where shown, and SHA-256 values where published
- GenGuard installation and managed-browser materials when GenGuard is entitled
Always obtain deployment assets and tenant-specific values from this page. Never substitute an organization ID or a key copied from another tenant.
Pulse
Pulse, under Overview, answers a short question from records this organization already keeps. The portal page stays in English; the question may be written in any language listed on that page. It covers recent alerts, the audit log, one named policy, a named station, and which stations were not seen today. The answer stays inside the portal. Trustity does not send the question or the answer to an AI provider. The question is written to this organization's audit log. See Pulse and the Privacy Policy.
An assistant outside the portal still uses the Customer API.
Find a page
Press Ctrl+K (or ⌘K on a Mac) from any portal page. Type a page name, a module, or a common synonym in English or Hebrew. Results follow the same modules and role as the sidebar. The search opens a page. It does not search log rows.
Notifications
The bell at the top right lights when support replies on a ticket you opened. VisionX, tamper, and agent-offline items follow the switches under Administration → Alerts. Support replies stay on. Marking the bell as seen is kept in this browser.
Security policies
Policy tabs appear only for entitled modules. Depending on subscription, the portal can expose:
- TAO endpoint hardening
- VisionX camera presence, lock, evidence, and activation behavior
- GenGuard browser rules, categories, destination controls, and TAO endpoint GenGuard (text, files, contexts)
- FileGuard labels, discovery, browser enforcement, and the Windows right-click menu (Agent One 4.0.3579+). This policy is organization-wide. Ransomware protection* is scheduled for the first quarter of 2027
- Vault/PAM rotation, Personal Vault restrictions, and publishing Organization File Vault for employees
- HostGuard IPS thresholds and allowlisting
- ZeroDevice peripheral controls
- Additional entitled controls shown in the tenant
For VisionX, ZeroDevice, GenGuard, FileGuard, and HostGuard IPS, target stations with tags and profiles under the seat caps on your commercial package. TAO Agent hardening, PAM rotation, and Vault file/share limits stay organization-wide. See Tags, profiles, and module seats and Security Policies hub. Device tree can still follow Active Directory for inventory; module overlays use tags. See Follow Active Directory for devices and policy.
Saving a portal policy makes it available to enrolled endpoints. Policy delivery is asynchronous, so verify the endpoint's recent health and applied state before concluding that a change failed.
Managed devices
Managed devices is the main endpoint operations view. Use it to confirm:
- Enrollment completed for the expected hostname
- The device has a recent online status
- Agent, OS, module, and inventory information is present
- Vault/PAM state is available when entitled
- Devices are organized into folders for browsing and bulk selection
- Tags assign stations to module seats and policy profiles
- Device tree is Manual, or Active Directory when you want sync health plus the OU tree; Managed by TAO and Directory reader badges appear on the fleet list
For a new rollout, reconcile this list against the deployment ring rather than assuming every installer execution produced a healthy device.
Event views
Security events are separated by module. Use the page matching the control you tested. A VisionX detection, GenGuard block, and HostGuard action are different signals and are not expected to appear in one universal event list.
Audit Logs
Audit Logs record supported administrative and system actions for the current organization. Search or export CSV when you need review evidence. Security detections remain in their module event views.
User Management
Portal access is invitation-based. Owner/Admin users can manage access; Editor, Viewer, and Vault roles support narrower responsibilities. Sidebar visibility and allowed actions vary by both role and entitlement.
First administrator walkthrough
- Confirm the organization identity and your role.
- Open User Management and ensure there is a backup administrator.
- Review enabled modules and visible policy tabs.
- Review each policy without changing enforcement.
- Open Deployment and confirm the expected assets are available.
- Record the published installer version and checksum, if shown, in the change record.
- After enrolling a pilot device, verify it in Managed devices.
- Perform one approved module test and locate its event.
- Review Audit Logs for the administrative change.
Verification
The portal is ready for pilot use when:
- Required administrators can sign in
- Expected policy and event pages are visible
- Deployment presents the expected assets and a configured organization key
- A pilot endpoint can appear in Managed devices
- Administrators know which page owns each operational signal
Troubleshooting and security
- Page missing: verify entitlement and role; signing out and back in can refresh a newly changed membership.
- No deployment assets: confirm an endpoint or GenGuard module is enabled. Contact the organization administrator if the page reports that assets are unavailable.
- Policy appears unchanged: save once, confirm the device is online, and allow an agent refresh before repeated edits.
- Unexpected device: preserve relevant records, confirm who deployed it, and contact support if enrollment is not authorized.
- Never paste license keys, vaulted credentials, or evidence images into general-purpose tickets or chat.