2127 results found

1. I want to be able to invite not-proton e-mails to meeting

   Currently, when I invite a non proton e-mail to a calendar event, the invitation is crypted and the receiver can't receive the invitation.

   3 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

   0 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

2. Same event in multiple calendars

   I have the problem that I need to share the same event with multiple different groups of people.
   For example, I need to share the dates of my firefighting drills with my office and my partner and sometimes even with my sport club. It would be amazing if it would be possible to elect multiple calenders when creating a new even or edit an existing one. Maybe there could even be some kind of "logical calendar" as shorthand to select a specific predefined set of calenders.

   3 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

   0 comments  ·  New feature  ·  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. Delete mails, not threads

   Maybe I just do not understand the functionality correctly, maybe this is actually really bad design:

   I want to delete specific emails from a thread and keep some others in the folder where they are, but if I delete one, it always moves around the other mails to this folder as well.

   If I for example have two mails in a thread in the inbox, I want to delete one, and later move one into a folder, then it directly moves both into delete when I delete one, and also moves both from the bin If I want to archive one.

   I am definitely clicking on one specific mail, not the entire thread. Bad design maybe? Me misunderstanding?

   Maybe I just do not understand the functionality correctly, maybe this is actually really bad design:

   I want to delete specific emails from a thread and keep some others in the folder where they are, but if I delete one, it always moves around the other mails to this folder as well.

   If I for example have two mails in a thread in the inbox, I want to delete one, and later move one into a folder, then it directly moves both into delete when I delete one, and also moves both from the bin If I want to archive… more

   3 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

   0 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

4. Add 'task completed' checkbox to existing calender entries

   If no separate Tasks are added to Proton Calender, please add a 'completed' checkbox to existing calender items and change the color of the 'completed' item to a little 'of'f the current color.

   3 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

   0 comments  ·  New feature  ·  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. Remove default connexion from old email adress

   Hello,
   When I created my proton email adress, I chose to connect it to my old gmail adress because I was originally thinking to suppress it. In the end I'd rather keep the old one for newsletter and promotional stuff, but I am not allowed to block the numerous messages I get from the gmail adress on my proton one, which is quite annoying.
   Can we find a way to change this feature or should I create a new proton adress?
   Thank you for considering this change or any advice.
   Best,
   Julia

   3 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

   0 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

6. Hide folders and categories feature when not used

   Folders and categories are a great feature, but if they are not in use, I don't want to see the icons below my e-mail folders. I'd like to be able to hide them for a cleaner UI.

   3 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

   0 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

7. make the invitation email for calendar events optional

   The email is currently mandatory.

   There is at least one use case when the email is not desiderable:

   I receive a Google Meet link with date and time by message in a Telegram DM or whatever.

   The meeting is agreed upon and confirmed by both.

   That person already has the event on his Google Calendar.

   I want to set it on my Proton Calendar with the counterparty email as a reference for myself, but I would rather not send a duplicate confirmation email.

   3 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

   1 comment  ·  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

