Pierre
My feedback
10 results found
-
25 votesPierre
supported this idea
·
-
24 votes
An error occurred while saving the comment Pierre
supported this idea
·
-
19 votes
An error occurred while saving the comment Pierre
commented
This is critical!!! At this point our bigboy password needs to sit at rest in a file on a server just to sync what it does. I have the server locked down but its not right.
My current solution, which I am pretty proud of, is a second free account and the password sits there syncing to it without MFA. Then I share that folder with full rights to my main account. It just works and I see it all under "Shared with me".
Not ideal but hey it works
Pierre
supported this idea
·
-
2 votesPierre
shared this idea
·
-
3 votesPierre
supported this idea
·
-
50 votes
An error occurred while saving the comment Pierre
commented
please please please.
It will stop my "Archive" vault from adding to my drop-down list and me wondering which one to choose.
Pierre
supported this idea
·
-
3 votesPierre
shared this idea
·
-
2 votesPierre
shared this idea
·
-
2 votesPierre
shared this idea
·
-
5 votes
An error occurred while saving the comment Pierre
commented
When importing from 1Password (.1pif or .1PUX files), Proton Pass ignores createdAt and updatedAt timestamps present in the source JSON payload. The importer uses the current date instead, losing valuable historical data.
Current Behavior:
- Imported items receive new created/modified dates based on import timestamp
- Original 1Password metadata (createdAt, updatedAt Unix timestamps) is silently dropped
- No warning or option to preserve these fieldsProposed Solution:
During import, detect and offer to preserve ignored metadata fields:1. Scan payloads for unused fields (e.g., createdAt, updatedAt)
2. Report count of affected entries (e.g., "Found 616 items with createdAt field")
3. Allow users to map each field to a custom field type (Date or Text)
4. Populate the mapped fields across all affected entriesWhy This Matters:
- Audit trail: See when credentials were originally created or last modified
- Migration transparency: Track what changed during transition
- Compliance: Many organizations need historical modification recordsImplementation Effort:
This is a low-effort, high-value change. The data exists in the export — it just needs to be routed to Proton Pass custom fields during import.Workaround Attempted:
Manually editing the Proton Pass JSON export is risky and complex. Better to build this into the import tool.Pierre
supported this idea
·
try this
create a second free account and the password can sit there on your server at rest syncing without MFA. Then you share that folder with full rights to your main account. It just works and you can see it all under "Shared with me". You can even edit/delete.
Not ideal but hey it works. You are limited to 2Gig but until Proton fixes this what can we do?
I have multiple accounts for this, one per machine I want to sync. Unfortunately you cannot use a proton-alias or hide my address alias to create an account.