The asset submission block allows users to submit files to Frontify even when they don't have a Frontify user account. This way, users without editor rights, external partners, and providers can easily submit their files.

You can find the asset submission block in the Frontify Marketplace. You can follow this procedure to install the block in your instance.

You can activate the block on your Libraries settings as shown below.

Now, simply go into your guidelines and add your block.

Open the setting of the recently added block and set your library. The files submitted via the asset submission block will end up in this library.

You can do various customizations, either directly on the block (inline customizations) or in the block settings panel on the right-end side of the screen.

Once you set up all the fields and finish the configuration, the block is ready to use by anyone who can access that particular guideline.

You will find the file in the library you previously linked.

When you upload an asset through the asset submission block, it will automatically appear in a dedicated backend library folder (this loom shows an example).

For instance, if you're uploading a visual from your brand guidelines, the system places it directly into an automatically created designated folder called the "Asset Submission Inbox" within the selected library. Inside this folder, you’ll find subfolders organized by the date the asset was transferred. From there, you can relocate the asset to a more appropriate folder to better suit your library structure.

If you need to copy the block from one brand and move it to the guidelines of another brand, you need to restart the configuration process, starting from activating the block in your library. For this reason, we recommend creating a new block from scratch if you want to use the asset submission block in the guidelines of other brands.

If editors would like to collect submitter information (name and email address) using a custom metadata field, they can enable automapping so that logged-in end users do not need to re-enter their name & email. Here is a video explaining this functionality.

The following are the extensions supported by the asset submission block:

"aac" "ac3" "ai" "aif" "aifc" "aiff" "artboard" "asc" "atom" "au" "avi" "bcpio" "bin" "bmp" "cdf" "cgm" "class" "cpio" "cpt" "csh" "css" "dcr" "dif" "dir" "djv" "djvu" "dll" "dmg" "dms" "dng" "doc" "docx" "dotx" "docm" "dotm" "dtd" "dv" "dvi" "dxr" "eps" "etx" "exe" "ez" "flac" "flv" "gif" "gram" "grxml" "gtar" "hdf" "heif" "hqx" "htm" "html" "ice" "ico" "ics" "idml" "ief" "ifb" "iges" "igs" "indd" "indt" "jnlp" "jp2" "jpe" "jpeg" "jpg" "js" "kar" "latex" "lha" "lzh" "m3u" "m4a" "m4b" "m4p" "m4r" "m4u" "m4v" "mac" "man" "mathml" "me" "mesh" "mid" "midi" "mif" "mkv" "mov" "movie" "mp2" "mp3" "mp4" "mpe" "mpeg" "mpg" "mpga" "ms" "msh" "mts" "mxu" "nc" "oda" "ogg" "pbm" "pct" "pdb" "pdf" "pgm" "pgn" "pic" "pict" "png" "pnm" "pnt" "pntg" "ppm" "ppt" "pptx" "potx" "ppsx" "ppam" "pptm" "potm" "ppsm" "ps" "psd" "qt" "qti" "qtif" "ra" "ram" "ras" "rdf" "rgb" "rm" "roff" "rtf" "rtx" "sgm" "sgml" "sh" "shar" "silo" "sit" "skd" "sketch" "skm" "skp" "skt" "smi" "smil" "snd" "so" "spl" "src" "sv4cpio" "sv4crc" "svg" "swf" "t" "tar" "tcl" "tex" "texi" "texinfo" "tif" "tiff" "tr" "tsv" "txt" "ustar" "vcd" "vrml" "vxml" "wav" "wbmp" "wbmxl" "webm" "webp" "wml" "wmlc" "wmls" "wmlsc" "wmv" "wrl" "xbm" "xht" "xhtml" "xls" "xml" "xpm" "xsl" "xlsx" "xltx" "xlsm" "xltm" "xlam" "xlsb" "xslt" "xul" "xwd" "xyz" "zip" "tpl" "zip", "mxf"

We hope you find this help article useful. If you have additional questions, please contact customer support.