Roles and Permissions
Roles
Owner
The account owner. Created automatically upon registration. Has full access to all platform features, including user management, site configuration, and account deletion.
Administrator
The platform administrator. Has access to all operational features: creating and configuring sites, agents, scan tasks, and performing any device operations. Cannot delete the account or manage other users' roles.
Operations Manager
The operations manager. The primary working role for employees managing the device fleet. Can perform all device operations, configure Scan Tasks, and view all site data.
Technician
A technical specialist. Works directly with devices on-site. Can perform maintenance operations: reboot, diagnostics, board and cooling management, Locate. Does not have access to site and agent settings.
Viewer
An observer. Read-only access. Can see all metrics, the dashboard, and the device list, but cannot perform any operations or change settings.
Permissions Matrix
| Action | Owner | Administrator | Operations Manager | Technician | Viewer |
|---|---|---|---|---|---|
| View dashboard and metrics | ✅ | ✅ | ✅ | ✅ | ✅ |
| View device list | ✅ | ✅ | ✅ | ✅ | ✅ |
| View device details | ✅ | ✅ | ✅ | ✅ | ✅ |
| Device Event Log | ✅ | ✅ | ✅ | ✅ | ✅ |
| Reboot / Restart / Pause | ✅ | ✅ | ✅ | ✅ | ❌ |
| Locate device | ✅ | ✅ | ✅ | ✅ | ❌ |
| Pool switching | ✅ | ✅ | ✅ | ✅ | ❌ |
| Firmware installation | ✅ | ✅ | ✅ | ✅ | ❌ |
| Diagnostic report | ✅ | ✅ | ✅ | ✅ | ❌ |
| Board management (Boards config) | ✅ | ✅ | ✅ | ✅ | ❌ |
| Cooling management (Thermal config) | ✅ | ✅ | ✅ | ✅ | ❌ |
| IP Reporter | ✅ | ✅ | ✅ | ❌ | ❌ |
| Overclock preset switching | ✅ | ✅ | ✅ | ❌ | ❌ |
| Create and configure Scan Tasks | ✅ | ✅ | ✅ | ❌ | ❌ |
| Create and configure agents | ✅ | ✅ | ✅ | ❌ | ❌ |
| Create and configure sites | ✅ | ✅ | ❌ | ❌ | ❌ |
| User management | ✅ | ❌ | ❌ | ❌ | ❌ |
| Account deletion | ✅ | ❌ | ❌ | ❌ | ❌ |
Notes
- A role is assigned when a user is invited and can be changed by an administrator in the account settings
- The Viewer role is convenient for granting access to mining hotel clients — they can see their equipment metrics but cannot make changes
- The Technician role is specifically restricted from infrastructure settings — they only work with devices at the maintenance level
Sites → Agents → Scan Tasks → Workers Hierarchy
HashCore Pulse is organized around a four-level hierarchy. Understanding this structure helps you properly configure the platform and efficiently manage equipment at any scale.
Device Statuses
HashCore Pulse uses a two-level status system for each device. The first level reflects device connectivity, the second — what's happening inside the miner. Together they give a complete picture of the fleet's state without needing to access each device individually.