Reporting Features
This page describes the options available to both the authors and readers of reports in your Kyso team..
A Kyso Report

Jupyter notebook to Kyso report

If a report has been published to a specific channel, anyone subscribed to the channel can read it, comment and discuss the results.
It looks very much like a Google Doc or Confluence page, with all interactive graphics rendering nicely - essentially anything with a JavaScript kernel running in the backend will work. For example:
  • plotly
  • bokeh
  • altair
Remember that this is a notebook that has gone through Kyso's renderer:
  • The code is hidden by default.
  • But if another technical member of the team wants to see how a particular output or graph was generated they can reveal the code under 'Show Code' in the top right-hand corner above the report.
  • Either option here can be made the default for any report, depending on who the intended audience for that report is.

File Browsing

Readers can browse through the different files attached to the report.
Note that, by default, all files within a repository are imported into Kyso. To ensure certain files are not included in the import (example: images, data files, etc,) add a .kysoignore file to the directory and Kyso will not import those files.
You can have as many notebooks within this project as you like - if a project report spans multiple notebooks for whatever reason. And you'll be able to specify a TOC.


For both Git-based projects and reports published using the Kyso CLI, any new commits made will be reflected here.
  • So all changes are tracked and maintained.
  • Users can view previous versions of the report here.
So this means that analyses/research is always up to date and the project's lifecycle is maintained.