8. Privacy-Preserving Notifications/Generic Notification Mode

   Recently, reports involving Signal highlighted that operating system notification databases may retain sensitive information from message notifications, even after the original messages are deleted. While this example involved Signal and iOS, the same general risk may apply to other apps and operating systems where notification content is stored or indexed outside the app.

   For privacy-focused users, Proton Mail and other Proton products should offer an option to use generic notification text instead of exposing message content in system notifications.

   For example, instead of showing sender names, subject lines, or message previews, the notification could simply say:

   “New Proton Mail message received”

   This would reduce the chance that sensitive email metadata or content could later be recovered from operating system notification logs, backups, search indexes, forensic tools, or other third-party access.

   Suggested feature: Generic Notification Mode

   Proposed options:

   Show full notification preview
   Show sender only
   Show generic notification only
   Disable notifications entirely

   This would be a valuable privacy enhancement for Proton Mail, Proton Calendar, Proton Drive, Proton Pass, and other Proton apps where notifications may reveal sensitive content.

   Recently, reports involving Signal highlighted that operating system notification databases may retain sensitive information from message notifications, even after the original messages are deleted. While this example involved Signal and iOS, the same general risk may apply to other apps and operating systems where notification content is stored or indexed outside the app.

   For privacy-focused users, Proton Mail and other Proton products should offer an option to use generic notification text instead of exposing message content in system notifications.

   For example, instead of showing sender names, subject lines, or message previews, the notification could simply say:

   “New Proton Mail message… more

   3 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

   0 comments  ·  New feature  ·  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. Time-tracking Calendar Integration

   One missing feature from the Proton Suite is a Time-tracking layer integrated in the Calendar app.

   It would be a handy feature to toogle on/off alongside your planned schedule, in order to track the real time invested in your projects, get records and overviews, and be able to learn from them and improve your workflow. All with the same level of privacy and encryption of the other features.

   Right now Proton users still depend on external apps to track their time, which don't integrate in the Proton ecosystem nor offer the same kind of data security. More on the contrary, multiplatform time-tracking sync apps are full of commercial trackers (pun very much intended) alongside security bugs.

   Also, If the Calendar app is indeed planning to allow to run it locally and asynchronized as an option, the Time-tracking layer could work the same way for those who don't want/need online sync between devices.

   I think there's a niche in the market for such (encrypted) feature, and it would be a point of attention for (small) businesses and independent entrepreneurs, while weighting on the idea of the Proton Suite above others.

   One missing feature from the Proton Suite is a Time-tracking layer integrated in the Calendar app.

   It would be a handy feature to toogle on/off alongside your planned schedule, in order to track the real time invested in your projects, get records and overviews, and be able to learn from them and improve your workflow. All with the same level of privacy and encryption of the other features.

   Right now Proton users still depend on external apps to track their time, which don't integrate in the Proton ecosystem nor offer the same kind of data security. More on the contrary,… more

   3 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

   1 comment  ·  New feature  ·  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

10. Remove notification after event ends

    In Google Calendar, on Android at least, event notifications automatically disappear after an event ends. It would be nice if Proton Calendar did the same, to help keep the system notification tray tidier.

    3 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

    1 comment  ·  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

11. (Current) Critical Security Vulnerability: Missing Default-Deny Policy - Why Whitelists Fail Against Zero-Click Exploits (State Trojans)

    (Current Text) April 26, 2026
    Dear Proton Team,

    Currently, Proton Mail under (Filters) "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow"). The "Allow" function serves merely to move important emails back from the Spam folder to the Inbox; it does not prevent the receipt of emails from other domains. The "Block" function serves only to block known, malicious senders.

    The fundamental security problem is that for users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous. An attacker can register thousands of domains or use hacked servers to send malicious emails. A "Block" list can never cover all future, unknown attackers; as soon as a new, malicious domain is created, it is not on the list, and the email is accepted. Furthermore, as long as the Proton server accepts every connection from an unknown domain (even if it is later moved to Spam), there is a critical risk that a Zero-Click Exploit could be executed during the processing phase, such as rendering images, parsing metadata, or analyzing attachments. The malicious code does not even need the user to open it; it can compromise the email client or server infrastructure as soon as the data touches the server. Many users mistakenly believe that an "Allow" list automatically blocks everything else. Technically, this is not the case. The current list is merely a filter ensuring that certain emails do not land in Spam, not a firewall that cuts off access for everyone else.

    I therefore demand the introduction of a separate, explicit setting "Allow Only Permitted Senders" that fulfills the following technical requirements. First, the whitelist must offer flexible granularity by supporting both individual email addresses and entire domains. This allows users to define permitted senders with two distinct levels of granularity to balance maximum security with practical usability. Individual email addresses are essential for high-security scenarios where only a specific person is trusted (e.g., john.doe@company.com); this prevents access even if other accounts within the same domain are compromised. Entire domains, on the other hand, serve for the efficient management of trusted organizations or partners (e.g., @trusted-partner.com) and allow all current and future senders from that domain without manual maintenance. The system must evaluate incoming mail against both lists, with a specific address rule taking precedence over a general domain rule if conflicts arise.

    Second, server-side rejection at the TCP/SMTP level is required. The server must immediately reject the connection before any data transfer if the sender is not explicitly on the whitelist. This requires validation already during the SMTP handshake, ideally immediately after the EHLO/HELO command or at the latest before the MAIL FROM command. If the sender is not allowed, the server must immediately terminate the TCP connection or return an SMTP error code (e.g., 550 Access Denied or 554 Transaction Failed) before the actual email data transfer (DATA command) begins. No data packets containing potential exploits may be received; the server must not buffer or analyze the email content even temporarily if the sender is not on the list. The connection must be severed at the entrance so that no data packet containing a potential exploit is received by the server infrastructure.

    Third, full user control must be guaranteed. Users must be given the opportunity to completely close their digital gate ("Air-Gap" principle for email) without relying on infinite and never-complete blocklists. The responsibility for maintaining the whitelist lies with the user; this is the principle of every high-security system.

    Proton advertises worldwide with "maximum protection" and "end-to-end encryption." Yet, without a "Default-Deny" option that supports both address and domain whitelisting, the door remains physically open to unknown attackers. With this function, Proton would be the only commercial email provider enabling users to protect themselves against state surveillance and zero-day attacks through strict perimeter security. For journalists, whistleblowers, and activists, this is not an optional comfort feature, but a matter of survival. The ability to whitelist entire domains simplifies communication with teams, while the option to whitelist single addresses ensures precision against targeted attacks.

    Please evaluate this request for technical feasibility and prioritize its integration into the roadmap for security updates. Proton should offer this choice to substantiate its position as the world's safest provider.

    Thank you for your work on a safer internet.

    (Current Text) April 26, 2026
    Dear Proton Team,

    Currently, Proton Mail under (Filters) "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow"). The "Allow" function serves merely to move important emails back from the Spam folder to the Inbox; it does not prevent the receipt of emails from other domains. The "Block" function serves only to block known, malicious senders.

    The fundamental security problem is that for users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model… more

    3 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

    0 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

