π Permissions
β
Who can create email pipelines? The system administrators.
βWho can use these pipelines? Generally anyone who knows the email address, subject to options linked to publication rights.
β
To facilitate contributions via email, Elium suggests a generic email address available to all users. This allows users to transfer emails or create new ones, including attachments, to save them on the platform.
β
In addition to this generic address, other email addresses can be created following specific publication rights and made available to users.
β
It is also possible to generate email addresses aimed at:
β
saving the email and attachments that reach the platform (similar to the standard email address, but with personalized choices regarding publication rules)
βsaving only the email
βsaving only the attachments (files)
βtransforming the email into an article (the subject of the email becomes the title, the body of the email becomes a text block, and any attachments are listed in a 'gallery of files' block)
βtransforming every web link content into the full body of the email
β
Every email address is differentiated by an extension defined by the administrator: your-platform.elium.com+extension@in.elium.com
β
These unique email addresses have distinct publication rules:
β
the publication space
βthe tag(s) attributed to the generated content
βthe contributor
βas draft or published
βwith or without verification of the publication rights of the sender
βwith or without confirmation of receipt by email
β
Creating Contributions via Email Address
To create these addresses, navigate to the administration interface and select the 'Email pipelines' tab.
β
Create a new address.
βDefine the extension to be used (we recommend making it sufficiently explicit).
βDescribe the behavior of this pipeline for quick reference in the interface.
βDefine the contributor: you can either let the system attribute the content based on the sender's email address or force attribution to a specific user.
βSpecify whether the system should verify if the user has the right to publish content in the selected space.
βIndicate whether the system should generate a confirmation of receipt.
βDefine how the system should handle sent content.
βChoose the publication space.
βSpecify any tags to be applied.
βTick the option if you want to publish the received content immediately.
β
Restraints and Limitations of Email Pipelines
Every email address operates uniquely, potentially leading to numerous addresses.
βTo save it as an article, emails with overly complex layouts may not be replicated optimally.
β
π Pro Tip
β
We recommend always properly numbering the files you send by email (by default, their name is used as the title in Elium).
βEnable confirmation of receipt whenever possible to ensure that the content sent has been received.
β