Amandeep Kumar

@NodePlease provide your email ID to me in DM, and we will manually disable it for you in the future.

Our development team has already accepted this feature request and has working on it. Adding a new feature may take some time, but rest assured, we'll keep you updated on the progress.

Our technical team has acknowledged the issue and is actively working on a solution. Fixing this bug may take some time, and the resolution will be included in the upcoming updates of the application. We appreciate your patience and understanding

We appreciate your effort in bringing this concern to our attention. I am raising this issue with our technical team as a feature request, and we may consider adding it in our future updates. However, please understand that several factors and considerations have to be taken into account. SI-3566

@jhcook Please provide your email ID to me in DM, and I will add you to TestFlight.

You can enable logs in Enpass by going to Settings > Advanced and checking the box for Enable logs.

I second @AnakinCaesar. If you have forgotten your Master Password, there is no way to restore Face ID access. Face ID is a convenience feature, but the Master Password remains the primary method of authentication. If you don’t remember it, you’ll need to reset your vault and set up Enpass again.

We appreciate you reaching out and sharing your experience. We are aware of this issue, as it has been reported by other users as well. Our team is actively investigating the root cause. Since the issue is not consistently reproducible in a specific scenario, resolving it is taking longer than expected. We understand how frustrating this can be and appreciate your patience while we work on a fix. If you notice any patterns or specific triggers, please let us know, as it could help in our investigation.

Currently, exporting passkeys is not available in Enpass. However, this feature is already on our roadmap, but it will take some time to be implemented. As a recommendation, you can add both vaults to the same device and manually copy items from one vault to another. This ensures that all data, including passkeys, is properly transferred. #SI-3658

Thank you for reaching out, and we’re sorry to hear about the issue with automatic backups. To better understand and assist you, could you please clarify a few details? Is the issue occurring on a specific device (Windows, macOS, Linux, etc.)? Are you using Enpass Personal or Enpass Business? Where are the backups being stored (local drive, network share, cloud storage, etc.)? Are there any permissions or access restrictions unique to AMG Steel Factory's system? Do you receive any specific error messages when the backup fails? Is the backup process partially working (e.g., creating incomplete files), or does it not trigger at all? Aside from resetting the admin password, were there any other system changes (e.g., new security policies, software updates)? Has the backup directory or file path changed? Feel free to share these details with us at support@enpass.io, and we’ll escalate the matter to our product team if necessary. We’re here to help and will work to resolve the issue promptly.

@Bragoon, Thank you for the clarification! Currently, in Enpass, each template can only be assigned to a single category at a time. Unfortunately, there is no direct way to assign the same template to multiple categories simultaneously. As a workaround, you can: Duplicate the Template: Create a copy of your desired template and assign it to the second category. This allows you to have the same structure available across multiple categories. Use Tags for Better Organization: Instead of relying solely on categories, you can apply custom tags to your items. This way, the same template structure can be organized and found under different contexts. We understand the convenience of having templates across multiple categories, and I’ll pass your feedback to our development team for future consideration.

@Kliwer,Thank you for sharing your feedback—we understand how frustrating frequent auto-locks can be, especially in specific use cases like using Enpass via RDP on a tablet without a keyboard. While Enpass currently does not offer a "Never" option for security reasons, here are a few workarounds that may improve your experience: Extend the Lock Time: Increase the "Enpass is idle for" and "System inactive for" duration to the maximum allowed time. You can find this option under: Settings > Security > Auto-Lock. Disable 'Lock When Enpass is Closed': Ensure this option is disabled to prevent locking when the window is minimized or hidden. If you continue to face issues with the Enpass window disappearing when using the on-screen keyboard, feel free to provide us with your device details and Enpass version—we’ll be happy to investigate further.

we’re glad to hear you’re enjoying Enpass Premium! It sounds like the change in networks and the time gap may have caused a desynchronization between your devices. Let’s try to get your Wi-Fi sync working again while ensuring no data is lost. 1. Identify the Most Up-to-Date Vault Open Enpass on each device (Linux PC, laptop, iPhone, and iPad). Check which device has the most current information by reviewing your most recent entries. 2. Backup All Vaults Before proceeding, create a manual backup of each device’s vault: Go to Settings > Vaults > [Vault Name] > Backup and save the file securely. 3. Reset Wi-Fi Sync On your Linux PC (or a device that will act as the host): Ensure all devices are on the same local Wi-Fi network. Go to Settings > Vaults > [Vault Name] > Set Up Sync > Wi-Fi Sync and choose Host a Server. On other devices (iPhone, iPad, laptop): Disconnect any existing sync: Settings > Vaults > [Vault Name] > Disconnect. Reconnect to the newly hosted Wi-Fi sync server. If the sync still fails or if you encounter conflicts, please let us know—we’ll guide you through advanced troubleshooting. We’re here to help if you need further assistance!

