It is quick and easy to remove the Malcolm! branding and - if you want - replace it with your own. Here is how: **Hosted Hub** By default your Hosted Hub is Malcolm! branded. To change that: * In MyMalcolm go to the Brand section * Click "Themes" on the black sub navigation * The default Malcolm! theme will be selected. Click the "duplicate" icon (two squares overlapping). This will create a copy of the default theme called "Default copy" * Select the Default copy theme by clicking on it. Then click the "edit" icon (a pencil). * This brings up the edit theme interface. There are a huge amount of things you can change here. Use the left hand vertical navigation to browse all the possibilities. **Footer** Be default a "powered by Malcolm!" badge appears at the bottom of content. You can turn this off (and also add other footer content such as copyright notices etc) in the "Footer" section of the edit theme interface referenced above. **Embeds** You can turn off the "powered by Malcolm!" badge in your embeds by turning off the footer. You do this via the style section of your embed configuration. **Domain** Finally don't forget you can easily configure Malcolm! to use your own domain or sub-domain. [For further details see this article.](https://support.malcolm.support/faqs/how-do-i-use-my-own-domain-or-sub-domain)

It is quick and easy to remove the Malcolm! branding and - if you want - replace it with your own. Here is how: **Hosted Hub** By default your Hosted Hub is Malcolm! branded. To change that: * In MyMalcolm go to the Brand section * Click "Themes" on the black sub navigation * The default Malcolm! theme will be selected. Click the "duplicate" icon (two squares overlapping). This will create a copy of the default theme called "Default copy" * Select the Default copy theme by clicking on it. Then click the "edit" icon (a pencil). * This brings up the edit theme interface. There are a huge amount of things you can change here. Use the left hand vertical navigation to browse all the possibilities. **Footer** Be default a "powered by Malcolm!" badge appears at the bottom of content. You can turn this off (and also add other footer content such as copyright notices etc) in the "Footer" section of the edit theme interface referenced above. **Embeds** You can turn off the "powered by Malcolm!" badge in your embeds by turning off the footer. You do this via the style section of your embed configuration. **Domain** Finally don't forget you can easily configure Malcolm! to use your own domain or sub-domain. [For further details see this article.](https://support.malcolm.support/faqs/how-do-i-use-my-own-domain-or-sub-domain)

Malcolm! let's you password protect individual items of content (e.g. a particular FAQ or Workflow) and/or your Hosted Hub. The best option for you will depend on how exactly you use and implement Malcolm! **Password Protection on Hosted Hub** You can add a "start of session" password to your Hosted Hub via the Visibility tab in the Settings section in MyMalcolm. In this area you can add one or more passwords. For example you could add one password that all your users share, or you could give each user an individual password. You can supply a label/description next to the password in MyMalcolm to remind yourself who that password was created for. From the same area you can suspend or delete previously created passwords, as well as see when passwords were last used. When a user visits any page on your Hosted Hub they create a web session. The first time they do this they will be asked for their password. You can configure the exact wording that is used on the password request screen in MyMalcolm! The user will then remain logged in for the remainder of their session. Sessions typically end when the user closes their web browser or after a long period of inactivity. **Password Protection on Individual Content Items** You can also add configure password protection on individual items of content like an FAQ or a Workflow. You do this via the Visibility tab in the Configure section of the individual FAQ or Workflow (which you access via the library in the respective FAQ or Workflow section of MyMalcolm). The default setting for items of content is that they inherit the settings from the Hub. So if no password is set at a Hub level no password is required to view the content. If a password is set at a Hub level then a password will be required at the start of the user session. If you want to ensure that a password is always required before a particular FAQ or Workflow is accessed you should set it at this content level. Bear in mind however that if you also have a Hub password set and a user starts their session with a direct link to individual content that is password protected they will need to enter two passwords: one to get them into the Hub session and a further password to view the content. You can also set an individual item of content to never require a password, even if the Hub has a password set. This can be useful if, for example, you want to put all your content behind a Hub password but want to create a Workflow that lets people request access. In this scenario you would create a Workflow for the purpose of requesting access, set it to never require a password then link to it from the text you can configure on the Hub password request screen. When requests come in you can review them and if you approve you can manually set up the user's password. **Also worth noting** If a user makes three failed password attempts they will not be able to attempt a further password within that session for 30 minutes.

