Best Practices: Hyperlinking File Source Locations in Your Content

For some customers, connecting a 3rd party file storage integration like Google Drive or SharePoint may raise concerns with their IT teams. Similarly, you may not want to upload and store files natively on Simpplr.

If this is the case, as an alternative you can link the source of your file(s) within your content or even feed posts. This will redirect users to your file storage location in a new tab, where all their existing permissions to the file will remain intact.

If a user does not have permission to view a certain file, and you hyperlink that file in your content, this may lead to a poor user experience. Therefore we recommend only doing this with public files that everyone in your org has access to, especially when linking within a public site.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • Can you please clarify best practices regarding if a file should live in a page or feed post, or if it should live in the site files and be linked from there to a page?

    Comment actions Permalink
  • Hi Katrina. So what actually happens is when you attach a file from your computer to a piece of content, that file is getting housed in the site where the content lives. So if you go to the site dashboard, you'll see the files tab, where there will be a folder labeled "Content files". That's where your file lives. The same goes for "Feed files" when you attached a file to a feed post in that site. So when these files get uploaded to content, feed, etc., they are by default part of the collection of "Site files".

    Does that help?

    Comment actions Permalink

Please sign in to leave a comment.

Articles in this section

See more