Mobile

Stay close to urgent client work.

Explore the iOS and Android app implementation for alerts, ticket triage, approvals and vault access. Check release availability, offline behavior and access controls before relying on it on call.

Book a walkthrough Explore Digital Vault & Password Manager

Implemented client · check distribution ↗

Conceptual phone, laptop, and managed endpoint connected through an approval checkpoint and evidence record.

Every access has a boundary

Useful access. Explicit control.

Review alerts, tickets, devices, approvals, and permitted Vault context from a trusted mobile session.

Illustrative workflow · explore the steps · no action is executed

Enroll a trusted device

Confirm this step for your release, permissions and environment.

Keep urgent work moving without turning a phone into an unrestricted console.

Keep action identity, tenant scope, MFA, device trust, and audit connected to the desktop workflow.

Inside the workflow

The work this connects.

Operational overview: See device, ticket, alert, approval, and account signals sized for quick mobile triage.
Device workflows: Review device detail and launch supported reboot, wake, terminal, or related actions according to policy.
Tickets and alerts: Filter queues, reply or comment, acknowledge alerts, and retain customer and SLA context.
Approvals: Review action intent and evidence before approving or rejecting a request from a separate authorized account.
Native Digital Vault access: Use permitted encrypted Digital Vault items with biometric unlock and policy-controlled offline cache.
Push notifications: Route supported operational events without placing sensitive payload content in the notification body.

Mobile workflow evaluation

Evaluate mobile triage before planning a rollout.

Review the intended alert, ticket, approval, trusted-device, and evidence path for bounded work away from the desktop.

This action reviews implementation scope and its release boundaries. It does not offer a public mobile release or claim current device availability.

Review the mobile workflow

Try one useful scenario

Credential custody and revocation

Fictional example: revoke a user while their client is offline, then attempt access before and after reconnecting. Test the approved offline expiry and confirm which cached items remain accessible.

Illustrative evaluation scenario, not a recorded product result.

What a useful result must show

Record who can decrypt each credential class, recovery authority, local expiry, domain-match result and the observed revocation boundary. Inspect what leaves the client for breach checks.

Get the evaluation worksheet →

Check the support boundaries

End-user encrypted vault items
Automation credentials authorized for execution
Recovery and offline access
Browser domain matching, biometric fallback and push privacy

The mobile app and browser extension are planned surfaces; signed distribution and a tested release are not evidenced here. A zero-knowledge claim for user vault items must not be generalized to automation credentials an executor is authorized to decrypt.

Check public evidence and availability →

Scope, availability and evaluation details

Mobile is a focused triage and approval surface, not a claim of complete desktop feature parity.

Offline data, remote actions, secret access, and revoked-device behavior follow tenant and trusted-device policy.

The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →

Review full environment and integration scope

iOS and Android on the same API contracts

The mobile app implementation uses Dayrook sessions and strict mobile contracts for alerts, tickets, devices, Digital Vault, backup, MDM, billing, support, push, and approvals.

Device-native protection

Biometric secure storage protects permitted cached state, while APNs and FCM delivery uses a bounded push outbox and excludes sensitive operational content from notification bodies.

Mobile reuses the first-party identity, tenant, approval, ticket, device, billing, notification, and Vault owners.

Questions, answered

Before you choose your next step.

Is the Mobile app available for iOS and Android?

iOS and Android are the target platforms. Signed release tracks, push delivery, store availability, and deployed-device QA must be confirmed during evaluation.

Can technicians use the Digital Vault on mobile?

Target design: Authorized Digital Vault records can be unlocked through the trusted-device and biometric policy, including controlled encrypted offline access.

Can the app replace the full web console?

It is designed for triage and bounded field workflows. Deep configuration and broad administrative work remain better suited to the web workspace.

What happens when a phone is revoked?

Active authorization is ended and cached material follows the trusted-device revocation and offline-access policy.

Your next step

Confirm the mobile workflow and release first.

Identify the urgent work an on-call technician needs to handle. Check the available app, supported actions, offline behavior and access controls before relying on it.