12. Strike agenda items

    When deleting an event in the Proton Calendar, I still want to be reminded that it was there originally. Is it possible to offer two kinds of delete:
    (A) strike through the event (so it is still visible in the calendar, but now the title is in strike through), or
    (B) permanently delete the event?

    3 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

    0 comments  ·  New feature  ·  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

13. Critical Security Vulnerability: Missing Default-Deny Policy – Why Whitelist Fails Against Zero-Click Exploits (State Trojans)

    Dear Proton Team,

    Currently, Proton Mail under "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow").

    • The "Allowed" function serves merely to move important emails back from the Spam folder to the Inbox. It does not prevent the receipt of emails from other domains.

    • The "Blocked" function serves to block known, malicious senders.

    The Fundamental Security Problem: For users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous.

    1. The Impossibility of a Complete Blocklist: An attacker can register thousands of domains or use hacked servers to send malicious emails. A "Blocked" list can never cover all future, unknown attackers. As soon as a new, malicious domain is created, it is not on the list, and the email is accepted.

    2. The Risk of Server-Side Acceptance: As long as the Proton server accepts every connection from an unknown domain (even if it is later moved to Spam), there is a critical risk that a Zero-Click Exploit could be executed during the processing phase (rendering images, parsing metadata, analyzing attachments). The malicious code does not even need the user to open it; it can compromise the email client or server infrastructure as soon as the data touches the server.

    3. Misunderstanding of the Current "Allowed" List: Many users mistakenly believe that an "Allowed" list automatically blocks everything else. This is technically not the case. The current list is only a filter ensuring that certain emails do not land in Spam. It is not a firewall that cuts off access for everyone else.

    The Demand: A True "Strict Allow-Only Mode" (Default-Deny Policy) I demand the introduction of a separate, explicit setting "Allow Only Permitted Senders" that fulfills the following technical requirements:

    • Server-Side Rejection (TCP-Level Blockade): The server must immediately reject every connection from a domain/sender that is not explicitly on the whitelist (e.g., with 550 Access Denied) before the email data is even transmitted.

    • No Data Acceptance: The connection must be severed at the entrance. No data packets containing a potential exploit may be received.

    • Full User Control: Users must be given the opportunity to completely close their digital gate ("Air-Gap" principle for email) without relying on infinite and never-complete blocklists.

    Why Proton Urgently Needs This: Proton advertises worldwide with "maximum protection" and "end-to-end encryption." Yet, without a "Default-Deny" option, the door remains physically open to unknown attackers.

    • Competitive Advantage: With this function, Proton would be the only commercial email provider enabling users to protect themselves against state surveillance and zero-day attacks through strict perimeter security.

    • Existential Necessity: For journalists, whistleblowers, and activists, this is not an optional comfort feature, but a matter of survival.

    Next Steps: Please evaluate this request for technical feasibility and prioritize its integration into the roadmap for security updates. The responsibility for maintaining the whitelist lies with the user this is the principle of every high-security system. Proton should offer this choice to substantiate its position as the world's safest provider.

    Thank you for your work on a safer internet.

    Dear Proton Team,

    Currently, Proton Mail under "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow").

    • The "Allowed" function serves merely to move important emails back from the Spam folder to the Inbox. It does not prevent the receipt of emails from other domains.

    • The "Blocked" function serves to block known, malicious senders.

    The Fundamental Security Problem: For users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous.

    1. The Impossibility of a… more

    3 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

    0 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