@mandebooks I have just messaged you. Please do check your direct messages (DM) and share required details there.

We're sorry to hear you're encountering sync issues with Nextcloud WebDAV. The error codes you mentioned (1308413 and 1304401) typically indicate connection interruptions or authentication challenges during the sync process. To help resolve the issue, please try the following steps: Clear Sync Cache: Disconnect the sync from Enpass. Log in to your Nextcloud account and manually delete the Enpass folder if it exists. Reconnect the sync from scratch and monitor the behavior. Ensure there are no VPNs, proxies, or network restrictions affecting the WebDAV connection. If the issue persists, please contact us at support@enpass.io with a demo account for your Nextcloud WebDAV server. This will allow us to raise the concern with our product team for further investigation.

I had a discussion with our technical team, and unfortunately, Enpass does not currently have this feature. We appreciate your effort in bringing this concern to our attention. I am raising this issue with our technical team as a feature request, and we may consider adding it in our future updates. However, please understand that several factors and considerations have to be taken into account. #SI-4281

Windows Hello should work on both instances. If it is not working on your machine, please provide more details, including: Enpass version on both accounts Windows OS version Kindly email us at support@enpass.io so we can investigate further.

Please share the URL where Enpass autofill is not working so we can investigate further. Kindly note that Enpass autofill is currently not working with desktop applications.

To resolve this issue, we need to check your purchase history. Please drop us an email at support@enpass.io with your registered email address. Looking forward to your email!

For security reasons, we haven’t provided an option to view the password on the Enpass login screen. However, we understand your concern and will pass this request to our product team for further review. #SI-1905

Thanks for reporting this issue and for being part of the beta channel! We've addressed this in the stable release, so updating to the latest version should prevent this from happening again. If you’re still experiencing the issue after updating, please let us know—we’d be happy to investigate further.

Our team is actively working on a workaround to ensure you can authenticate your application even with Zscaler installed. We appreciate your patience and will update you as soon as we have more information. #SI-3465

Here’s a quick rundown addressing your points: macOS Sequoia Compatibility: Enpass 6.11.8 is fully compatible with macOS Sequoia as an application. However, for autofill functionality in browsers, Enpass relies on our secure browser extension. Since Apple's built-in Password Manager is integrated into macOS and Safari, it might appear as the default option. On macOS, the Safari extension is bundled with the Enpass desktop app and is added to Safari automatically, but it isn’t enabled by default. To enable the Enpass extension on Safari, please follow these steps: Go to Safari Preferences > Extensions > Enpass. Click the checkbox next to Enpass Extension in the sidebar. Click the Turn On button in the pop-up that appears. Once the extension is installed, connect it to the Enpass desktop app to allow access to your saved accounts, passwords, and passkeys. Click on Always Allow On Every Website. Browser Extension and Security: We understand the security concerns regarding browser extensions. Our Enpass extension is built with stringent security measures and only accesses fields necessary for autofill after your explicit permission. If you're not comfortable using the extension, you can continue using Enpass as a secure vault and manually copy credentials when needed. Using Two Password Managers: While it might seem like you're managing two systems, Apple's Password Manager and Enpass serve different purposes. For a seamless autofill experience with Enpass, we recommend activating the browser extension. This way, you can enjoy the robust features of Enpass while keeping your credentials secure. I hope this helps clarify things. If you have any further questions or need more details about our extension’s security protocols, please let me know.

Thank you for sharing the details info information. This will surely be helpful for our backend team in further investigation. Please allow us some time to get back to you with more findings or solutions. We appreciate your time & patience as we work on solving this issue!

It seems there might be a conflict between Enpass's entry update process and LinkedIn's passkey creation workflow. To address this, please try the following steps: Manually Save the Passkey: Instead of letting Enpass update the existing entry automatically, disable autofill temporarily in the browser and manually create or update the LinkedIn entry in Enpass with the passkey details. Check for Field Mapping: Verify that all required fields (e.g., email, password, and OTP) in the LinkedIn item within Enpass are correctly mapped and saved in the correct format. Clear Browser Cache and Cookies: Sometimes, browser cache and cookies can interfere with website workflows. Clear them and try the process again. Update Enpass Extension: Ensure the Enpass extension in Firefox is up-to-date. If the issue persists, please share any error details or screenshots (if possible) so we can investigate further.