Malcolm! let's you password protect individual items of content (e.g. a particular FAQ or Workflow) and/or your Hosted Hub. The best option for you will depend on how exactly you use and implement Malcolm! **Password Protection on Hosted Hub** You can add a "start of session" password to your Hosted Hub via the Visibility tab in the Settings section in MyMalcolm. In this area you can add one or more passwords. For example you could add one password that all your users share, or you could give each user an individual password. You can supply a label/description next to the password in MyMalcolm to remind yourself who that password was created for. From the same area you can suspend or delete previously created passwords, as well as see when passwords were last used. When a user visits any page on your Hosted Hub they create a web session. The first time they do this they will be asked for their password. You can configure the exact wording that is used on the password request screen in MyMalcolm! The user will then remain logged in for the remainder of their session. Sessions typically end when the user closes their web browser or after a long period of inactivity. **Password Protection on Individual Content Items** You can also add configure password protection on individual items of content like an FAQ or a Workflow. You do this via the Visibility tab in the Configure section of the individual FAQ or Workflow (which you access via the library in the respective FAQ or Workflow section of MyMalcolm). The default setting for items of content is that they inherit the settings from the Hub. So if no password is set at a Hub level no password is required to view the content. If a password is set at a Hub level then a password will be required at the start of the user session. If you want to ensure that a password is always required before a particular FAQ or Workflow is accessed you should set it at this content level. Bear in mind however that if you also have a Hub password set and a user starts their session with a direct link to individual content that is password protected they will need to enter two passwords: one to get them into the Hub session and a further password to view the content. You can also set an individual item of content to never require a password, even if the Hub has a password set. This can be useful if, for example, you want to put all your content behind a Hub password but want to create a Workflow that lets people request access. In this scenario you would create a Workflow for the purpose of requesting access, set it to never require a password then link to it from the text you can configure on the Hub password request screen. When requests come in you can review them and if you approve you can manually set up the user's password. **Also worth noting** If a user makes three failed password attempts they will not be able to attempt a further password within that session for 30 minutes.

