Feedback by UserVoice

Obliterator

My feedback

  1. 3,265 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    516 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We see two patterns in this feedback thread and are addressing them now. The first pattern is that users want AutoSave OFF. The second pattern is that the Template scenarios are problematic with AutoSave.

    To address turning AutoSave OFF, we have implemented these capabilities:

    1. To avoid accidental edits by others, the owner of a file can set it to Always Open Read-Only. This can be done by setting the file to open in Read-Only Recommended (File > Info > Protect Document/ Workbook/ Presentation > Always Open in Read-Only) or by Sharing the file without allowing others to edit (File > Share > People with the link can edit > Uncheck the “Allow Editing” box).

    2. Users can turn AutoSave OFF for a file. While a document is open, clicking the AutoSave toggle turns AutoSave OFF for the current document for that user. The next time the same…

    Obliterator supported this idea  · 
  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Obliterator supported this idea  · 
  3. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Obliterator supported this idea  · 
  4. 116 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  M365 (Microsoft 365) Admin Mobile  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Obliterator commented  · 

    Agree with all comments.

    Signature fields need conditional logic.
    E.g. {{IF%%PhoneNumber%%}}Phone: %% PhoneNumber%%{{ELSE}}Call Reception{{ENDIF}}

    Configurable insertion point (below current reply and option to avoid repeat insertion).

    Option to force html format for mail (i.e. convert emails sent in plaintext from iPhone/iPad) when inserting the signature.

    Don't expect to require/pay a third party to provide basic signature functionality. Should be built into the default offering.

    Obliterator supported this idea  · 
  5. 40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Obliterator commented  · 

    Can't believe there isn't any viable signature support in EAC O365!

    Adding the signature in a append disclaimer transport rule isn't sufficient. It doesn't distinguish between email in html format and plain text - so any html signature gets mangled if the email was sent in plain text (e.g. from an iPhone/iPad). Need an option to force the email to html format first before adding the signature in this way (can't see any rule to help with this).

    Control over signature placement would also be desirable (e.g. append below reply, not just append to foot of email).

    The length of the disclaimer text that can be added is also quite limited (when adding html signatures).

    The current signature support is unusable unless every user uses Outlook.

    Obliterator supported this idea  · 
  6. 409 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    45 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Obliterator commented  · 

    Needs to support html signatures (including whe sent from iOS devices - by converting the email to html format if required)

    Obliterator supported this idea  · 

Feedback and Knowledge Base