14. “Read Receipt” as DEFAULT for Mac app users? Thanks.

    It would be very helpful, IMHO, to have a default setting option to request read receipts for outgoing messages. Thank you!

    3 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

    0 comments  ·  New feature  ·  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

15. For Huawei devices

    Hi, I like the app and it would be nice if it is also available natively for Huawei devices in its app store, appgallery, for a better experience

    3 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

    0 comments  ·  New feature  ·  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

16. Show time zone names (or custom labels) in the calendar view, not just GMT offsets

    When two time zones are enabled, both columns are only labeled with their GMT offset. Example: Europe/Vienna and Africa/Johannesburg both display as "GMT+2" during European summer time — completely indistinguishable. In winter the offset differs by one hour, but "GMT+1 / GMT+2" still doesn't tell you which column belongs to which zone.

    Please show one of the following next to (or instead of) the offset:

    The IANA city name (e.g. Vienna, Johannesburg), or
    A user-defined label per zone, or
    The standard abbreviation (CET/CEST, SAST).

    3 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

    0 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

17. Booking Page - Sync availebility from my calendar

    I do photography on my free time, therefore my booking page might have availibility from 4pm to 10pm on weekdays and 10am to 6pm on weekends. I would like to have the option to sync my standard calendar into the availibility on the booking page.

    That way any meetings with friends etc. I have set in my calendar will automatically block the time in the booking calendar. In addition i want the option to then also block a selcted time before and after to make sure I can make both appointments.

    3 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

    1 comment  ·  New feature  ·  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

18. PST and MBOX files

    Add the ability to import PST and MBOX files via the import/export tool and not just via the Webui Easy Switch

    3 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

    0 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

19. Set message expiry in the mobile

    Allow users to set messages to expire directly on the mobile app. It is currently only supported through the web interface.

    3 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

    0 comments  ·  New feature  ·  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

20. SimpleLogin Alias Export CSV Should Include Display Names

    The "Display Name" field for aliases should be backed up into the CSV file that gets produced when going to Alias import/export -> Export Aliases under Settings.

    At present, notes entered under "Alias Description" are included, but Display Names are absent.

    The Display Name field allows for custom per-alias user entered names that should certainly be preserved in backups, and restored in the event that the CSV file gets used "for a future batch import" -- which is one of its explicitly stated purposes.

    At present, my manual workaround is to ensure that custom Display Names are also copied and pasted into the Description fields for their respective aliases, so that they at least get backed up in some fashion.

    The "Display Name" field for aliases should be backed up into the CSV file that gets produced when going to Alias import/export -> Export Aliases under Settings.

    At present, notes entered under "Alias Description" are included, but Display Names are absent.

    The Display Name field allows for custom per-alias user entered names that should certainly be preserved in backups, and restored in the event that the CSV file gets used "for a future batch import" -- which is one of its explicitly stated purposes.

    At present, my manual workaround is to ensure that custom Display Names are also copied and… more

    3 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

    0 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