First download the Malcolm! Wordpress Plugin [here](https://github.com/acknet/malcolm-wp-plugin/archive/master.zip). In MyMalcolm! create your embeds as normal - [instructions here.](https://support.malcolm.support/faqs/how-do-i-embed-content-from-malcolm-into-my-own-website-or-app) At the end of the Embed creation process when your embed code is generated there is some text which says "Embedding in a Wordpress site?" - if you click that text you will be shown your instance ID and for some embed types you will be shown a shortcode. There is also an option to have this information emailed to you. In Wordpress, install the Malcolm! plugin then goto Settings --> Malcolm! and add your instance ID. Currently on some versions of Wordpress when you add the instance ID and press Save there is no acknowledgement of this but you can verify the instance ID has indeed been saved by navigating away and then back to Settings --> Malcolm! For Widget and Full page embeds this is all you have to do - you can then configure on which pages your embeds appear via MyMalcolm (via the URL rules section of the respective embed). For inline embeds and overlays you need to position where you would like the embed or the overlay launcher in your content. You do this using the Shortcode. Go to the page or post in Wordpress, make sure you are in code editor (not visual editor) and put the Shortcode where you wish the embed to appear / or the overlay be launched from. If you have any issues with you embeds not appearing [first check these things.](https://support.malcolm.support/faqs/why-is-my-embed-not-showing)

First download the Malcolm! Wordpress Plugin [here](https://github.com/acknet/malcolm-wp-plugin/archive/master.zip). In MyMalcolm! create your embeds as normal - [instructions here.](https://support.malcolm.support/faqs/how-do-i-embed-content-from-malcolm-into-my-own-website-or-app) At the end of the Embed creation process when your embed code is generated there is some text which says "Embedding in a Wordpress site?" - if you click that text you will be shown your instance ID and for some embed types you will be shown a shortcode. There is also an option to have this information emailed to you. In Wordpress, install the Malcolm! plugin then goto Settings --> Malcolm! and add your instance ID. Currently on some versions of Wordpress when you add the instance ID and press Save there is no acknowledgement of this but you can verify the instance ID has indeed been saved by navigating away and then back to Settings --> Malcolm! For Widget and Full page embeds this is all you have to do - you can then configure on which pages your embeds appear via MyMalcolm (via the URL rules section of the respective embed). For inline embeds and overlays you need to position where you would like the embed or the overlay launcher in your content. You do this using the Shortcode. Go to the page or post in Wordpress, make sure you are in code editor (not visual editor) and put the Shortcode where you wish the embed to appear / or the overlay be launched from. If you have any issues with you embeds not appearing [first check these things.](https://support.malcolm.support/faqs/why-is-my-embed-not-showing)

Invisible tags are a useful way you can influence search results. Like normal tags they will contribute to search ranking of an FAQ, but they won't be shown on the front-end to your users. If you therefore want a particular phrase to return a particular FAQ but your content doesn't feature that phrase or is being out ranked by another FAQ invisible tags can help. You can make current tags invisible or set up new invisible tags in MyMalcolm via FAQs / Tags: You then apply tags as usual via the configure area of the individual FAQ:

Invisible tags are a useful way you can influence search results. Like normal tags they will contribute to search ranking of an FAQ, but they won't be shown on the front-end to your users. If you therefore want a particular phrase to return a particular FAQ but your content doesn't feature that phrase or is being out ranked by another FAQ invisible tags can help. You can make current tags invisible or set up new invisible tags in MyMalcolm via FAQs / Tags: You then apply tags as usual via the configure area of the individual FAQ:

When you create an Overlay embed we give you two bits of code to add to your page. The first is the master code which you should place just before the closing ``` ``` tag. The second is the inline code which generates the button users click to open the overlay - this goes inside the ``` ``` ``` ``` tags where you want the button to appear. When the user clicks the button the Overlay embed will appear in a modal (pop-up) over your page. The inline code we give you will look like this ``` ``` Sometimes you might want to call the overlay but not use our button. You might want to call it from text or use your own button/graphic or you might want to call it in the background when a user does something else on your page. You can do this by calling mapi in Javascript. The mapi has four methods - open, close, trigger and toggle. Open, close and toggle all return promises (i.e. a function that resolves when the animation is complete or a rejects if something went wrong, e.g. no embed found for the param passed). Trigger is more "fire and forget" - it will call the open function if everything goes well, otherwise it silently fails. Here is an example using an href link that uses the trigger method to open the Overlay: ``` Click me ``` Note that you must have our master embed code on your page for the above to work and you need to replace INSERT_EMBED_ID_HERE with your embed ID. The above may also be useful for customers who are using third party site building systems - sometimes putting inline code into a page on those systems can be restricted so you can't add our inline code to render your button. If you can create inline links you could try using the above example with the trigger method to open the Overlay (again remember you also need the master code on the page).

When you create an Overlay embed we give you two bits of code to add to your page. The first is the master code which you should place just before the closing ``` ``` tag. The second is the inline code which generates the button users click to open the overlay - this goes inside the ``` ``` ``` ``` tags where you want the button to appear. When the user clicks the button the Overlay embed will appear in a modal (pop-up) over your page. The inline code we give you will look like this ``` ``` Sometimes you might want to call the overlay but not use our button. You might want to call it from text or use your own button/graphic or you might want to call it in the background when a user does something else on your page. You can do this by calling mapi in Javascript. The mapi has four methods - open, close, trigger and toggle. Open, close and toggle all return promises (i.e. a function that resolves when the animation is complete or a rejects if something went wrong, e.g. no embed found for the param passed). Trigger is more "fire and forget" - it will call the open function if everything goes well, otherwise it silently fails. Here is an example using an href link that uses the trigger method to open the Overlay: ``` Click me ``` Note that you must have our master embed code on your page for the above to work and you need to replace INSERT_EMBED_ID_HERE with your embed ID. The above may also be useful for customers who are using third party site building systems - sometimes putting inline code into a page on those systems can be restricted so you can't add our inline code to render your button. If you can create inline links you could try using the above example with the trigger method to open the Overlay (again remember you also need the master code on the page).

A Workflow is a web based form that your customers complete. You can build these forms quickly in MyMalcolm and use them to create a digital version of a business process. **For example** * A contact form * A survey * A customer enquiry * A new customer details form You can build everything from simple single screen journeys through to more complex multi-step journeys with conditional routing (ie offering certain choices based on previous answers). Malcolm! automatically stores all data - including abandoned forms. You can export this data at any time. You can also pass that collected data through to other systems via Integrations or Webhooks.

A Workflow is a web based form that your customers complete. You can build these forms quickly in MyMalcolm and use them to create a digital version of a business process. **For example** * A contact form * A survey * A customer enquiry * A new customer details form You can build everything from simple single screen journeys through to more complex multi-step journeys with conditional routing (ie offering certain choices based on previous answers). Malcolm! automatically stores all data - including abandoned forms. You can export this data at any time. You can also pass that collected data through to other systems via Integrations or Webhooks.

Sometimes you may wish to use Workflows but restrict other Team members on your instance from having access to the data that is submitted by your end users. **Here is how to do this:** * Access is managed via the "Team" section of MyMalcolm. * In that section if you click on a Team Member then select "privileges" you can configure whether a user can see and/or export submitted Workflow data. You can even remove all their access to the Workflow section. * Depending on their settings the Instance Owner and some Team Members may also receive submitted data via email alerts. [See more about managing email alerts here.](https://support.malcolm.support/faqs/can-i-turn-off-automatic-email-alerts) * Regardless of their own preferences Team Members won't receive email alerts relating to Workflow completion if they don't have access to Workflow submitted values and exports. **Some related things to be aware of:** * Remember that on a Workflow level further email recipients can be added in the "email answers" part of the configure section of the individual Workflow - it may make sense to review this recipient list at the same time you review who on your team has access to end user submitted data. * Be aware that if you are pushing some or all of the submitted data to third party systems via Integrations or Web Hooks then submitted data will potentially be viewable by users in those systems. [We recommend that you review this article to read about GDPR and how it applies to Malcolm! and your users.](https://support.malcolm.support/faqs/is-malcolm-gdpr-compliant)

Sometimes you may wish to use Workflows but restrict other Team members on your instance from having access to the data that is submitted by your end users. **Here is how to do this:** * Access is managed via the "Team" section of MyMalcolm. * In that section if you click on a Team Member then select "privileges" you can configure whether a user can see and/or export submitted Workflow data. You can even remove all their access to the Workflow section. * Depending on their settings the Instance Owner and some Team Members may also receive submitted data via email alerts. [See more about managing email alerts here.](https://support.malcolm.support/faqs/can-i-turn-off-automatic-email-alerts) * Regardless of their own preferences Team Members won't receive email alerts relating to Workflow completion if they don't have access to Workflow submitted values and exports. **Some related things to be aware of:** * Remember that on a Workflow level further email recipients can be added in the "email answers" part of the configure section of the individual Workflow - it may make sense to review this recipient list at the same time you review who on your team has access to end user submitted data. * Be aware that if you are pushing some or all of the submitted data to third party systems via Integrations or Web Hooks then submitted data will potentially be viewable by users in those systems. [We recommend that you review this article to read about GDPR and how it applies to Malcolm! and your users.](https://support.malcolm.support/faqs/is-malcolm-gdpr-compliant)

Malcolm! will automatically send you email alerts when certain activity happens on your instance, such as a user leaving feedback or a Workflow being completed. Wherever possible we aggregate these alerts so you receive fewer emails but if you'd rather not receive them you can easily turn them off. To do this, from the MyMalcolm control panel area, click your name at the top of the screen where it says "Logged in as" You'll then be taken to your personal preferences. If you select the "Notifications" tab on the left you'll be able to edit the notifications you receive. Remember to hit "Save" once you are done! Note that your notificatons are based on an instance. If you are a user on more than one instance you should first switch to the instance you wish to adjust notifications for. You can do this using the drop down selector at the top right of the screen. You can therefore have different notification preferences for different instances. The notificiation preferences you choose are personal to you and will not affect the notifications of other team members on an instance.

Malcolm! will automatically send you email alerts when certain activity happens on your instance, such as a user leaving feedback or a Workflow being completed. Wherever possible we aggregate these alerts so you receive fewer emails but if you'd rather not receive them you can easily turn them off. To do this, from the MyMalcolm control panel area, click your name at the top of the screen where it says "Logged in as" You'll then be taken to your personal preferences. If you select the "Notifications" tab on the left you'll be able to edit the notifications you receive. Remember to hit "Save" once you are done! Note that your notificatons are based on an instance. If you are a user on more than one instance you should first switch to the instance you wish to adjust notifications for. You can do this using the drop down selector at the top right of the screen. You can therefore have different notification preferences for different instances. The notificiation preferences you choose are personal to you and will not affect the notifications of other team members on an instance.

Webhooks allow you to set up your own integrations to Malcolm! Workflow. By subscribing to the Workflow Completed event you will receive a HTTP POST Payload containing information about the completed Session. You could use this information to keep local records of when your Workflows are completed as well as receiving meta data like the start and completed times. For security and data privacy reasons we do not include the submitted Values in the payload. There are numerous ways the Values can be retrieved and matched up to the Session. The simplest way is to use the MyMalcolm Control Panel. Here you can view or export the Values. Alternatively, if you're on our Enterprise Plan, you can request an API Key and programmatically fetch the Values using our friendly REST API. ## Configuration Webhooks are are configured in "Workflow > Configure > Webhooks" section of MyMalcolm. The only requirement when adding or editing an existing Webhook is the URL. This is the URL Malcolm! will send the HTTP POST Payload to. The URL should be a secure URL (that means it starts with https://) and publicly accessible - i.e. not behind a firewall or on a local machine. There are conditional controls available too. If you have a condition configured the HTTP POST Payload will only be sent if the conditions at the end of the Workflow are satisfied. ## Payload The Payload is a simple HTTP POST with JSON Body. The Payload will contain the following special Headers. | Header | Description | |---|---| | X-Instance-Id | The ID of the Instance. E.g. "xxxxxxxxxx" | The Body will contain the following attributes. | Attribute | Description | |---|---| | id | The ID of the Workflow Session. E.g. "xxxxxxxxxx" | | label | A descriptive label, which will include the name of the person who completed the Workflow if your Workflow contains name attributes. E.g. "Completed by Malcolm!" | | locale | The locale used during the Workflow. E.g. "en-GB" | | started-at | The localised date and time the Session was started. E.g. "2020-04-01 12:00:00" | | completed-at | The localised date and time the Session was completed. E.g. "2020-04-01 12:00:00" | | workflow.id | The ID of the Workflow. E.g. "xxxxxxxxxx" | | workflow.name | The name of the Workflow. E.g. "Open Support Ticket" | | workflow.published-at | The localised date and time the Workflow was published. E.g. "2020-04-01 09:00:00" | | workflow.version | The name of the Workflow version. E.g. "Version 1" | ### Example Payload ``` POST /workflow-completed HTTP/1.1 Host: webhooks.my-domain.com Content-Type: application/json X-Instance-Id: xxxxxxxxxx { "id": "xxxxxxxxxx", "label": "Completed by Malcolm!", "locale": "en-GB", "started-at": "2020-04-01 12:00:00", "completed-at": "2020-04-01 12:05:00", "workflow": { "id": "xxxxxxxxxx", "name": "Open Support Ticket", "published-at": "2020-04-01 09:00:00", "version": "Version 1" } } ``` ## API For Enterprise customers a further HTTP GET Payload can be used to fetch the associated Values. | Endpoint | |---| | GET /sessions/xxxxxxxxxx/values | | Header | Description | |---|---| | Host | api.malcolm.solutions/1.0/workflow-api | | Accept | application/json | | Authorization | A Bearer string composed by concatenating "api-key:" and your API key and then Base 64-encoding the result. E.g. "Bearer xxxxxxxxxx" | | X-Instance-Id | The ID of the Instance. E.g. "xxxxxxxxxx" | ### Example Response ``` { "data": [ { "attributes": { "is-valid": true, "value": "Malcolm!" }, "id": "xxxxxxxxxx", "links": { "self": "/values/xxxxxxxxxx" }, "meta": { "field": { "id": "xxxxxxxxxx", "name": "Name", "required": true, "type": "Name" } }, "relationships": { "field": { "links": { "related": "/values/xxxxxxxxxx/field", "self": "/values/xxxxxxxxxx/relationships/field" } } }, "type": "values" }, ... ], "links": { "first": "/sessions/xxxxxxxxxx/values?page=1", "last": "/sessions/xxxxxxxxxx/values?page=1", "self": "/sessions/xxxxxxxxxx/values?page=1" }, "meta": { "pagination": { "total": 1, "per-page": 1, "current-page": 1, "page-count": 1, "from": 1, "to": 1 } } } ``` For further help or information on our Enterprise Plan please contact the [Support Team](mailto:support@malcolm.support).

Webhooks allow you to set up your own integrations to Malcolm! Workflow. By subscribing to the Workflow Completed event you will receive a HTTP POST Payload containing information about the completed Session. You could use this information to keep local records of when your Workflows are completed as well as receiving meta data like the start and completed times. For security and data privacy reasons we do not include the submitted Values in the payload. There are numerous ways the Values can be retrieved and matched up to the Session. The simplest way is to use the MyMalcolm Control Panel. Here you can view or export the Values. Alternatively, if you're on our Enterprise Plan, you can request an API Key and programmatically fetch the Values using our friendly REST API. ## Configuration Webhooks are are configured in "Workflow > Configure > Webhooks" section of MyMalcolm. The only requirement when adding or editing an existing Webhook is the URL. This is the URL Malcolm! will send the HTTP POST Payload to. The URL should be a secure URL (that means it starts with https://) and publicly accessible - i.e. not behind a firewall or on a local machine. There are conditional controls available too. If you have a condition configured the HTTP POST Payload will only be sent if the conditions at the end of the Workflow are satisfied. ## Payload The Payload is a simple HTTP POST with JSON Body. The Payload will contain the following special Headers. | Header | Description | |---|---| | X-Instance-Id | The ID of the Instance. E.g. "xxxxxxxxxx" | The Body will contain the following attributes. | Attribute | Description | |---|---| | id | The ID of the Workflow Session. E.g. "xxxxxxxxxx" | | label | A descriptive label, which will include the name of the person who completed the Workflow if your Workflow contains name attributes. E.g. "Completed by Malcolm!" | | locale | The locale used during the Workflow. E.g. "en-GB" | | started-at | The localised date and time the Session was started. E.g. "2020-04-01 12:00:00" | | completed-at | The localised date and time the Session was completed. E.g. "2020-04-01 12:00:00" | | workflow.id | The ID of the Workflow. E.g. "xxxxxxxxxx" | | workflow.name | The name of the Workflow. E.g. "Open Support Ticket" | | workflow.published-at | The localised date and time the Workflow was published. E.g. "2020-04-01 09:00:00" | | workflow.version | The name of the Workflow version. E.g. "Version 1" | ### Example Payload ``` POST /workflow-completed HTTP/1.1 Host: webhooks.my-domain.com Content-Type: application/json X-Instance-Id: xxxxxxxxxx { "id": "xxxxxxxxxx", "label": "Completed by Malcolm!", "locale": "en-GB", "started-at": "2020-04-01 12:00:00", "completed-at": "2020-04-01 12:05:00", "workflow": { "id": "xxxxxxxxxx", "name": "Open Support Ticket", "published-at": "2020-04-01 09:00:00", "version": "Version 1" } } ``` ## API For Enterprise customers a further HTTP GET Payload can be used to fetch the associated Values. | Endpoint | |---| | GET /sessions/xxxxxxxxxx/values | | Header | Description | |---|---| | Host | api.malcolm.solutions/1.0/workflow-api | | Accept | application/json | | Authorization | A Bearer string composed by concatenating "api-key:" and your API key and then Base 64-encoding the result. E.g. "Bearer xxxxxxxxxx" | | X-Instance-Id | The ID of the Instance. E.g. "xxxxxxxxxx" | ### Example Response ``` { "data": [ { "attributes": { "is-valid": true, "value": "Malcolm!" }, "id": "xxxxxxxxxx", "links": { "self": "/values/xxxxxxxxxx" }, "meta": { "field": { "id": "xxxxxxxxxx", "name": "Name", "required": true, "type": "Name" } }, "relationships": { "field": { "links": { "related": "/values/xxxxxxxxxx/field", "self": "/values/xxxxxxxxxx/relationships/field" } } }, "type": "values" }, ... ], "links": { "first": "/sessions/xxxxxxxxxx/values?page=1", "last": "/sessions/xxxxxxxxxx/values?page=1", "self": "/sessions/xxxxxxxxxx/values?page=1" }, "meta": { "pagination": { "total": 1, "per-page": 1, "current-page": 1, "page-count": 1, "from": 1, "to": 1 } } } ``` For further help or information on our Enterprise Plan please contact the [Support Team](mailto:support@malcolm.support).

Each instance of Malcolm! initially comes with a 0.5GB allocation of file storage space. Because a web bowser will download all content on a page it's good practice (for page loading speed and also SEO purposes) to try and keep each image on your page under 2MB and not include too many images on any one page. [Squarespace have a good general guide here.](https://support.squarespace.com/hc/en-us/articles/206542517-Formatting-your-images-for-display-on-the-web) Video files should not be uploaded to Malcolm! - instead use YouTube or Vimeo and embed your content - [see here for more info.](https://support.malcolm.support/faqs/can-i-embed-youtube-or-vimeo-videos-in-my-faqs). This offers a much better experience for your users (they get a device/speed appropriate stream) and your page download speed will not be compromised. If you wish to make large documents available for download consider using a dedicated file hosting service (eg Dropbox, Google Drive, WeTransfer etc) and linking to that from your FAQs. This is better user experience because your user will be made aware of the file size before starting the download. Remember in particular your mobile users who may be viewing your content via significantly slower connections! If you do find yourself nearing the limit of your initial allocation [contact us](https://support.malcolm.support/workflows/submit-support-ticket) to request a higher allocation and we can provision this for you - there is no extra charge for this.

Each instance of Malcolm! initially comes with a 0.5GB allocation of file storage space. Because a web bowser will download all content on a page it's good practice (for page loading speed and also SEO purposes) to try and keep each image on your page under 2MB and not include too many images on any one page. [Squarespace have a good general guide here.](https://support.squarespace.com/hc/en-us/articles/206542517-Formatting-your-images-for-display-on-the-web) Video files should not be uploaded to Malcolm! - instead use YouTube or Vimeo and embed your content - [see here for more info.](https://support.malcolm.support/faqs/can-i-embed-youtube-or-vimeo-videos-in-my-faqs). This offers a much better experience for your users (they get a device/speed appropriate stream) and your page download speed will not be compromised. If you wish to make large documents available for download consider using a dedicated file hosting service (eg Dropbox, Google Drive, WeTransfer etc) and linking to that from your FAQs. This is better user experience because your user will be made aware of the file size before starting the download. Remember in particular your mobile users who may be viewing your content via significantly slower connections! If you do find yourself nearing the limit of your initial allocation [contact us](https://support.malcolm.support/workflows/submit-support-ticket) to request a higher allocation and we can provision this for you - there is no extra charge for this.