Feature-requests

It is not feasible to use the solution and then have to manually download each of the meetings of a person who left the company.

It would help to improve the user experience and be better organized tl, dv: I wanted to propose an improvement. When it comes to managing and organizing recordings, it would be nice if, when you put a meeting in a folder, it disappeared from the “meetings” view

This can be easily tested by feeding the transcript into any LLM and asking for a summary - without template. The LLM will give a significantly better result. Seems like tldv runs on older LLM, please upgrade to a better one. Some of the mistaken summaries are fatal. It often combines different topics into one, giving a dangeriously misleading information.

saves me a great deal of time

if you add this feature to record my screen like Loom or Vimeo, I can then understand your pricing level for PRO and delete my VIMEO account because you will have a better feature than them

Hello, please add a function to change the speaker's name in the conference.

The folders seem pretty useless at this point of time. I think it should be a quick fix to add a few multi select options. To begin with, you could copy all the existing multiple select features on the meetings page to within a folder as well.

I have a list of meetings in Meetings & Folders. I want to be able to select multiple meetings from here and add them all at once to a folder. Now I have to do it 1 by 1.

Edit the transcript by hand to improve it's accuracy in places Optionally with an review-cum-approval process which would be especially useful if the meeting is about discussing terms between two parties

As a Business plan user utilizing the tl;dv API for my team's bot, I need the ability to selectively grant API access to specific meetings rather than all recordings. This would protect sensitive meeting content while still leveraging tl;dv's powerful API for workflow automation. Currently, API access provides visibility to all recordings a user can view, which creates privacy concerns when building custom integrations