Spiro Reports: Publishing and Embedding Views in Web Pages and Applications

Follow

Publishing Options

Spiro Reports offers a wide range of publishing options to enable easy distribution and collaboration. You can publish the reports and dashboards that you create in Spiro Reports as live embedded reports in your websites/webpages or share them as easy to access URLs. 

Salient Features

  • You can publish any data, reports or dashboards that you create in Spiro Reports.
  • You can embed your live reports and dashboards across Websites, Blogs and Applications for wider consumption.
  • You can generate easy to access standalone URLs (Permalinks), which can even be bookmarked, for accessing the reports and dashboards by your users.
  • You can set fine-grained permissions while publishing the reports to users, such that they would be allowed to do only the permitted operations, like read, write, export etc., when they access the reports published.
  • Any data or report or dashboard published when accessed by users, will always see the latest live version and nothing old

Embedding Views* in Web Pages, Web Applications and Blogs

Spiro Reports allows you to easily embed any view such as a table, report or dashboards in a website, web application, blog or an intranet page. You can embed views with a secured login (with login) or a private permalink (without login) or with public access. Users visiting the webpage will be able to see the latest live version of the view and any changes that you make to the view will automatically get reflected in the embedded version as well.

*We can help you set up views

1. What are the views that I can embed in my website/blog?

You can embed all the views such as tables, charts, pivots, tabular view, summary view, query tables and dashboards that you create using Spiro Reports. To embed a view created in Spiro Reports, you need to get the corresponding HTML code snippet generated for the view by Spiro Reports and paste them within the <body>...</body> HTML tags of the destination page.

2. What are the access modes available when embedding a report/dashboard?

The following are the three access models that you can choose while embedding a report/dashboard.

  1. Embedding with Secured Login (with login): This is the most secure mode of embedding a view. Only the users with whom you have shared the report will be able to view it upon logging into Spiro Reports.
  2. Embedding with Private permalink (without login): When this setting is selected Spiro Reports will generate an embed URL (within an iframe code) which will contain a big randomly generated private key (private link), making them secure and very hard (if not impossible) to guess. Users can view the embedded report without logging in to Spiro Reports. 
  3. Embedding with Public Access: In case you want your embedded report to be accessible to all the users who visit your web page and do not require any random key based link generation or logging into Spiro Reports, you can use this access mode.

3. What is the difference between the three embedding modes?

Embedding with secured login allows the highest level of security to the embedded view. When you embed the view with "Private Access with Login", then it would prompt for the users to login to Spiro Reports to access the embedded view. Also, only users to whom you have shared the view would be able to access the embedded view, on successful login. 

When you embed a report with "Private Access without Login", Spiro Reports will generate a private permalink making it secure and very hard to guess. Users need not login to Spiro Reports to view the embedded report. Although this is secure, the randomly generated key is not impossible to guess.

In case you want your embedded report to be accessible to all the users who visit your web page and do not require any random key based link generation or logging into Spiro Reports, you can use the public access mode.

 

Interested in Spiro for your team? Sign up for a demo today: spiro.ai/demo

Questions? Email [email protected]

 

Was this article helpful?
0 out of 0 found this helpful

Comments