<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Multi-tenancy In Workato in Workato Embedded Discussion</title>
    <link>https://systematic.workato.com/t5/workato-embedded-discussion/multi-tenancy-in-workato/m-p/8938#M106</link>
    <description>&lt;P&gt;Does workato support multi-tenancy when we embed the platform into our webapp which is multitenant? We want granular access control where one customer can't see integrations/configurations of other customer and within the same customer also we should be able to manage by who can create a connection VS who can view it. Is this possible?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Feb 2025 14:06:30 GMT</pubDate>
    <dc:creator>ronak1308</dc:creator>
    <dc:date>2025-02-18T14:06:30Z</dc:date>
    <item>
      <title>Multi-tenancy In Workato</title>
      <link>https://systematic.workato.com/t5/workato-embedded-discussion/multi-tenancy-in-workato/m-p/8938#M106</link>
      <description>&lt;P&gt;Does workato support multi-tenancy when we embed the platform into our webapp which is multitenant? We want granular access control where one customer can't see integrations/configurations of other customer and within the same customer also we should be able to manage by who can create a connection VS who can view it. Is this possible?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2025 14:06:30 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-embedded-discussion/multi-tenancy-in-workato/m-p/8938#M106</guid>
      <dc:creator>ronak1308</dc:creator>
      <dc:date>2025-02-18T14:06:30Z</dc:date>
    </item>
  </channel>
</rss>

