🚀 Dashboard

data is everything. I believe that a revamped dashboard would allow us to better visualize and understand our client’s data. This would give us a more accurate and up-to-date snapshot of where the business is at, which would help us make better decisions.

  • Data visualizations of the information in our different apps. This would make it easier to see trends and patterns in our data.
  • The ability to filter and drill down into the data. This would allow us to get more granular insights into our data.

Do you have a mockup of what something like this could look like?

Hi @bettypublico,

thanks for the feature request! Dashboards are currently one of the top priorities on our roadmap and have already been mentioned to us by several partners and users.
We will have a dedicated app type dashboard, so you can build and use dashboards as you like e.g. as a home page for a workspace or as a management overview in an extra workspace.
I would also be very interested in a mockup or screenshot so I can check that we meet all your requirements.

Thanks again and best regards

1 Like

Excited to hear about the incoming dashboards. I’d love for them to basically be calculation fields on steroids with the flexibility to pull data from anywhere and display it using the existing HTML/Javascript tools. An example use case:

(1) An HR workspace that includes an app for Personnel records and an app for Leave Request records. Personnel records would have some unique identifier such as a relationship field to a user/guest or a field containing the user’s/guest’s email address. The Leave Request app would have a relationship field to the Personnel record.

(2) A travel workspace with an app for Trips/Events, an app for Attendees, and an app for Reimbursements. Attendees would have a unique relationship field to Personnel and a unique relationship field to Trips/Events. Reimbursements would relate back to an Attendee record.

(3) Finally, a theoretical “You” workspace dedicated to displaying/summarizing the data unique to the logged-in user via “dashboards”. One dashboard app could find a record in the Personnel app that ties to the logged-in user, grab all related items from the Leave app, and show both individualized summaries (e.g. 70 hours of annual leave available, total 270 hours of annual leave accrued, total 170 hours of annual leave used, total 30 hours of annual leave planned) and a detail table (all leave requests in a table showing date, type, approval status, and # of hours). Another dashboard app could do something similar with Trips/Events and Reimbursements–a detail table of all trips/events that the logged-in user was involved in via Personnel–>Attendees including the status and amounts of any of their Reimbursement records tied to that Trip/Event, and summaries that show total $$$ reimbursed, total $$$ pending reimbursements. etc.

Hope that all made sense.


Hello @nnsc,

great to meet you and a warm welcome to our community! :grinning:

All your use cases for dashboards make 100% sense and are extremely valuable for us in the requirements analysis of how we implement the dashboards in detail.

I can already confirm that our ideas and considerations go very much in the direction you would like to see. After we have the basic canvas with the drag and drop grid and all the basiccs so far, we want to create a code block as one of the first dashboard blocks in which the users can generate very powerful reports with JavaScript.
With conditional display of blocks or an active user variable, which we are planning in a further step, we could then implement the “You” dashboard. However, this would also be possible with the current permission system with several dashboard apps in which only the respective user has access.

If you have more ideas or use cases then please write us here anytime. The more real use cases we have from our users the better the feature will be in the end!

Cheers and thanks again for your insights

1 Like

Hi there!
Excited to hear about the dashboard feature coming, too! We are also interested in this for our ticket system. To give you an example:
(1) I have workspaces I share with all customers and a Ticket app
(2) Automatization copies the Ticket in an internal pool system where I can assign a team, team member ect.
(3) To manage the tickets, the tables are totally enough, but to give me a total overview of # of incoming tickets per week, # of (still) open tickets per week etc. the dashboard would be useful

Same goes for avg. response time, avg. closing time etc.

1 Like

Hi @joschkalang,

great use case for tape and especially for the planned dashboards to make the overview of open tickets even better. We will also consider your use case directly during the implementation.

One more question, have you already tested the split by function in the views for a date field and calendar week for your use case? With this you could already get a very good overview with the filters. The average closing time you could evaluate with the table calculations over all tickets and automatically determine per ticket with the calculation field.

If you want to use these functions and you need support then write us anytime here.

Best regards