iSpring Cloud offers several sharing methods for a variety of file types. You can send a link to a presentation via email right from your iSpring Cloud account or put it on social media. Additionally, you can get your presentation playing on a website or blog. Simply copy and paste the HTML code to your page of choice from the Embed Code tab.
By default, all files in your iSpring Cloud account are public and can be viewed by anyone on the web.
You can grant public or private access to the files in your account right in the Sharing window. Just toggle the switch Link Access to OFF, if you want to restrict access to your content. Toggle it back to ON to remove the viewing restrictions.
You can distribute your content among viewers by sending them a direct link for a presentation. To do this, please follow the instructions below:
You can send the link to anyone over instant messenger or a community web site.
This feature allows you to share your spectacular content with your followers on Facebook, Twitter or LinkedIn.
Using the Share by Email option, you send not a presentation itself, but a link to it. An end user won't have to download it or install PowerPoint. Plus, this way you guarantee the safety of your source files.
To share a content item by email:
If there is a problem while sending emails, the system will notify you.
You can add interactivity to your webpage by embedding a media-rich presentation. Simply copy and paste the HTML code from iSpring Cloud.
Table 1. Embed Code Options
|Fit to window|
Select Fit to window, if you want your content matches the window size.
|Play embedded content automatically|
Check the Play embedded content automatically to start the content playback automatically. By default, the embedded content won't play automatically.
You can lock your files to be played back on selected domains. Type in one or several domains in the Trusted Domains text box. Click Save to apply the trusted domains info to the embed code.
Switch this setting if you want to replace the <iframe> tag with <script>. In this case the embedded content will be initialized only after the page where it is inserted loads.
<script> may not be supported by some editors.