Malcolm! auto generates certain listings of FAQs such as most helpful, most popular, recently added and trending. If an FAQ is hidden ([see here for more info](https://support.malcolm.support/faqs/how-do-i-hide-an-faq) it won't be included in these listings but sometimes you may wish to exclude a regular non hidden FAQ from these listings. You can do this via in MyMalcolm via the individual FAQ's visibility settings (FAQs / Library / Configure / Visibility):

Malcolm! auto generates certain listings of FAQs such as most helpful, most popular, recently added and trending. If an FAQ is hidden ([see here for more info](https://support.malcolm.support/faqs/how-do-i-hide-an-faq) it won't be included in these listings but sometimes you may wish to exclude a regular non hidden FAQ from these listings. You can do this via in MyMalcolm via the individual FAQ's visibility settings (FAQs / Library / Configure / Visibility):

You can add Javascript tracking tags via the Settings Section of MyMalcolm. Select Tracking tags within that section. For Google Analytics you can just add your GA ID. For users of Google Tag Manager you can add your GTM ID then manage all tags via their interface. For any other tags add these in the "Any other Javascript snippets" area. If you wish to use another tag manager you could add that tag managers code in the "Any other Javascript snippets" area and then manage your tags via their interface.

You can add Javascript tracking tags via the Settings Section of MyMalcolm. Select Tracking tags within that section. For Google Analytics you can just add your GA ID. For users of Google Tag Manager you can add your GTM ID then manage all tags via their interface. For any other tags add these in the "Any other Javascript snippets" area. If you wish to use another tag manager you could add that tag managers code in the "Any other Javascript snippets" area and then manage your tags via their interface.

Integrations are a way of passing data you collect in a Malcolm! Workflow into other third party software or systems. We currently offer integrations with: * [Dropbox](http://www.dropbox.com) * [Mailchimp](http://www.mailchimp.com) * [Mandrill](http://www.mandrill.com) * [Twilio](http://www.twilio.com) * [Zendesk](http://www.zendesk.com) * and over 1,500 over apps via Zapier.com ([more info here](https://support.malcolm.support/faqs/how-do-i-use-zapier-to-connect-malcolm-to-other-applications-or-services-i-use)) **Configuring Integrations** Once you have created your Workflow, go to the Configure section and select Integrations. There you can link your third party accounts at our integration partners to your Malcolm! Instance by providing your credentials. Once your accounts are linked you can configure integrations with that partner and choose the data from your Workflow that is passed across. You can configure whether data is passed on every Workflow completion or only when certain conditions are met. It is possible to have multiple integrations so, for example, you could create a form which collected details from a new customer including a copy of their ID. You could then subscribe that new customer to a Mailchimp mailing list and store their uploaded ID documents in your Dropbox account by creating two integrations. **Customer Consent** A reminder that it is good practice - and in certain territories a legal requirement - to ensure that your customers actively consent to their data being passed to third party companies who, like Malcolm!, act as data processors on your behalf. You act as the data controller. Most companies handle this consent via provisions in their Privacy Policy which their customers agree to. It is good practice therefore to include a check box in your Workflows that reminds customers of your Privacy Policy and their continuing agreement of it. **Integration Failures** Sometimes integrations may fail. This could be for a variety of reasons, for example the integration partner's API's may be down and/or there may be a problem with your account at the third party provider (for example your Dropbox account may be over quota). Firstly don't worry re losing customer data - Malcolm! will always store any user submitted data so if there is a problem with an integration you won't lose any data. When a problem occurs we'll create a notification to let you know and periodically retry the integration. You can review the Integration logs and retry a failed integration event manually via MyMalcolm (navigate to the Workflow via Library then select Integration logs) **More Integrations coming soon!** We will be adding more and more integrations to Malcolm! in the coming months. If there is a particular integration you'd like us to add [please let us know! ](https://support.malcolm.support/workflows/feedback)

Integrations are a way of passing data you collect in a Malcolm! Workflow into other third party software or systems. We currently offer integrations with: * [Dropbox](http://www.dropbox.com) * [Mailchimp](http://www.mailchimp.com) * [Mandrill](http://www.mandrill.com) * [Twilio](http://www.twilio.com) * [Zendesk](http://www.zendesk.com) * and over 1,500 over apps via Zapier.com ([more info here](https://support.malcolm.support/faqs/how-do-i-use-zapier-to-connect-malcolm-to-other-applications-or-services-i-use)) **Configuring Integrations** Once you have created your Workflow, go to the Configure section and select Integrations. There you can link your third party accounts at our integration partners to your Malcolm! Instance by providing your credentials. Once your accounts are linked you can configure integrations with that partner and choose the data from your Workflow that is passed across. You can configure whether data is passed on every Workflow completion or only when certain conditions are met. It is possible to have multiple integrations so, for example, you could create a form which collected details from a new customer including a copy of their ID. You could then subscribe that new customer to a Mailchimp mailing list and store their uploaded ID documents in your Dropbox account by creating two integrations. **Customer Consent** A reminder that it is good practice - and in certain territories a legal requirement - to ensure that your customers actively consent to their data being passed to third party companies who, like Malcolm!, act as data processors on your behalf. You act as the data controller. Most companies handle this consent via provisions in their Privacy Policy which their customers agree to. It is good practice therefore to include a check box in your Workflows that reminds customers of your Privacy Policy and their continuing agreement of it. **Integration Failures** Sometimes integrations may fail. This could be for a variety of reasons, for example the integration partner's API's may be down and/or there may be a problem with your account at the third party provider (for example your Dropbox account may be over quota). Firstly don't worry re losing customer data - Malcolm! will always store any user submitted data so if there is a problem with an integration you won't lose any data. When a problem occurs we'll create a notification to let you know and periodically retry the integration. You can review the Integration logs and retry a failed integration event manually via MyMalcolm (navigate to the Workflow via Library then select Integration logs) **More Integrations coming soon!** We will be adding more and more integrations to Malcolm! in the coming months. If there is a particular integration you'd like us to add [please let us know! ](https://support.malcolm.support/workflows/feedback)

If you want to send an end user who completes a Workflow an email you can do this via an integration. We currently offer a direct Mandrill integration and there are lots of options [via Zapier](https://zapier.com/apps/categories/transactional-email). The reason for this approach is that you are likely to want to send a branded email to your Workflow form filler and you are likely to want to send it from your own email address. Because of this it's better to pass the data through from Malcolm! to an account you have with a transactional email service where you have set up SPF and DKIM etc to ensure deliverability. They also offer a whole load of functionality it doesn't make sense for us to replicate our side.

If you want to send an end user who completes a Workflow an email you can do this via an integration. We currently offer a direct Mandrill integration and there are lots of options [via Zapier](https://zapier.com/apps/categories/transactional-email). The reason for this approach is that you are likely to want to send a branded email to your Workflow form filler and you are likely to want to send it from your own email address. Because of this it's better to pass the data through from Malcolm! to an account you have with a transactional email service where you have set up SPF and DKIM etc to ensure deliverability. They also offer a whole load of functionality it doesn't make sense for us to replicate our side.

The Malcolm! widget is a great way to put your content in front of users. By using the widget you can float content over an existing website or application. Want to let your users find out answers to FAQs about a product or service you provide but don't want them to make them navigate from the screen they are on? The Malcolm! widget is what you need. Or perhaps you'd like to float a feedback or get in touch form over your website? Super easy to do with the Malcolm! widget. You can even make the content displayed contextual to the screen the widget is floating over. How cool is that? We recommend you place the Malcolm! widget embed code on every page of your website. You can then configure whether the widget displays or not (and what it displays) from within MyMalcolm! Here is how to start using the Malcolm! widget. **Step 1: Create an embed** Go the Share section of MyMalcolm and select the Embed tab and then Create an embed. Select Widget as the type of embed you want to create. Give your embed a name. **Step 2: Choose your content** From this area you can choose a single FAQ or Workflow to display in the widget, or you can choose collections of content. These collections can be a category, a tag or an author. You can also make a collection out of a search result including a search that is contextual to the meta content of the page that the widget is on - you can query content based on the page title, meta keywords, meta description or a meta search tag. Users can navigate content within the widget via clicking on items in the user interface eg categories, tags or authors. If you don't choose a specific FAQ, Workflow or collection of content the default content displayed will be the most popular content. **Step 3: Configure the visual style of your widget** You can configure various options about the visual appearance and behaviour of your widget. The options include what the widget looks like in it's pre-expand state (a button or a drawer), the text used on the pre-expand, the colours and logo plus the location of the widget on your screen. You can also configure whether you want the search and footer used on expanded widget and whether the transition from pre-expand to post-expand and vice versa are animated or not. **Step 4: Set up URL rules and visibility settings** We recommend you put the Malcolm! widget embed code on every page of your website. But you might not want the widget to appear on every page. Using URL rules you can mangage and easily change which pages the widget does appear on from within MyMalcolm! You may not want the widget to display on mobile browsers, or you may want the widget to only appear at certain times (for example when your office is closed) - you can configure these options in visibility settings. **Step 5: Publish and place code on site** Finally when you are happy publish your widget. Finally collect your code - you can cut and paste this or have it emailed to you (or the person who is responsible for implementation). If you use Google Tag Manager you can also deploy the embed code via this system. [See here for more details.](https://support.malcolm.support/faqs/can-i-put-malcolm-widget-code-into-another-site-via-google-tag-manager)

The Malcolm! widget is a great way to put your content in front of users. By using the widget you can float content over an existing website or application. Want to let your users find out answers to FAQs about a product or service you provide but don't want them to make them navigate from the screen they are on? The Malcolm! widget is what you need. Or perhaps you'd like to float a feedback or get in touch form over your website? Super easy to do with the Malcolm! widget. You can even make the content displayed contextual to the screen the widget is floating over. How cool is that? We recommend you place the Malcolm! widget embed code on every page of your website. You can then configure whether the widget displays or not (and what it displays) from within MyMalcolm! Here is how to start using the Malcolm! widget. **Step 1: Create an embed** Go the Share section of MyMalcolm and select the Embed tab and then Create an embed. Select Widget as the type of embed you want to create. Give your embed a name. **Step 2: Choose your content** From this area you can choose a single FAQ or Workflow to display in the widget, or you can choose collections of content. These collections can be a category, a tag or an author. You can also make a collection out of a search result including a search that is contextual to the meta content of the page that the widget is on - you can query content based on the page title, meta keywords, meta description or a meta search tag. Users can navigate content within the widget via clicking on items in the user interface eg categories, tags or authors. If you don't choose a specific FAQ, Workflow or collection of content the default content displayed will be the most popular content. **Step 3: Configure the visual style of your widget** You can configure various options about the visual appearance and behaviour of your widget. The options include what the widget looks like in it's pre-expand state (a button or a drawer), the text used on the pre-expand, the colours and logo plus the location of the widget on your screen. You can also configure whether you want the search and footer used on expanded widget and whether the transition from pre-expand to post-expand and vice versa are animated or not. **Step 4: Set up URL rules and visibility settings** We recommend you put the Malcolm! widget embed code on every page of your website. But you might not want the widget to appear on every page. Using URL rules you can mangage and easily change which pages the widget does appear on from within MyMalcolm! You may not want the widget to display on mobile browsers, or you may want the widget to only appear at certain times (for example when your office is closed) - you can configure these options in visibility settings. **Step 5: Publish and place code on site** Finally when you are happy publish your widget. Finally collect your code - you can cut and paste this or have it emailed to you (or the person who is responsible for implementation). If you use Google Tag Manager you can also deploy the embed code via this system. [See here for more details.](https://support.malcolm.support/faqs/can-i-put-malcolm-widget-code-into-another-site-via-google-tag-manager)

It's quick and easy to embed a Workflow into your website or app. In the Library screen of the Workflow section of MyMalcolm click the three dots on the right hand side of the screen and select "Embed" This will take you into the Share section of MyMalcolm! Here you can choose the type of embed you want to create. * If you want to float your Workflow over your webpage in a widget launched from a button or drawer that hugs the side or top/bottom of the screen select Widget. * If you want to launch an overlay that contains your Workflow from your webpage choose the Overlay option. * If you want your Workflow to appear within a part of an exisiting webpage select the inline option. * Finally if you want your Workflow to replace the entire content of a page select Full page. Follow the create embed process through - the Workflow you came from will be preselected as the content you want to embed. You will be offered various styling and display options based on the type of embed you choose. At the end of the process you will be supplied with the embed code that you can add to he site or app where you want the Workflow to appear.

It's quick and easy to embed a Workflow into your website or app. In the Library screen of the Workflow section of MyMalcolm click the three dots on the right hand side of the screen and select "Embed" This will take you into the Share section of MyMalcolm! Here you can choose the type of embed you want to create. * If you want to float your Workflow over your webpage in a widget launched from a button or drawer that hugs the side or top/bottom of the screen select Widget. * If you want to launch an overlay that contains your Workflow from your webpage choose the Overlay option. * If you want your Workflow to appear within a part of an exisiting webpage select the inline option. * Finally if you want your Workflow to replace the entire content of a page select Full page. Follow the create embed process through - the Workflow you came from will be preselected as the content you want to embed. You will be offered various styling and display options based on the type of embed you choose. At the end of the process you will be supplied with the embed code that you can add to he site or app where you want the Workflow to appear.

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.

You can change the text label next to the email an FAQ feature on an indiviual FAQ. This can be useful if you are using the FAQ part of Malcolm! to publish articles or other types of content rather than just answers to questions and the "email this answer" language no longer makes sense. To update the text go to the Brand section in MyMalcolm, then Themes, then click the edit icon in the relevant theme then select "FAQs" in the left hand nav.

You can change the text label next to the email an FAQ feature on an indiviual FAQ. This can be useful if you are using the FAQ part of Malcolm! to publish articles or other types of content rather than just answers to questions and the "email this answer" language no longer makes sense. To update the text go to the Brand section in MyMalcolm, then Themes, then click the edit icon in the relevant theme then select "FAQs" in the left hand nav.

If you'd like to hide the "last updated" date displayed on an FAQ you can do this on a per FAQ basis via the Configure / General area of the FAQ in MyMalcolm: If you want to turn off this feature for all FAQ's in the instance you can do this globally via Settings / FAQs / General Settings:

If you'd like to hide the "last updated" date displayed on an FAQ you can do this on a per FAQ basis via the Configure / General area of the FAQ in MyMalcolm: If you want to turn off this feature for all FAQ's in the instance you can do this globally via Settings / FAQs / General Settings:

**What is GDPR?** "GDPR" refers to The General Data Protection Regulation 2016/679. This is a regulation in EU law on data protection and privacy for all individuals within the European Union and the European Economic Area. It also addresses the export of personal data outside the EU and EEA areas. **How does it apply to Malcolm?** Malcolm! collects, stores and processes data about our own customers - people signing up to Malcolm! and creating and managing instances. We may also - via Workflows - collect, store, process and transfer data about your customers. When talking about GDPR it is important to understand the concept of the Data Controller and the Data Processor. * The **Data Controller** determines the purposes for which and the means by which personal data is processed * The **Data Processor** processes personal data only on behalf of the controller. **Is Malcolm! the Data Controller or the Data Processor?** In the context of information about our own customers, eg people who sign up for Malcolm! accounts and manage Instances we are the Data Controller. In the context of information about your customers, eg information that is collected on your behalf via Workflows you create in Malcolm! we are the Data Processor only. You - as the Data Controller - have the obligation to ensure you are acting lawfully in accordance with the GDPR legislation. **What does all this mean?** When you sign up to Malcolm! you agree to our [Terms of Service](https://malcolm.support/terms) and our [Privacy Policy](https://malcolm.support/privacy) which detail how we handle your data. By agreeing you give us your consent. It is important that when you collect, store, process and potentially transfer (via Integrations or Exports) data from your own customers via a Malcolm! Workflow you have your customers consent to do this. Most companies handle this via provisions in their Privacy Policy and/or Terms and Conditions around data processing which their customers agree to. **It is therefore good practice to include a check box in your Workflows that reminds customers of your Privacy Policy and their continuing agreement of it and/or confirms their consent for you to collect and process their information** **Further Questions** If you have further questions about GDPR or wish to contact our Data Protection Officer [you can contact us here](https://malcolm.support/contact). [You can find out more about GDPR here. ](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/)

**What is GDPR?** "GDPR" refers to The General Data Protection Regulation 2016/679. This is a regulation in EU law on data protection and privacy for all individuals within the European Union and the European Economic Area. It also addresses the export of personal data outside the EU and EEA areas. **How does it apply to Malcolm?** Malcolm! collects, stores and processes data about our own customers - people signing up to Malcolm! and creating and managing instances. We may also - via Workflows - collect, store, process and transfer data about your customers. When talking about GDPR it is important to understand the concept of the Data Controller and the Data Processor. * The **Data Controller** determines the purposes for which and the means by which personal data is processed * The **Data Processor** processes personal data only on behalf of the controller. **Is Malcolm! the Data Controller or the Data Processor?** In the context of information about our own customers, eg people who sign up for Malcolm! accounts and manage Instances we are the Data Controller. In the context of information about your customers, eg information that is collected on your behalf via Workflows you create in Malcolm! we are the Data Processor only. You - as the Data Controller - have the obligation to ensure you are acting lawfully in accordance with the GDPR legislation. **What does all this mean?** When you sign up to Malcolm! you agree to our [Terms of Service](https://malcolm.support/terms) and our [Privacy Policy](https://malcolm.support/privacy) which detail how we handle your data. By agreeing you give us your consent. It is important that when you collect, store, process and potentially transfer (via Integrations or Exports) data from your own customers via a Malcolm! Workflow you have your customers consent to do this. Most companies handle this via provisions in their Privacy Policy and/or Terms and Conditions around data processing which their customers agree to. **It is therefore good practice to include a check box in your Workflows that reminds customers of your Privacy Policy and their continuing agreement of it and/or confirms their consent for you to collect and process their information** **Further Questions** If you have further questions about GDPR or wish to contact our Data Protection Officer [you can contact us here](https://malcolm.support/contact). [You can find out more about GDPR here. ](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/)