Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Project-level settings
Company-wide settings applying to all projects
Dedicated interface for viewing, managing, and updating financial information, transactions, and payment methods for subscribing services
This tab contains information about the plan and add-ons for the currently selected project.
This tab contains invoicing and payment information for the company.
The invoices page provides a comprehensive summary of both paid and pending invoices, offering the ability to download them for record-keeping and reference.
Filerobot is an AI-powered Digital Asset Management (DAM) platform with integrated image and video optimizers that stores, organizes, and accelerates media galleries online.
Filerobot can be implement either as or as a combination of:
Collaborative DAM for marketing, content and creative teams to upload, manage and transform marketing assets in one central source-of-truth
Headless DAM for organizing, optimizing and delivering millions of media assets via API and integrating into your tech stack easily
Media Asset Widget for providing a fast and modern upload experience and delivering media galleries on any web application
Filerobot is architected to scale and manage thousands to hundreds of millions of assets per customer tenant.
Filerobot is a modular platform build around 5 main components:
Filerobot File System: A scalable cloud-based file system to store and organize files across the globe
Web applications such as the #the-asset-hub, the #filerobot-media-asset-widget-fmaw, the #sharebox and #airbox to offer multiple entry and media distribution points for content administrators, contributors and consumers
ASK Filerobot: AI-powered automations to enrich and moderate assets and generate variants
Media optimizers to transform and optimize images, videos and any static content on-the-fly and accelerate over CDN
A multi-CDN delivery infrastructure to accelerate asset loading times worldwide
Through a variety of APIs, plugins and connectors, Filerobot is designed to be integrated in an ecosystem of 3rd party applications such as PIM, CMS, ERP, booking platforms, and more.
Filerobot relies on a multi-tenant, scalable and flexible file system serving as foundation to an intuitive for enabling DAM workflows and integrations within your Content Operations.
AI-powered uploads automatically tag assets for better classification, data enrichment and search while content moderation algorithms automate User-Generated Content (UGC) flows.
Filerobot is designed to be the central Hub for all brand and product images, videos as well as static assets in your organization. The Filerobot Media Asset Widget provides interfaces to your internal and external stakeholders to upload, categorize, collaborate and deliver fast and beautiful media assets via multiple channels to global audiences.
The Filerobot Media Asset Widget is a versatile file uploader and media gallery seamlessly integrated into an easy-to-use modal or inline widget. As a window to the Filerobot DAM, it empowers users to enjoy accelerated uploads through Filerobot's robust content ingestion network and reverse CDN as well customizable galleries.
The FMAW offers advanced capabilities such as inline image editing, search, filtering, bulk management of tags and metadata.
It is an ideal solution for building interactive media upload and management experiences in your web or mobile applications.
The Sharebox is Filerobot's external sharing feature that allows to securely share multiple assets directly from the DAM with external parties. Select the files for sharing and create a password-protected Sharebox with optional password protection and expiration date. All active Shareboxes are accessible within the shared tab in the Asset Hub, allowing you to manage them in one place.
The Airbox grants external users to upload assets directly into specific folders in the DAM using public links. Password-protection and expiration date are optionally available.
Scaleflex Visual AI is the hub running all Filerobot's ML and AI capabiltiies. Upon asset upload, ASK Filerobot intelligently extracts information from your media assets with AI and grants you the flexibility to initiate various tasks.
These post-processing capabilities can be done in 2 ways:
Asynchronous processes allow you to avoid waiting for the process to complete during the upload
Synchronous processes empower you to validate assets based on pre-defined criteria
This versatile feature streamlines your asset management process to suit specific business needs.
Filerobot integrates 3 advanced image, video, and static file optimizers, empowering you to transform your media assets on-the-fly or through a background process after uploading.
Image optimization: Filerobot will save you hours in image processing tasks by manipulating and transforming your images, optimized for web delivery.
Video optimization: Filerobot's adaptive streaming and video transcoding features ensure your videos load fast anywhere and on any device. Filerobot can transcode your videos in multiple target resolutions and generate the playlist (manifest) for your DASH or HLS video players.
Static content: With the Filerobot CDN, Filerobot efficiently accelerates the delivery of all types of static content, including PDFs, CSS and JS minification.
Filerobot collaborates with numerous Content delivery Network (CDN) providers that boast an extensive global network of thousands of Points-of-Presence (PoP). This strategic partnership allows Filerobot to efficiently cache media assets as close as possible to the viewers, resulting in significantly faster loading times of assets regardless of the channel, device and user location.
The Filerobot token is a key concept to understand when working with Filerobot. It identifies your tenant, aka project.
Whether you need to enhance sharing and collaboration around media assets within siloed teams to increase productivity or manage millions of product images, videos and data sheets, Filerobot's multi-tenancy will enable you to address all use cases from a single pane of glass.
Single or multi-brand scenarios?
Single or multi-site setup?
Interactions between multiple internal and external teams as part of your Content
Operations?
Filerobot's scalable multi-tenancy will prevent asset duplication, save time in categorizing and retrieving assets and overall structure your media asset library to set your organization for success when it comes to building engaging and fast digital experiences.
Each tenant is called a Project identified by a Token ({token}) in the DAM. A project hierarchy can be created with users and teams given various access permissions to a single or multiple projects.
Each new Filerobot account comes with a first token or project. Each project combines a storage container to store assets and a CDN distribution to deliver optimized assets over CDN all around the world.
Some system settings are project-specific while others are company specific.
As a simple rule, all Organisation settings are linked to the company, while all other settings such as Project or Development or are project-specific.
Users can be created at company level and thus access all company projects or at project-level to restrict their access to only specific projects. See Users for more details.
Teams help organising users into groups and set team-based permissions on folders and assets
Authorized users can create teams with the button. Following fields are needed to create a team:
To manage team members, users can either:
Click on an existing team to show the team composition on the collapsible right side panel
Access the Manage members option from the actions menu ...
Both options provides:
A list of existing team members with an option to remove them from the team (trash icon)
A link to add new members with their name / email either -- addition can be done one by one or in bulk
A search to quickly find an existing team member (first name, last name or email)
This page contains company-wide settings applying to all projects
This page section contains the key personal information about the user:
In this section, the user can specify the security settings company-wide
Configure SSO for users to log in with their corporate credentials (such as Active Directory, Okta or Azure AD / Entra ID) into Filerobot.
An Identity Provider supporting SAMLv2 is required.
To configure SAMLv2-based SSO, click on the Add SSO connection button. Any Identity Provider supporting the SAMLv2 protocol is supported.
After saving the SSO connection, every user attempting to log in with an email address from the domain configured in Step 3 will be redirected to the configured Identity Provider and automatically logged into the Asset Hub if an active SAMLv2 session is enabled.
This section manages all users with Filerobot Asset Hub access
The Invite users modal is used to invite users where single or bulk invitation emails can be sent. Users can be created at the company level for access to all corporate projects or at the project level for access to a single or multiple projects.
The Asset Hub supports various user access levels, a.k.a. user level.
In addition to the standard levels mentioned above, administrators have the possibility to create up to 5 custom levels and define for each which pages and menu will be available
Custom project levels are available for company-wide and project users (they don't have access to company-related informations)
Users can only invite lower-level users, with the exception of project-level Managers, who can also invite Manager.
Email address
User level (see above)
Access scope:
Entire company
Project(s): select projects user should have access to
Once validated, an email invitation is sent to the user's email address.
A user can only manage lower-level users, e.g. a Viewer cannot manage a Manager.
The following attributes are available for editing:
User level
Active or inactive status
Access scope
It is also possible to create custom user attributes fields on top of the existing system fields (email, name..)
Configure the Asset Hub's menus
| Setting | Description |
|---|
Enable Products to activate the Product reference and Product position system metadata for each asset and categorize assets per product SKU and position in a carousel as well as the Products asset view page to view assets per Product reference.
Allow you to configure the order of pages in the main menu for all users of this project.
General settings for metadata variants and upload constraints
Owner, Administrators and Managers can manage the metadata structure
- general settings for metadata variants and upload constraints
- detailed specification of the metadata fields per asset type
This tab contains general settings for metadata variants and upload constraints
Enabling this option will prevent users from uploading assets without specifying the required metadata.
The asset upload option does not apply to API uploads
Metadata variants enable alternative displays for the same asset attributes, e.g. language, currency, location, etc.
System variants (language, regional group...) are required for the system to run
Custom variants can be created by users by clicking on the Add variant button:
A variant can contain multiple options: each option is composed of an API key and a label
Please note the special case for Language system variants
The top most option will be the default language for metadata and tags
All language options are to be selected from a drop-down list of supported languages (Languages that supported by AI are indicated with an AI tag)
The language API keys are the ISO code of the language selected and can't be modified
This section allows the user to specify which metadata fields should be used for special system attributes and functionality, such as licence expiry.
To add a mapping, click on the Add mapping button:
Choose the system attribute to map a metadata field to, select a compliant metadata field from the drop-down and press Save.
Currently, only license expiry is available
If there are no suitable metadata fields, you can click on the Create new metadata field button, which will trigger the Add a metadata modal (restricting the options to the applicable ones) to create a suitable field.
This tab enables the configuration of all asset metadata fields for the organisation. It consists of 1 pre-defined group of fields (System fields) and an option for the users to create additional metadata groups and fields.
The user can:
Users can search either by field name or field API key.
The search is dynamic, activating after the user enters at least 2 characters.
The search also filters both system and custom fields.
Every asset must have the following metadata fields:
Title
Description
Both are of type Text and with applicable regional variant Language.
Set whether it’s Required or not
Update the Placeholder text
Update the Info tooltip text
Adding a new group
When the user clicks the + Add group button, a new custom group is immediately added to the bottom of the custom groups list and the screen is auto-scrolled to it.
The user can:
Rename the group
Delete the group
Add a field to the group
Managing an existing group
Edit a field
Delete a field
The user can:
Save any changes by clicking the Save button
Cancel the operation and any changes by clicking the X button
The user has the following options:
Visibility - ON / OFF toggle button whether to show the field in the public API response header.
Name - free text to enter the field’s name
API key - the key to store/retrieve the variation from the back-end
Info tooltip - free text providing helpful information about what’s expected as value for the added metadata field
Placeholder text stating: ”Helpful information to display on hover”
You can set the Regional variant of a metadata field on creation only - you cannot modify it later.
If the selected Type is single- or multi-select, then the Metadata variant is disabled (since those options are lists of predefined items)
Required - ON/OFF toggle whether this field needs to be populated for every asset in the organisation. If a custom-defined metadata field is configured to be "Required", it means that Filerobot will not save assets where this field has no value and will prompt the user to fill it in, in order to Save.
Add button - to create the field
Cancel button - to cancel the operation without saving anything
When the user chooses Select-one or Multi-select type for the metadata field, they have to provide one or more answer options with the following details per each:
state the option's API key
specify the option’s value
It is a good practice to not include special characters in the API key, to keep it simple and corresponding to its value.
Editing a group field
The following fields are not editable:
Type
Metadata variant
Upload management rules, default visibility & download
When enabled, the system will return success once the entire file has been transferred from the user's browser to the uploader infrastructure. The file might not be immediately for download as it has to complete the upload to the storage infrastructure.
Set a rule for naming the assets once uploaded. Possible options are:
Assign a random file name in UUID format
Keep original file name with random suffix
Keep original file name
When enabled, Filerobot will resize the images during the upload process to optimize storage and accelerate further actions such as image editing or variant creation
When enabled, share an Asset Gallery Explorer over a public link to external users.
Set the default CDN visibility for the root folder.
Public will publish all assets over CDN link
Private will make the assets only visible in the Asset Hub and Widget implementations. Folders can inherit or override the Root folder’s default CDN visibility.
Set a default gallery role for all users in the project.
Provide the agreement text users should agree to in order to download an asset.
Custom routing rules allow you to rewrite URLs in order to match file paths and names in Filerobot thereby shortening public asset URLs.
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Parameter | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
The user levels Owner and Administrator are only available for company-wide users as they have access to company-related information such as or
| User level | Available menu |
|---|
The user level determines which Asset Hub menu items are visible to a user. The user level does not govern the folders and assets a user can view or the permissions assigned to them. These accesses are controlled via the gallery role assigned via the modal.
Custom company levels are only available for company-wide users as they can have access to company-related information such as or
Individually or in bulk, new users can be added via the button. Following fields are needed to invite an user:
| Field | Description |
|---|
| System attribute | Metadata field requirements |
|---|
Thereafter, all assets with that field filled will be searchable and most importantly can be alerted on that (expiry) date. See on how to configure them.
The System fields appear in the Embedded metadata category. They cannot be deleted - as indicated by a padlock icon All other fields are custom-defined metadata and the users can create, edit or delete them.
a field by Name or Key
(reorder) custom groups (only)
- add and delete new groups, as well as add, reorder, edit and delete their fields.
Users cannot modify system fields, apart from:
Click on the button to:
Once fields are added, the user can do the following operations on them by clicking on theellipsis button:
When the user clicks the Organize button, the screen is refreshed, showing only the custom group names in rows, under an Organize groups section title:
Reorder the groups by clicking and dragging on the reorder icon
Type - drop-down field with the following options: Integer | Select-one | Multi-select | Text-area | Text | Date | Boolean. Please find details for them .
NB. If the user chooses Select-one or Multi-select as type, then they must populate the relevant below
Metadata variant - drop-down field to select any of the available
Editing a custom metadata field is similar to , with the following exceptions:
| Name | Type | Description | Examples (used for) |
|---|
| Setting | Description |
|---|
| Setting | Description |
|---|
When enabled, Asset Hub users will be required to accept the custom before being able to download an asset.
Applied when is enabled
Plan overview
Describes the current plan being subscribed to
Purchased Add-ons
This is a list of all subscribed and activated Add-ons for the current plan
Available Add-ons
This is the list of additional add-ons that can be enabled
Billing address
Specify (or update) a billing address and contact email for invoicing
Invoice email
Add contacts who should receive copies of the invoices
Payment method
List of available payment methods for making payments on your invoices. You can only choose one option.
Payment method: Card
Once "CARD" is selected, you will be required to enter your card details, which will be used to make payments.
Payment method: Bank (manual)
Once "Bank (manual)" is selected, a bank transfer will be setup and used to make payments.
Payment method: Direct debit
Once "Direct debit" is selected, you will be required to enter your IBAN, which will be used to make payments.
Logo (optional)
HEIC, JPEG, PNG, or WebP, max size 5MB
Name (required)
Name of the team
Description (optional)
Free text
Company name
The company name displayed in the upper left corner of the Asset Hub, unless a project logo has been uploaded under Branding
Default language
When a Default language is selected, it will be used for all users.
Please note that it can be changed individually in My Account by each user.
Multi-factor authentication
Enable or disable MFA for all company or company project users. The MFA Code will be sent via email. Please note that MFA is bypassed if SSO is enabled.
Single sign-on (SSO)
Configure SAMLv2-based SSO to enable users to access the Asset Hub using SSO via an Identity Provider (IdP).
Prompt new users to accept the company's Ts & Cs on first login
Enable or disable the requirement for users to accept the customizable T&Cs upon first login
Ts & Cs content
The custom text or HTML to display to users on their first login. Supports multiple languages.
Force all users to accept the new Ts & Cs
Modifying the content of Ts & Cs will create a new version. Enabling this setting will force users having already accepted the previous version of the Ts & Cs to accept the updated version upon next login.
Theme
Select between Dark, Light and Custom theme.
Color
Add your own color-hex code to override the Asset Hub's default colour.
Default number format
Set the styling for the thousands and decimal separators in numbers that you want to enforce.
Login page layout
Select the layout of the login page
Background cover type
Select the background of the login page: color or an image
Cover
Select a background image if you have selected the image option
Color
Set a background color if you have selected the color option
Enable / Disable toggle | Enables the optional Home landing page where users will land when logging into the Asset Hub. The Home page is a widget-based customizable page that promote specific assets, folders, collections, tags, ... and also displays usage statistic such as "Most downloaded asset". |
| The name of the variant |
| the key to store/retrieve the variation from the back-end |
| the name for the particular variation |
license expiry |
|
Short text | TEXT | Free text shown on 1 line. Does not accept line breaks. | Title |
Long text | TEXTAREA | Similar to TEXT but you can place inside longer text and paragraphs. | Description |
Boolean | BOOLEAN | True/False indicator. Note: In the Filerobot UI it is visualised as a check-box. | "Approved" or "Published" |
Date | DATE | Calendar date format. | Created at |
Number (integer) | INTEGER | Positive and rond number. Note: takes only digits. | Order number |
List (single value) | SELECT | List with pre-defined options, where only one can be selected. Note: should not be used for more than 100 options to chose from. | Country of origin |
List (multiple values) | MULTI-SELECT | List with predefined options, where multiple values can be selected. Note: should not be used for more than 100 options to chose from. | Markets |
Supertags | TAGS | Unlimited list of attributes added into a dynamic list that can be searched and augmented on the fly by users. | Customers |
URI-type attachment | URI | Link to an external (WWW) asset or resource Officially supported URI schemes are: - url (http://xx, https://xx, www.xx) - phone (tel:+xx) -email (mailto:xx) Other URI schemes will also function but are not documented | Privacy policy |
Asset-type attachment | ATTACHMENT | Attach an internal hub asset Can add up to 5 attachments per metadata -- all hub assets types (video, image, pdf..) are supported | Asset |
| Set a rule for dealing with a duplicate asset: • Accept • Refuse |
| Set a rule for dealing with a duplicate asset name: • Refuse • Override • New version |
| Resize |
| In Pixels |
| In pixels |
| ON/OFF toggle |
The CDN invalidation page allows users to invalidate images from the CDN and Filerobot resizing servers.
The CDN invalidation is accessible from Settings > Development > CDN invalidation
Invalidation allows to flush the CDN cache to refresh the assets with their latest version without changing the URL. By default, Filerobot invalidates older version when a new version is created in the Asset Hub. Hence manual invalidation is mostly needed for externally hosted assets.
This option on the Add invalidation form enables the user to request the invalidation of all assets or a subset of assets by asset path using the 'original' option.
Past invalidation details
Past invalidation requests can be viewed along with their status and details (follow the links to view the inventory of invalidated assets).
The full API documentation is availabe under developers.scaleflex.com.
Owner (company only) | All Hub pages & System Settings |
Administrator (company only) |
Accountant |
Manager |
|
Developper | All Hub pages System settings:
|
Contributor | No System Settings Hub:
|
Viewer | No System Settings Hub:
|
Project logo
Upload a project (or company) logo to be displayed on the top-left corner of the Asset Hub.
Favicon
Upload a custom favicon to replace the default Filerobot favicon.
Process settings cover many of the key functions in your Filerobot account
Add one or multiple custom domains to deliver DAM assets over your subdomains, for example medias.acme.com. Once the custom domain added, you will need to create 2 DNS CNAME entries to validate the TLS certificate and point your subdomain to Filerobot.
Example:
DNS1: _076f48ef8df3a3ca368b89c6f0bb0bcf.medias.acme.com. CNAME _29163927834ee4c4e03c365fd7282c74.nhqijqisfx.acm-validations.cdnprovider
DNS2: medias.acme.com CNAME token.cdnprovider.com
If you want to change your domain, please contact support
Aliases can be used to shorten your Filerobot URLs and hide parts of the asset folder path. We recommend prefixing and suffixing the aliases with underscore '_' to avoid loops.
User create custom transformations using presets to shorten the Filerobot URLs.
Rules allow to apply default transformations on assets based on the asset’s filename.
Allow Filerobot to deliver externally hosted assets
In case customers want to use their Filerobot token to deliver externally hosted assets (= Cloudimage only functionality) and want to limit the list of domains hosting assets that origin assets can be downloaded from, a domain white list can be created.
WebP is a format optimized for web and mobile delivery. Filerobot can compress your images automatically into WebP to reduce bandwidth and improve loading times.
This section governs the video compression settings of the project. Video compression involves the transcoding of an original high resolution video file (HD, UHD, 4K, …) into smaller resolution for better web delivery (720p, 480p, …).
This section governs the video conversion from one format to another.
This section governs the video transcoding for adaptive streaming settings.
These settings govern the delivery of static content (JS/CSS/PDF, …).
Manage API keys for headless applications
API keys allow to call the Filerobot file management API and are suited for backend or headless application where no user context is needed and where the key is not exposed to the browser
Authentication against the Filerobot API is done with an API Secret Key available under Settings > Developers > API keys.
New API keys can be created with the button. On click, user will be requested to
Enter the API key description so it can be easily identified
Select the permissions to be attached with the API key (multi selection from the permissions list) -- these defines what the user will be able to do with the assets
| API Permission | Description |
|---|---|
Existing API keys can be managed individually or in bulk for status (Active <> Deactivate). The following settings can be edited:
Specify who and when should be alerted about important events, such as asset expiration, being tagged in comments, and others
The metadata field used for the notification (eg. "licence expiry") needs to be configured (mapped) first.
It can be done in Settings > Project > Metadata > (tab) Configuration > (section) Field mappings:
You can read more about them in #field-mappings.
When the option is enabled, user can set notification on asset expiry by completing the following information:
Unless otherwise specified, notifications are typically sent at 6am UTC
Post processing, Webhooks & integrations
Automations allow applying automated actions (background removal, AI-tagging, detecting brand logos, etc.) to uploaded assets during or after the upload process, or sending the uploaded asset's metadata to an external API endpoint.
The Automation settings are accessible from Settings > Development > Automations
Post-processing includes the application of various verifications and enrichments to an asset on upload - e.g. detect if it's not safe for work, count faces in an image, remove image background and many others.
To add a post process, you can click on the "+ Add post process" button and select a post process from the list (See link to list below)
Remember that post-processes marked with a * require ASK Filerobot credits.
Please note that when marked "Unavailable", a post-process will not run and needs a preliminary activation. That happens with a request to our Support Team, and in the meantime, triggering will be prevented regardless of the configuration of the post-process.
Provided it is then available to your token, and your account has enough ASK credits to run it (when needed), the post-process will be applied to all uploads if the "Run on every upload" is set to "Enabled".
Refer to Upload post-processes for a list of available post processes.
Once a post process is selected, user is requested to set the following parameters:
| Parameter | Description |
|---|---|
Web-hooks allow to call a 3rd party web service upon specific triggers and send all asset data in the JSON body.
Defines when the Webhook will be triggered
Defines which data is sent to the webhook
Security templates are used to generate API access keys (temporary keys with configurable permissions & restrictions)
The Security Templates are accessible from Settings > Development > Security templates
Security Templates can be created with the Add Template button by entering the following informations
Used to identify the security template
Used to defines what users can / can't do with the assets. Permissions are selected from the list:
| API Permission | Description |
|---|---|
These settings set limits on the Upload API.
It restricts API calls based on IP address ranges and/or countries.
This setting allows to set validity period of key, for example to match the user's session length in your authenticated application
Directories where the key is allowed to list elements. If you want to allow all subdirectories of /folder, set the value to /folder/*
Existing API keys can be managed individually or in bulk for status (Active <> Deactivate):
All Hub pages & System Settings Limitation on : Administrators can only manage users with lower levels than Administrator
Only
All Hub pages & System Settings except and settings Limitations on :
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Parameter | Description |
|---|---|
| Setting | Description |
|---|---|
If no metadata field is mapped, no notification will be triggered, regardless of the configuration setup.
| Parameter | Description |
|---|---|
| Webhook parameter | Description |
|---|---|
| Assets trigger | Metadata trigger |
|---|---|
| File | Video | Image |
|---|---|---|
| Setting | Description | Default |
|---|---|---|
| Setting | Description | Default |
|---|---|---|
| Setting | Description | Default |
|---|---|---|
| Setting | Description | Default |
|---|---|---|
| User level | Description |
|---|---|
Domain name
Domain name without https://
Alias
_alias_
Redirect to
url to redirect to
Note
Preset
Preset name (ex: full-view-sm...)
Redirect to
Operations & filters (ex:h=900&w=1200&func=bound&org_if_sml=1)
Description
Note (ex:Gallery Full View on Mobiles)
Rule match
Rule (ex: .png)
Parameters
Operations & filters
Description
Note
Domain name
Domain name without https://
Compress all PNGs to WebP automatically
On/Off
Compress animated GIFs to WebP automatically
On/Off
Compress all other image formats to WebP automatically
On/Off
Enable AVIF compression
On/Off
Compress by default
On/Off
Default compression factor
Integer
Progressive JPEG
On/Off -- Progressive JPEG enables the loading of a low quality preview while the full image is loaded. Enabling this feature will slightly increase the file sizes of your JPEGs.
Enable PNG lossy compression
On/Off
Default PNG quality
Integer
Rasterize SVG
On/Off -- When active, all SVG files are converted to a raster image.
Enable SVG lossy compression
On/Off -- Reduce the number of curve nodes and remove invisible elements to decrease filesize.
Keep origin image ICC profile
On/Off -- Always remove ICC profiles and convert images to sRGB. Might decrease processing performance.
Convert ICC profile to sRGB if too large
On/Off -- Remove ICC profiles and convert to sRGB only for large images.
Convert ICC profile if larger than
Integer
Video resolutions
Configures the target video resolutions
Target bitrate
defines the target bitrate (only accept integer)
Target folder
Defines where compressed video will be stored: • Internal hidden folder • Same folder as original video
Target format
Configures video conversion target: • WebM • MP4
Video resolution
In addition to convert the video file into WebM or MP4, the video API can also compress (see above) the video into a target resolution
Target folder
Where the converted video will be stored: • Internal hidden folder •Same folder as original video
Protocol
• HLS • DASH
Enable static content acceleration
ON/OFF -- Accelerate any static files over CDN. Enabling this feature requires images to have image file extensions (.jpg, .png, .webp, .gif, ...)
Max-age
value in seconds
S-maxage
value in seconds
Automatic origin image refresh
On/Off
Image origin refresh period
value in seconds
Description
To identify the API keys
Secret key
To be kept secret
Created at
The API key creation date
Active
The API key status that can be toggled from active to deactivated using the ... options
-- If used, deactivated API keys will return an error
Copy
Copy the secret key in the notepad for easy integration
Notification name
Free text
Notification type
Drop down to select the type of notification: Asset expiry ...
Notification channel
• Email • App • Email and App
Recipients
Specify who will receive the notifications: • Asset owner • Users who downloaded the asset
Notifications schedule
Specify when the notifications should be sent: • On the day of expiration •
Mode
Sets if the post processing is SYNC (synchronous, -during the upload- preventing the asset to actually be stored while it's analysed) or ASYNC (asynchronous, meaning that the analysis job will be queued, allowing for the asset to immediately be available in the library)
Run on every upload
When enabled, post process will apply to every upload (allows you to prepare, test parameters, and temporarily put on hold the post-process while not losing the configuration)
Trigger rules
Defines conditions under which the post processing will be triggered. If "no trigger rules" is selected, the post processing will trigger with every upload.
Validation rules (optional)
Some post-process running in sync mode allow to determine attributes for a file that can be used to decide whether or not to take a predetermined validation action at upload (eg. Notice or Refuse the upload)
Webhook url
Target webhook url to POST event to
Hostname
The domain address of the 3d party to post data to
Path
The domain path to post data to
Basic Authentication
Requires a Username and a password
oAuth2 Authentication
Requires an authentication endpoint (with https://), a username and a password
On upload
On change meta
On move
On change info
On rename
On change tag
On delete
On change label
Name
Width
Width
Size
Height
Height
Path
Length (in seconds)
MIME type
Bitrate
CDN link
HLS/DASH playlist URL
File UUID
OBJECTS_LIST
List files
OBJECTS_FETCH
Fetch file
FILE_UPLOAD
Upload file
FILE_META_CREATE
Create file metadata
FILE_RENAME
Rename file
FILE_MOVE
Move file
FILE_DELETE
Delete file
FILE_SET_VISIBILITY
Set file visibility
DIR_CREATE
Create directory
DIR_RENAME
Rename directory
DIR_META_CHANGE
Create directory metadata
DIR_MOVE
Move directory
DIR_DELETE
Delete directory
DIR_SET_VISIBILITY
Set dir visibility
CONFIG_CHANGE
Change container configuration
CONFIG_LIST
List container configuration
FILE_PRODUCT_CHANGE
Change product information
FILE_PROCESS_AUTOTAGGING
Perform autotaggin
OBJECTS_SHARE_MANAGE
Manage shares
OBJECTS_AIRBOX_MANAGE
Manage airbox
OBJECTS_APPROVAL_MANAGE
Manage approval
OBJECTS_APPROVAL_VOTE
Manage approval voting
Limit per min
(limit_per_min)
Set the maximum of upload per minute with the key
Unlimited
Limit per source IP
(limit_per_source_ip)
Maximum number of uploads allowed by IP by the key
Unlimited
Directory scope
(dir_scope)
Directories where the key is allowed to upload. If you want to allow all subdirectories of /folder, set the value to /folder/*
All directories
whitelist_ip_ranges
Allowed IP ranges for using the key from
0.0.0.0 format accepted: 8.8.8.8, 255.240.0.0/12, ...
whitelist_countries
Allowed countries for using the key from. Provide the code ISO of the country
all countries
The IP are converted to country thanks to GeoLite2
expiration_duration
time in second before the key expires
1200 s (20 minutes)
directory_scope
Directories where the key is allowed to list and search assets. If you want to allow all subdirectories of /folder, set the value to /folder/*
All directories
Description
To identify the Security template
Secret key
To be kept secret
Created at
The API key creation date
Scope
Used to limit the scope
Active
The Security template status that can be toggled from active to deactivated using the ... options
Copy
Copy the secret key in the notepad for easy reuse
OBJECTS_LIST
List files
OBJECTS_FETCH
Fetch file
FILE_UPLOAD
Upload file
FILE_META_CREATE
Create file metadata
FILE_RENAME
Rename file
FILE_MOVE
Move file
FILE_DELETE
Delete file
FILE_SET_VISIBILITY
Set file visibility
DIR_CREATE
Create directory
DIR_RENAME
Rename directory
DIR_META_CHANGE
Create directory metadata
DIR_MOVE
Move directory
DIR_DELETE
Delete directory
DIR_SET_VISIBILITY
Set dir visibility
CONFIG_CHANGE
Change container configuration
CONFIG_LIST
List container configuration
FILE_PRODUCT_CHANGE
Change product information
FILE_PROCESS_AUTOTAGGING
Perform autotaggin
OBJECTS_SHARE_MANAGE
Manage shares
OBJECTS_AIRBOX_MANAGE
Manage airbox
OBJECTS_APPROVAL_MANAGE
Manage approval
OBJECTS_APPROVAL_VOTE
Manage approval voting
Control panel where users can manage profile information, login and security settings
| Section | Fields |
|---|---|
Personal info
First name
Last name
Display name
Location
Bio
Profile image
Login info
Email address
Password with Edit password button
Multi-factor authentication
Session timeout
Multi-factor authentication (MFA)
Verify logins by email
Verify logins with SMS
General settings for tag management and use
Tags are managed in Settings -> Tags management. In order to see this page, you need to have a Manager, Admin, Developer or Owner User Role.
Control auto-tagging and whether to allow only the predefined tags in the Tags tab
This tab enables the user to create a dictionary of predefined tags, translate them into all supported languages, and specify whether or not they should be suggested (in the asset management details screen).
You can define a new tag in one or more languages by clicking the "+ Add tag" button, which will take you to the end of the list of current tags. In case there is no specific value for some language, the default language value will be used instead of it.
If the toggle button "Suggested" is ON, then the tag will be shown in the list of suggested tags that appears on Asset Edit.
You can Search by Tag name using the Search box and to define how many columns with Displayed languages to be shown while you are editing the Tags data.
If you select one or more tags using the Selection checkbox at the left of the tag's name, then a navigation menu at the top of the page appears and provides the option to Delete or add multiple tags at once to "Suggested".
| Setting | Description |
|---|---|
Auto tagging
This is an ON/OFF toggle button. If set to "ON" this feature will allow Filerobot to generate tags automatically. External providers are used to analyze the asset and push back tag suggestions for the content of your file.
Max number of automatic (AI) tags
This setting limits the number of tags generated by the external provider when auto-tagging an asset. Its purpose is to prevent the generation of a long list of not relevant tags (in addition to the confidence %)
Auto-tagging confidence
It specifies how confident the external algorithm should be that the auto-generated tag is relevant to the image. Values below 50% are considered low while values >80% are considered high. Only tags having confidence equal to or above the configured value will be shown.
Predefined tags only
A toggle button which, if set to "Yes", disables the Auto-tagging and allows Filerobot to use only the list of already defined tags in the tab "Tags"
Available languages
List of the languages that the tags support. To add/edit/delete languages, please refer to the Localization section
