<?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 Collaborating in DBSQL in Warehousing &amp; Analytics</title>
    <link>https://community.databricks.com/t5/warehousing-analytics/collaborating-in-dbsql/m-p/20101#M391</link>
    <description>&lt;P&gt;Are there workarounds that would allow multiple people to edit the same dashboard? I understand that "can edit" permission is on the roadmap but is there anything else they can do in the meantime to collaborate? Is it possible to disable access control completely in SQLA? Or should we recommend to login using a shared login such as&amp;nbsp;DBSQL@customer.com&amp;nbsp;?&lt;/P&gt;</description>
    <pubDate>Thu, 20 Mar 2025 16:59:59 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2025-03-20T16:59:59Z</dc:date>
    <item>
      <title>Collaborating in DBSQL</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/collaborating-in-dbsql/m-p/20101#M391</link>
      <description>&lt;P&gt;Are there workarounds that would allow multiple people to edit the same dashboard? I understand that "can edit" permission is on the roadmap but is there anything else they can do in the meantime to collaborate? Is it possible to disable access control completely in SQLA? Or should we recommend to login using a shared login such as&amp;nbsp;DBSQL@customer.com&amp;nbsp;?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 16:59:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/collaborating-in-dbsql/m-p/20101#M391</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-03-20T16:59:59Z</dc:date>
    </item>
  </channel>
</rss>

