Standalone access
Work directly in LiftShift Records
Staff use it to find historical reports, follow related records and prepare a PDF.
Try the walkthroughAPI & integrations
When staff need an older report mid-task, they shouldn’t have to leave your application. Connect it to LiftShift Records so they can search the history and open the record from the screen they’re already on.
Discuss a customer workflowThis example is laid out for a wider screen.
Use the person, case or other supported information already in context.
Return the information the screen needs to help staff choose a record.
Give the user a route into the record, with the applicable access checks.
Choose the connection that helps
LiftShift Records works on its own. Add an integration when history belongs inside your customer’s current workflow.
Standalone access
Staff use it to find historical reports, follow related records and prepare a PDF.
Try the walkthroughOptional integration
Use information already in your application to find relevant history and give staff a route to the record.
Agree on the interface, sign-in arrangement and application work for the connection.
Plan the integration
Partners agree on the record types, search fields and record references with LiftShift once. Each new customer archive starts from that model, with its own sources mapped and reviewed.
Where staff start, what they search and which record they need to open.
Information exchanged, supported operations and access arrangements.
Changes in the vendor application, LiftShift Records configuration and customer-specific mapping.
Who implements, validates, hosts and supports each part.
Discuss a customer workflow
Bring a screen, a use case or a customer question. We’ll walk through LiftShift Records and the connection it would need.