Connect CyberQP to bring managed accounts into Lexful as password records under the right organization. Your team can find the account details in Lexful and retrieve the current password when they need it. CyberQP remains responsible for storing and rotating the password.
Before you begin
Use a Lexful account with permission to manage integrations and data sync.
Have access to a CyberQP tenant and a technician with the Primary or Super role to generate API credentials. CyberQP recommends a dedicated System User for integrations.
Know which region hosts your CyberQP tenant.
API credentials inherit the access of the CyberQP technician who creates them. Keep the tokens private and use your organization’s approved password manager to store them.
1. Get your CyberQP API credentials
Follow CyberQP’s API setup guide to authorize access and obtain your Client ID, Access Token, and Refresh Token.
Use the API address for your tenant’s region:
United States:
https://us.getquickpass.comEurope:
https://eu.getquickpass.comCanada:
https://ca.cyberqp.com
Use the API base address, not your dashboard address or the /api/docs documentation page. CyberQP’s guide explains the sign-in and consent process. Save the credentials when they are displayed; revisiting the credential-generation page creates a new set.
2. Connect CyberQP in Lexful
Open Platform → Integrations → Data sources.
Find CyberQP and click Connect.
Enter your regional API URL. The form already displays
https://, so enter the hostname, such asus.getquickpass.com.Enter the Client ID, Access Token, and Refresh Token from CyberQP.
Click Test Connection. Resolve any error before continuing.
Once the test succeeds, click Connect CyberQP.
Example setup only. Enter your own CyberQP credentials; the sample values shown are not valid.
Lexful begins collecting source data automatically after connecting. This first collection makes CyberQP customers and account details available for the mapping and data-sync steps.
3. Review organizations and sync password records
Before syncing records into your documentation, review how CyberQP customers correspond to your Lexful organizations. Correct organization matching keeps each customer’s passwords with the right customer.
Wait for the initial CyberQP collection to complete and review the connection’s status in Data sources.
Review customer-to-organization matches and resolve missing or incorrect mappings.
Open Data sync, review your sync configuration, and run the sync.
Check the sync result, then open Passwords in the relevant organization to review the records.
The integration brings in admin, service, and end-user accounts. Just-in-time (JIT) accounts are not included.
What happens to existing password records?
Lexful can match a CyberQP account to an existing password record using an exact normalized account identifier within the same organization. Similar display names alone do not create a match. If there is no suitable match, Lexful creates a new password record.
When an existing record matches, CyberQP becomes the source of its password. The previously stored password is replaced by the CyberQP-managed connection. Review organization mappings and existing usernames before your first sync.
Use a CyberQP-managed password
Open the password record in Lexful as usual. The password field has a lock indicator identifying it as managed in CyberQP, and the externally managed secret is read-only.
Retrieve the current password: use the record’s password controls. Lexful fetches the secret from CyberQP on demand rather than storing a copy as the record’s password.
Reveal: the eye button follows your asset type’s password-reveal setting. Copying remains available when reveal is turned off, subject to your permissions.
Change or rotate the password: make the change in CyberQP. Lexful does not write or rotate passwords back to CyberQP.
Account details arrive through sync; password retrieval happens when you request the secret. You do not need to wait for a metadata sync to retrieve a password that CyberQP has rotated.
Troubleshooting
The connection test fails
Check that the API URL matches your tenant’s region and that all three credential values came from the same credential-generation session. Copy the complete values without extra spaces. Confirm that the CyberQP technician has the required API access.
The connection stops working
Lexful handles token refresh for the connection. If authorization has been revoked or the refresh token is no longer valid, obtain fresh credentials through CyberQP and update the connection in Lexful. Re-test it before retrying the sync.
A password record is missing
Check both stages: the CyberQP source collection and the Lexful data sync. Confirm that the customer maps to the intended organization and that you are viewing that organization. JIT accounts are not imported.
The record is visible, but its password cannot be retrieved
Confirm that you have permission to access the password and that the CyberQP connection is healthy. Retrieval depends on CyberQP being available and the account still being accessible there. Retry after a temporary service error; if it continues, contact Lexful support with the affected record and error message, without including passwords or tokens.
I cannot edit the password field
This is expected for a CyberQP-managed password. Update the password in CyberQP, then retrieve it from the Lexful record when needed.