Scenario 1: An external partner only needs to monitor data
Recommended role: Viewer If the person only needs miner status, hashrate, alerts, and results, and does not need to change configuration or run tasks, Viewer is the right choice. Best setup- Assign only the farms they need to review
- Do not grant miner operations or configuration changes
- Keep the experience read-only
Scenario 2: An operator needs to handle miner issues
Recommended role: Member If the person needs to reboot miners, run tasks, switch power modes, or perform other daily operations but does not manage the team, use Member. Best setup- Assign only the farms they are responsible for
- Confirm the role is Member, not Viewer
- Do not give access to member management or workspace settings
Scenario 3: A third-party developer needs API or debugging access
Recommended role: Member If the person needs to inspect farms, miners, and tasks inside a limited scope or help debug issues, Member usually fits, but the scope should stay narrow. Best setup- Grant only the farms needed for the integration or investigation
- Let an Admin create and manage API Key access when it is required
- Do not grant invitation, role, or workspace settings permissions
Scenario 4: A lead needs to manage the team and shared resources
Recommended role: Admin If the person is responsible for member changes, role updates, farm scope assignments, and workspace settings, Admin is the correct role. Best setup- Let them invite and remove members
- Let them adjust access boundaries for other users
- Let them manage workspace settings and API Key access