Team Access
Roles, team seats, invitations, and the handoff from Staff to Manager.
Organization access is introduced client by client. Staff becomes available after HumanByte has completed the release checks for your organization. If an action or role is unavailable, contact your Manager or HumanByte support.
Roles
| Role | Everyday responsibilities |
|---|---|
| Admin — HumanByte support | Verified HumanByte support assigned to your organization. Manages organization settings, eligible roles, service QR badges and technical Sentinel settings. |
| Manager | Manages the team within the rules below, operating hours, people whitelist, blocklist changes and business report recipients. Reviews Sentinel cases and makes final theft decisions. |
| FAE | Technical installation and support: device configuration, diagnostics, enrollment, secrets, updates and rollback. Access logs retain original customer UUIDs and log IDs for CRM troubleshooting; customer contacts, customer exports, Sentinel and blocklist are unavailable. |
| Staff | Checks devices and access logs, views customer information and blocklist, adds Sentinel notes and triages cases. Cannot change device configuration, block entries or final theft decisions. Available only after activation for your organization. |
All four roles can check device status and request a restart. Restarts share a five-minute waiting period per location, including requests from other team members. Wait for the displayed time before trying again. Technical setup and dashboard updates require FAE or HumanByte Admin access.
Authorized log viewers can filter by exact customer ID within the selected organization's locations. The original UUID links evidence across Bytekey and ByteGate; it does not grant access to a customer profile or another organization.
Creating an organization gives its creator the Manager role. Ask FAE or HumanByte support to help enroll the first device.
Seats and Managers
Each organization has five seats shared by Manager, Staff and FAE. Active assignments and unexpired pending invitations reserve seats. Partner FAE uses a seat too. Mobile customers, locations and service QR credentials do not use team seats.
Only verified HumanByte Admin assignments are exempt. An old Admin label alone does not establish that exemption; HumanByte reconciles these assignments before rollout.
At most two Manager slots may be occupied, including pending Manager invitations. At least one active Manager must remain. You cannot remove or change the final Manager while waiting for a new Manager to accept an invitation.
The Team screen shows current usage. If legacy usage exceeds the limit, existing assignments are retained while the team is reconciled; increasing usage is blocked. Revoking an unused invitation or letting it expire releases its reservation.
Invite or approve a colleague
- Open Settings → Team in the intended organization and check seat availability.
- Enter your colleague's email and choose an available role. Review its responsibilities before sending.
- Ask the colleague to open the email invitation and sign in with the invited email. The invitation is valid for seven days.
- Refresh the Team screen to confirm the accepted assignment and updated usage.
Manager can invite or approve Manager and Staff. Admin can assign eligible roles. A join request alone reserves no seat; approval must fit both seat and Manager limits. An existing member's role is not changed by approving a duplicate request.
Manager can remove Staff and revoke their own pending Manager/Staff invitations. Manager cannot change existing roles, remove another Manager/FAE/Admin, or revoke someone else's invitations. Ask HumanByte Admin to make permitted role changes.
If delivery is pending or failed, use the available retry action. Retrying uses the same invitation and seat reservation. A created invitation does not guarantee an email reached the inbox. If retry is unavailable or the invitation expired, an authorized team manager can revoke the old invitation and send a new one. Contact support if delivery keeps failing.
If a colleague changes the team at the same time, refresh the screen and review the latest counts before retrying a rejected action. The server checks the final state for every change.
Sentinel handoff
Staff can label an unreviewed or false-alarm case as False alarm or Suspected theft, and add notes. A suspected case passes to Manager for a decision. Staff cannot revise that suspicion or change a confirmed-theft decision; Manager or HumanByte Admin confirms theft or resolves the case as a false alarm.
A triaged case is not always a resolved decision. Suspected cases remain in the Manager queue even when all cases for the day have been triaged or the day's checklist is complete. Customer contact information remains available to Staff under the current policy. Tracking contacted/paid/no-reply case progress is a separate future workflow.
Manager manages business report recipients and schedules. HumanByte Admin manages provider credentials, bot setup, Sentinel analysis settings, batch retries and service QR badges. Contact your Manager for customer decisions and FAE/HumanByte support for device diagnostics.
Last updated on