1529 results found

1. Domain Hosting

   Firstly, a great product folks! Keep up the good work.

   How would you feel about hosting domains so we can have our company emails encrypted? It would save set up fees and obviously we'd just point our mail records at your servers.....

   372 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   32 comments  ·  New features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Proton Forums (Discourse)

   It would be nice to connect with the community.

   30 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   11 comments  ·  New features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. HIPAA compliance certification

   Many doctors would like a way to communicate securely with their patients. Doctors don't know how to evaluate products such as ProtonMail - they rely on certifications from 3rd-party agencies that the product meets HIPAA requirements.

   158 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  10 comments  ·  New features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Proton API

   Would love to see an API to give businesses the tools they need to run their own secure mail service.

   308 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   36 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Owncloud Integration

   Owncloud Integration

   37 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   9 comments  ·  New features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add feature request button in Proton Mail

   In the sidebar, next to the Report a Problem button, add a Request a Feature button that links to this website. I was using report a problem before for feature requests because I didn’t realize this website existed.
   Also please get rid of the bot comments spamming links in the comments of these feature requests

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Temporal Context Enhancements for Lumo

   Dear Proton Support Team,

   I would like to propose a set of related enhancements concerning temporal information in Lumo, together with a suggested deployment model aligned with your existing subscription structure.

   Current Situation
   Lumo currently receives the calendar date in its system prompt (e.g., "Today's date: 07 Oct 2026"), but does not have access to:
   1. The day of the week
   2. The ISO week number
   3. The local time of day
   4. Any record of when previous messages in a conversation were sent

   The weekday and week number are mathematically derivable from the date, but this derivation must be repeated on every message — unnecessary overhead for facts that never change within a day. The time of day cannot be inferred from the date at all without indirect methods (such as invoking a tool purely to extract a timestamp from its response), which is inefficient and unreliable. And since past system prompts are not retained in the conversation context, Lumo cannot perceive any elapsed time between messages, no matter how precisely the present is known.

   Proposed Enhancements

   1. Weekday and ISO Week Number (all users)
      Append both to the existing date injection.
      • Token cost: minimal, roughly a dozen characters per message.
      • Benefit: eliminates redundant per-turn computation and guarantees consistent calendar awareness.

   2. Current Time Injection (Lumo Plus)
      Additionally inject the user's local time of day into each prompt, as an opt-in setting.
      • Cost: requires a client-side time handshake or similar per-session mechanism, comparable to existing infrastructure-backed Plus features such as web search.
      • Benefit: enables time-aware behavior such as tone adjustment to the hour, and rules that trigger at specific times.

   3. Per-Message Timestamps (Lumo Plus, probably)
      Append the send time to each message, persisted in the conversation transcript.
      • Cost: unlike the fixed-size injections above, the accumulated token overhead of per-message timestamps grows with conversation length — effectively consuming a small surcharge on every historical turn in every subsequent prompt. For long-running conversations this is a recurring and increasing cost, which suggests the Plus tier.
      • Benefit: this is the only mechanism that provides elapsed-time reasoning. Knowing the current time alone does not tell Lumo when a previous message was sent; a timestamped transcript does.

   Use Cases

   Personal use case — alternating shift schedules: I work alternating early and late shifts based on ISO week parity. In odd-numbered weeks (early shift), I should be asleep by 20:00; in even-numbered weeks (late shift), I arrive home at 21:30; weekends are unconstrained. A functional reminder rule ("after [20:00 or 02:00, depending on shift] on a work night, tell me to go to bed") requires the weekday, the week number, and the current time — all three layers together. Today, only the date is provided, and the derivation of calendar facts is reasoning-intensive and unreliable enough that such a rule cannot be trusted.

   Commitment tracking: time-relative statements ("I'll check back in five minutes") only become meaningful if the assistant can compare a previously stated time against the present. Without per-message timestamps, this class of verification is structurally impossible — the assistant knows only "now," with no record of "when."

   Conversation integrity: with automated summarization of long conversations, timestamps serve as structural markers. Elapsed-time gaps carry real meaning (a thirty-second reply versus an overnight pause), and preserving that information makes compacted summaries substantially more faithful.

   Implementation Notes
   Timestamps can be captured client-side at send time and attached to the message payload, requiring no server-side clock synchronization. All four proposals operate entirely within the existing privacy model: no data sharing, no training usage, and timestamps originate from the user's own device. Users implementing parity-based rules (as in my schedule) could additionally anchor their rotation to a reference week in persistent memory, keeping such rules debuggable when the underlying roster changes.

   Closing
   These proposals would give Lumo a coherent sense of time that currently requires awkward workarounds to approximate. I believe the split between near-free calendar facts and infrastructure-dependent time data fits your existing tier structure well.

   Thank you for considering this suggestion.

   P.s.: Yes, Lumo wrote this on my behalf. I did proofread all and edited some of it, though.

   Dear Proton Support Team,

   I would like to propose a set of related enhancements concerning temporal information in Lumo, together with a suggested deployment model aligned with your existing subscription structure.

   Current Situation
   Lumo currently receives the calendar date in its system prompt (e.g., "Today's date: 07 Oct 2026"), but does not have access to:
   1. The day of the week
   2. The ISO week number
   3. The local time of day
   4. Any record of when previous messages in a conversation were sent

   The weekday and week number are mathematically derivable from the date, but this derivation must be… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Common issues people face during GSuite to Office 365 Migration?

   I am looking to perform a GSuite to Office 365 Migration and went through the manual processes first. There are several ways of migrating data from G Suite to Microsoft 365, but I stumbled on some issues while trying.

   For a manual and/or simple migration, one can export data from Gmail via takeout or Google’smigration options and import the required data to Microsoft 365. Similarly, one can also export and import calendar and contact information if the data to be migrated is small. This is ideal for few users with less data.

   What are the common pitfalls?

   Failure to verify the source and destination accounts (users) before migration

   Missing attachments and old emails

   Poor user/mailbox mapping

   Duplicates created upon multiple user migrations

   Failure to migrate calendars, contacts, and emails

   Too many users to migrate manually.

   Other complications can include authentication errors, permission issues, failed mailbox migrations caused by large data, or migration job failure due to huge data.

   I stumbled on the Kernel GSuite to Office 365 Migration tool while searching for alternatives. The tool offers bulk migration and selective/incremental migration options to deal with large-scale data migration. Unlike the manual process, it does not require migrating each user’s data.

   For a user that has performed a Google Workspace to Office 365 Migration before, what approach worked? Were they able to adopt the free/manual option, or was it necessary to invest in a migration tool due to the volume of data or users?
   https://www.nucleustechnologies.com/g-suite-to-office-365/

   I am looking to perform a GSuite to Office 365 Migration and went through the manual processes first. There are several ways of migrating data from G Suite to Microsoft 365, but I stumbled on some issues while trying.

   For a manual and/or simple migration, one can export data from Gmail via takeout or Google’smigration options and import the required data to Microsoft 365. Similarly, one can also export and import calendar and contact information if the data to be migrated is small. This is ideal for few users with less data.

   What are the common pitfalls?

   Failure to verify… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Configurable session expiraion timeout

   In https://account.proton.me/u/1/mail/security#sessions I'd like to change the expiration timeout from 60 days to something like 2 days.

   I open proton daily on only one single device, so this should be fine. The long timeout of 60 days seems unnecessarily relaxed for me, could be a bit more secure.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating