Xibernetix Mobile Android App Documentation Android
Actor guide ยท Operator

Operate nearby devices with a verified operator identity.

The Operator workspace is the only mobile role that enters Device Control. It combines role-protected account access with NFC or Bluetooth communication at the physical device.

Operator responsibilities

Operate devices

Choose NFC or Bluetooth and keep the phone near the physical device until the connection or authentication result is complete.

Maintain NFC records

View, edit, activate, deactivate, or delete NFC-tag records available to the signed-in operator.

Protect operator identity

Review operator events, profile details, and passkeys, and sign out before transferring the phone.

Authorization boundary. Device Control and NFC processing perform explicit operator-role checks. A Maker or Administrator token cannot be substituted for an Operator session.

Start or access an Operator session

  1. Choose Operator.From the app's home screen, open the Operator workspace.
  2. Register if invited.Provide the requested operator profile and security details, or use an account created through your organization's process.
  3. Sign in.Use an enabled method such as passkey, Google sign-in, or the deployment's configured sign-in form.
  4. Confirm the dashboard.The signed-in workspace exposes Device Control, NFC tags, security events, passkeys, and the operator profile.

Operate a device

NFC

  1. Open Device Control, then select NFC Tag Scan.
  2. Hold the phone's NFC antenna against the approved device tag.
  3. Keep the tag in range until the result screen opens.
  4. Proceed only when the result says Authentication successful.

An existing tag is verified only when its cryptographic exchange succeeds and its stored operator ID matches this Operator session. A new factory tag is provisioned and bound to the current operator. Read the detailed NFC guide โ†’

Bluetooth

  1. Open Device Control, then select Bluetooth Scan.
  2. Grant any Android permission requested for nearby-device discovery.
  3. Select the intended device from the discovered results and wait for the BLE session.
  4. Verify the displayed device identity before sending supported controls.

Review NFC tags and events

The NFC tags area lists records scoped by the authenticated operator. Use record actions deliberately:

Action Operator intent
View Inspect identity, type, lifecycle state, counter, and linked-device information.
Edit Correct authorized record metadata without changing the physical cryptographic identity.
Activate or deactivate Change whether the backend considers the credential active.
Delete Remove the backend record after confirmation; this does not restore a physical tag's factory master key.

Use Security events to review activity attributed to the operator. Record the event time and outcome when escalating a failed operation.

Operator safety checklist

  • Confirm the correct operator profile before scanning a tag.
  • Provision only approved factory-fresh tags; provisioning changes key slot 0.
  • Do not interpret tag metadata as proof when authentication failed.
  • Do not repeatedly scan during an NFC authentication-delay response.
  • Review passkeys periodically and remove lost-device credentials from both Xibernetix and the credential provider.