<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Multi tenants for one application]]></title><description><![CDATA[<p dir="auto">Hello, there's something I can't understand with the tenants, a priori when we create an application we have to provide it with a single tenant.</p>
<p dir="auto">So I'm wondering what's the point of passing a tenantId in the authorization url? Since apparently it doesn't take into account the tenant passed and systematically uses the tenant linked to the application.</p>
<p dir="auto">As a result, I can't quite grasp the usefulness of the tenants. Could you clarify this for me?</p>
<p dir="auto">Thank you</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2666/multi-tenants-for-one-application</link><generator>RSS for Node</generator><lastBuildDate>Wed, 16 Sep 2026 09:29:47 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/2666.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 30 Apr 2024 16:42:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Multi tenants for one application on Tue, 14 May 2024 17:58:13 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3003">@qwandery</a>,</p>
<pre><code>OR, perhaps a new concept is needed in FusionAuth -- "Organizations" if you will -- that allows for granting users with different permission sets inside the same Application.
</code></pre>
<p dir="auto">You should feel free to open up a feature request <a href="https://github.com/FusionAuth/fusionauth-issues/issues/new?assignees=&amp;labels=&amp;projects=&amp;template=feature_request.md" rel="nofollow ugc">here</a>.</p>
]]></description><link>https://fusionauth.io/community/forum/post/7261</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7261</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Tue, 14 May 2024 17:58:13 GMT</pubDate></item><item><title><![CDATA[Reply to Multi tenants for one application on Wed, 08 May 2024 17:25:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2990">@vandaele-seba</a> <a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2507">@mark-robustelli</a><br />
I agree that it seems non-intuitive. I'm building a B2B2C multi-tenant application; it's very awkward trying to shoehorn things in the other way around.</p>
<p dir="auto">In my case, we have user accounts that can exist in, and have different permissions to, different tenant instances of the same application. I'm planning to work around this by using API to creating a new instance of the application from a sort of hard-coded template every time I create a tenant, and creating duplicates of users in the same fashion. But it's certainly awkward, I wish there were a way to share Applications and Users across tenants.</p>
<p dir="auto">OR, perhaps a new concept is needed in FusionAuth -- "Organizations" if you will -- that allows for granting users with different permission sets inside the same Application.</p>
]]></description><link>https://fusionauth.io/community/forum/post/7243</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7243</guid><dc:creator><![CDATA[qwandery]]></dc:creator><pubDate>Wed, 08 May 2024 17:25:41 GMT</pubDate></item><item><title><![CDATA[Reply to Multi tenants for one application on Mon, 06 May 2024 20:54:08 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2990">@vandaele-seba</a> A tenant in FusionAuth is a named object that represents a discrete namespace for Users, Applications, and Groups. It is a way to separate Users, Applications, and Registrations into separate containers.  There is a <a href="https://fusionauth.io/docs/get-started/core-concepts/tenants" rel="nofollow ugc">diagram in the documentation</a> that may help.</p>
]]></description><link>https://fusionauth.io/community/forum/post/7231</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7231</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Mon, 06 May 2024 20:54:08 GMT</pubDate></item></channel></rss>