Frequently Asked Questions
Browse 20 focused answers about product scope, workflows, RBAC, signing, immutable PDFs, audit trails, notifications, security, and deployment.
Type to filter questions across all categories.
No results found.
Try one of these keywords:
Product
Core platform scope and supported handover scenarios.
HandoverTool supports paperless asset handover and employee offboarding workflows with role-based permissions, audit-ready logs, and digitally signed protocol records.
No. The platform is built for both IT and non-IT assets, including equipment, access materials, and other accountable business resources.
Yes. You can review detailed functional areas on the App page and open the live demo to test the workflow.
Workflow
Lifecycle states, protocol composition, and searchability.
Protocols move through Draft, Pending, Active, Return Request, and Inactive states so each step is controlled and auditable.
Yes. A single protocol can include multiple assets with structured fields such as type, brand/model, serial or IMEI, quantity, and notes.
Return Request is a dedicated lifecycle state used when assigned assets need to be formally returned and tracked through closure.
Yes. Search supports protocol number, employee name, and asset identifiers such as serial or IMEI, with filters for fast retrieval.
Roles & Access
Role boundaries and data visibility rules.
HandoverTool uses Admin, Manager, and User roles to separate governance, workflow ownership, and participant actions.
Audit logs are visible only to Admins, aligning oversight privileges with compliance accountability.
No. Users see protocols assigned to them, while Managers can access protocols they created. Full system-wide visibility is reserved for Admins.
Signing & PDFs
Digital signature evidence and immutable document output.
Signing captures timestamp and IP metadata, updates workflow status, and triggers the final protocol output.
A single immutable PDF is generated at signing time and retained as the official evidence record for that protocol.
No. The signed PDF is locked as the final immutable document so downstream review and audit evidence stays consistent.
Notifications
Status communication during handover execution.
Notifications cover pending signatures, successful signing, return requests, and lifecycle closure to Inactive.
Yes. The workflow is designed to keep participants aligned through both email and in-app updates for key protocol events.
Security
Auditability, access control, and protected records.
Audit logs include actor, action, timestamp, IP address, and before-after values for traceable compliance review.
RBAC enforces least-privilege access by limiting each role to the exact records and actions needed for its responsibilities.
Documents are handled through secure object storage patterns with controlled access, including signed URL-based delivery where required.
Deployment
Environment fit and integration expectations.
Yes. The architecture is LDAP-ready and designed for enterprise-oriented identity and policy requirements.
No. Typical deployment patterns are available, but implementation details can be adapted to each organization's security policies and operational constraints.
Need guidance for your handover rollout?
We can map your workflow, access model, and compliance evidence requirements.