· Other
· None of the above
· Other
How do I connect multiple Tidal accounts (family plan) to my Rune profiles? I'll need to cancel my subscription if this feature doesn't exist. Thanks!
Custom
Hello @0xd !
At this exact moment you cannot connect more than one Tidal account to Roon server.
Can you please clarify what are you trying to achieve and we’ll let you know about possible ways to get it ?
Regards.
Hi @0xd,
We haven’t seen a response to this thread yet. If you can elaborate on your intentions and provide a little more context, we can probably suggest a solution or workaround that might work for you.
We’ll watch for your reply. Thank you.
Thanks for the reply! I’m looking for a settings page where each profile can input their own Tidal credentials. With the current design, all API calls are happening on a single account so our history, suggestions, and favorites all get comingled. This seems like a really simple win so I was surprised when I couldn’t find an option to handle family plans. Let me know if I missed something obvious.
Don’t know if obvious 
Hello @0xd
Thank you for the update.
Please feel free to vote for the feature request provided by @Suedkiez to prioritize this feature for the review of the product team.
I voted but I’m a little skeptical about the whole process after reading through the entire thread started almost a decade ago. Can an engineer chime in and let us know if this is a limitation of the Tidal API? If it isn’t, this functionality seems far simpler to implement than the vast majority of feature requests. Is there a review process that determines how feasible a feature request actually is or is this just purely voter based?
If this is the final resolution to my support request, this effectively and unfortunately ends my ability to continue using Roon. I require an interface the entire family can use.
Hello @0xd
Thank you for your feedback and for taking the time to vote on the feature request.
To clarify: this is not a bug, and there is no engineering issue preventing normal operation of Roon as designed. Because of that, our engineers will not be providing a technical breakdown in the support thread.
Feature requests are not handled through the support channel. They are evaluated separately by our product and development teams, and prioritization is based primarily on overall user interest and demand, not on the technical difficulty or simplicity of implementation. Some seemingly simple requests have wide-ranging implications for the user experience, metadata systems, or partner integrations, while more complex ones may align better with long-term product direction.
If a feature receives strong community interest, it will be reviewed internally and considered for inclusion in a future release. If it does not, it may remain unimplemented.
We understand that every user has specific needs, and we genuinely appreciate you sharing yours. Your vote ensures that your use case is represented in our evaluation process.
If you have any further questions about your current setup, we’re here to help.
Thanks for the follow-up. I went ahead and canceled my Roon subscription and made a note of the reasoning. Hopefully that holds more weight than the voting system. I appreciate the time the support staff have taken with replies and hopefully someone on the team can get this simple feature into the pipeline. Roon’s ability to play my lossless purchases is great but the UI, artist data, knowledge graph and streaming service abstractions are the main reasons to pay for Roon in the age of lossless streaming.