The behavior is controled by the option replicate deletion as un-label / archive: If you enable the option replicate deletion as un-label / archive, the replication of deletion of emails will work as follows: if user A deletes an email (puts it in the trash or permanently deletes it) then user B will have that […]
Articles Tagged: requirements
Save Emails to Google Drive: limitations and requirements
Save Emails to Google Drive allows you save and archive emails to any Google Drive folder. However, there are some limitations and requirements. Limitations Your labels and sub-labels cannot have /, +, \, special characters, or emojis in their names. For example, instead of Emails/Clients, use Emails – Clients. Your labels cannot be named INBOX. For example, instead […]
Gmail Label and Email Sharing: limitations and requirements
Gmail Label and Email Sharing allows you to share labels (and emails) as you would share folders in Google Drive (or Dropbox). However, there are some limitations and requirements. Limitations Your labels or sub-labels must not have “/“, “+“, “\“, special characters, or emojis in their name. For example, if your label name is “Inbox/Clients” […]
Save Emails: Limitations and requirements
Limitations Your labels or sub-labels must not have “/“, “+“, “\“, special characters, or emojies in its name. For example, if your label name is “Inbox/Clients” please rename that label to “Inbox – Clients”. \ back slash in the label name / forward slash in the label name * asterisk in the label name double […]