<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:goat="https://www.plan4better.de/ns/goat-changelog">
  <channel>
    <title>GOAT Changelog</title>
    <link>https://www.plan4better.de/en/goat/changelog/</link>
    <description>What changed in GOAT, and what it means for your work. New features, improvements and fixes, in plain language.</description>
    <language>en</language>
    <atom:link href="https://www.plan4better.de/en/goat/changelog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Closest-average heatmaps without a travel time limit</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#heatmap-closest-average-no-limit</link>
      <guid isPermaLink="false">heatmap-closest-average-no-limit</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>When you set a reference area in Heatmap - Closest Average, the travel cost limit no longer applies for walking, cycling, pedelec and car. Every cell gets its real average travel cost, however far away the destinations are.</description>
      <content:encoded><![CDATA[<p>When you set a <em>Reference area</em> in <em>Heatmap - Closest Average</em>, the travel cost <em>Limit</em> no longer applies for walking, cycling, pedelec and car. Destinations outside the area count too, and every cell gets its real average travel cost, however far away the destinations are. Cells that are not reached within a limit no longer drop out of the result.</p>
<p>Public transport still uses the <em>Limit</em>. A reference area can cover at most 200,000 cells for walking, cycling and pedelec, and 40,000 for car.</p>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.9</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#fixes-v3-0-9</link>
      <guid isPermaLink="false">fixes-v3-0-9</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Accepting an organization invitation.</description>
      <content:encoded><![CDATA[<ul>
<li>Accepting an invitation to an organization no longer keeps the roles you held before. You get the role you were invited with, and a user who already belongs to an organization can’t accept a second invitation.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Number fields that count up on their own, and unique IDs</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#serial-and-uuid-fields</link>
      <guid isPermaLink="false">serial-and-uuid-fields</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>Two new field types let GOAT fill in a value for every new feature, whether you draw it, add it in a table or create it in a batch. A serial field gives each feature the next running number, starting where you choose, and never hands out a number twice, even after a feature is deleted. A UUID field gives each feature a unique ID.</description>
      <content:encoded><![CDATA[<p>Two new field types let GOAT fill in a value for every new feature, whether you draw it,
add it in a table or create it in a batch. A serial field gives each feature the next
running number, starting where you choose, and never hands out a number twice, even after
a feature is deleted. A UUID field gives each feature a unique ID.</p>]]></content:encoded>
    </item>
    <item>
      <title>Templates can give every user their own copy of a dataset</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#template-dataset-copies</link>
      <guid isPermaLink="false">template-dataset-copies</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>When you save a template, you now choose for each dataset how the people who use it receive it. A dataset can still be shared read-only. It can also be copied, so that every user gets their own editable version, either with all its rows or empty, with only the fields, field settings and style.</description>
      <content:encoded><![CDATA[<p>When you save a template, you now choose for each dataset how the people who use it
receive it. A dataset can still be shared read-only. It can also be copied, so that every
user gets their own editable version, either with all its rows or empty, with only the
fields, field settings and style.</p>]]></content:encoded>
    </item>
    <item>
      <title>Shared templates show up under the space they were shared into</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#shared-templates-in-template-list</link>
      <guid isPermaLink="false">shared-templates-in-template-list</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>A template shared with your organization or team used to appear only under Everyone in the template list, while Content showed it in the organization space. The Organization and Team filters now find it too, and a new Shared with me source lists templates shared with you alone. This applies to workflow, layout and Home templates.</description>
      <content:encoded><![CDATA[<p>A template shared with your organization or team used to appear only under <em>Everyone</em> in
the template list, although <em>Content</em> showed it inside the organization space. The
<em>Organization</em> and <em>Team</em> filters now find it too, whether it was shared on the template
itself or on a folder above it.</p>
<p>A new source, <em>Shared with me</em>, lists templates that were shared with you alone. Each
template is listed under the space it was shared into. This works in the workflow, layout
and Home template pickers.</p>]]></content:encoded>
    </item>
    <item>
      <title>Zoom the workflow canvas out much further</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#workflow-canvas-zoom-out</link>
      <guid isPermaLink="false">workflow-canvas-zoom-out</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>The workflow canvas used to stop zooming out at half size, which is too close to see a large workflow as a whole. It now zooms out to a tenth.</description>
      <content:encoded><![CDATA[<p>The workflow canvas used to stop zooming out at half size, which is too close to see a
large workflow as a whole. It now zooms out to a tenth.</p>]]></content:encoded>
    </item>
    <item>
      <title>Workflow variables can have a label and a description</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#workflow-variable-labels</link>
      <guid isPermaLink="false">workflow-variable-labels</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>A workflow variable keeps its technical name for references such as {{@name}}. It can now also have a display label and a short description, so people who run your workflow see what each value is for.</description>
      <content:encoded><![CDATA[<p>A workflow variable keeps its technical name for references such as {{@name}}. It can now
also have a display label and a short description, so people who run your workflow see
what each value is for.</p>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.8</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#fixes-v3-0-8</link>
      <guid isPermaLink="false">fixes-v3-0-8</guid>
      <pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Copies and imports of projects with a Dashboard, empty layers, joins in workflows, shared templates, printed fonts, legend labels and German interface texts.</description>
      <content:encoded><![CDATA[<ul>
<li>Copying or importing a project no longer changes numbers in the Dashboard that only looked like layer IDs, such as shadow or opacity. These copies could not be opened before.</li>
<li>Dashboard interaction rules, such as visibility sync and tab switching, work in a copy or import of a project. They used to keep pointing at the original.</li>
<li>Blank lines in a Dashboard’s rich text are kept instead of disappearing.</li>
<li>The first run of a workflow in a copied project, or a project made from a template, keeps the description, tags and column settings of the layer it replaces.</li>
<li>An empty layer, such as one you draw your planning into, keeps its geometry through export and import. It can be shown again and used in workflows.</li>
<li>A custom SQL node no longer fails on an empty intermediate result when it uses spatial functions.</li>
<li>Stray bounding-box columns from older GOAT versions no longer show up in field lists or get carried into joins, SQL and tool results.</li>
<li>The workflow preview of a join lists the columns the run really writes, with the join_ prefix. A SQL node written against the preview no longer fails.</li>
<li>Using a template inside a project shows the layers it adds right away, without a reload.</li>
<li>Someone who may use a template that was shared through a folder can now read the datasets it ships. Projects made from it no longer miss those layers.</li>
<li>Sharing a template with a person, team or organization outside your own organization is refused before anything is saved.</li>
<li>In a print layout, Verdana, Garamond and Consolas print in fonts of similar width, so text wraps as it does in the editor.</li>
<li>Legend labels you edit in place wrap at spaces, so a title no longer pushes the last legend entry out of its box in print.</li>
<li>Opportunity inputs in workflow tools show a proper label as tooltip instead of a generated title.</li>
<li>More of the German interface is translated, and dates in the header, job list and time picker follow the language.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Ask for help and follow your support tickets inside GOAT</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#support-tickets</link>
      <guid isPermaLink="false">support-tickets</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>Open a support ticket from the support menu in the GOAT header, attach files, and follow the conversation inside GOAT. When our team replies, you get an email with a link back to the ticket.</description>
      <content:encoded><![CDATA[<p>You can now open a support ticket from the support menu in the GOAT header, attach
files, and follow the conversation inside GOAT. When our team replies, you get an email
with a link back to the ticket.</p>
<p>You can answer, mark a ticket as solved, reopen it, and rate the help you got. Owners and
admins of an organization see all of its tickets. The link to the documentation has moved
into the same menu.</p>]]></content:encoded>
    </item>
    <item>
      <title>See which steps of a workflow you cannot run, and why</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#workflow-refused-nodes</link>
      <guid isPermaLink="false">workflow-refused-nodes</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>When a workflow in a shared project uses datasets you are not allowed to read, the workflow editor now marks those nodes, names them, and suggests what to do, instead of only saying &quot;Resource not found&quot;.</description>
      <content:encoded><![CDATA[<p>In a shared project, a workflow can use datasets you are not allowed to read. Until now
the run failed with “Resource not found” and nothing more.</p>
<p>Now the workflow editor marks the affected nodes as failed, names them, and suggests what
to do: ask the owner to share the datasets, or use <em>Replace datasets…</em> to choose your own.</p>]]></content:encoded>
    </item>
    <item>
      <title>Workflow templates keep the style of their results</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#workflow-template-styles</link>
      <guid isPermaLink="false">workflow-template-styles</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>When you save a workflow as a template, GOAT now remembers how you styled each exported result, so anyone who uses the template gets the same colours and symbols on their first run.</description>
      <content:encoded><![CDATA[<p>When you save a workflow as a template, GOAT now remembers how you styled each exported
result. Anyone who uses the template gets the same colours and symbols on their first run,
instead of the tool’s default style.</p>
<p>Project templates already worked this way. An export that never ran before you saved the
template still uses the default style.</p>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.7</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#fixes-v3-0-7</link>
      <guid isPermaLink="false">fixes-v3-0-7</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Workflows on the default network run again, ÖV-Güteklassen use the main station, and project exports take their workflow datasets along.</description>
      <content:encoded><![CDATA[<ul>
<li>Workflows run again when their network is left on the default network.</li>
<li>ÖV-Güteklassen use the name and position of the main station, not of one of its platforms.</li>
<li>When you export a project, its workflows take along the datasets they use, as long as you can read them. A dataset you cannot read is left out, and the workflow asks for a new one after the import.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.6</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-10/#fixes-v3-0-6</link>
      <guid isPermaLink="false">fixes-v3-0-6</guid>
      <pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Custom basemaps, folder order, yes/no fields, datasets shared with a team or organization, the dataset upload and the Catalog's area filter.</description>
      <content:encoded><![CDATA[<ul>
<li>A project’s custom basemap now always shows when you open the project. You no longer briefly see the previous project’s basemap.</li>
<li>In a folder with many datasets, folders and projects are listed first instead of moving to later pages.</li>
<li>Styling and filtering by a yes/no field now works correctly.</li>
<li>Datasets shared with a team or organization now appear when you add a layer from that space, not only on the <em>Content</em> page.</li>
<li>Uploading a dataset is called <em>Upload dataset</em> everywhere, with the same icon.</li>
<li>Searching the Catalog with an area filter uses the exact shape of the area instead of a rectangle around it, so the results fit the area better.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.5</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#fixes-v3-0-5</link>
      <guid isPermaLink="false">fixes-v3-0-5</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Layer styles keep what you set, the data table stays readable while it loads, and dashboards handle long labels and cut-off names.</description>
      <content:encoded><![CDATA[<ul>
<li>Line layers have an opacity slider under <em>Color</em>, and an opacity of 0 is kept when you save.</li>
<li>Switching the colour palette keeps your custom break values.</li>
<li>Unsaved changes to a custom colour scale are kept when you switch <em>No data</em> on or off.</li>
<li>When you choose a field to size by, the size range starts at the current size instead of at 0.</li>
<li>The data table keeps the current page visible while the next one loads.</li>
<li>Long link labels in a dashboard’s <em>Links</em> widget wrap instead of running past the panel.</li>
<li>Where a name is cut off, the full name shows when you hover over it.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.4</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#fixes-v3-0-4</link>
      <guid isPermaLink="false">fixes-v3-0-4</guid>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>The scale bar shows full numbers, catchment areas in workflows fill in correctly, and Catalog search favours datasets for the area you are looking at.</description>
      <content:encoded><![CDATA[<ul>
<li>The scale bar shows full numbers instead of abbreviations with K and M.</li>
<li>In a workflow, a catchment area with several starting points from a previous step now fills in its input correctly.</li>
<li>Catalog search gives more weight to datasets that cover the area you are looking at.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Know which starting point each catchment area belongs to</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#catchment-area-origin</link>
      <guid isPermaLink="false">catchment-area-origin</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>Separate catchment areas for several starting points now carry an origin field, so you can tell which starting point each area comes from and label, filter or style the areas by it.</description>
      <content:encoded><![CDATA[<p>When you calculate separate catchment areas for several starting points, each area now
has an origin field that says which starting point it comes from. You can label, filter or
style the areas by it.</p>]]></content:encoded>
    </item>
    <item>
      <title>Fixes in v3.0.3</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#fixes-v3-0-3</link>
      <guid isPermaLink="false">fixes-v3-0-3</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <category>fixed</category>
      <description>Catalog text search finds datasets more reliably, the Join tool handles large datasets, and tools no longer add extra columns to their results.</description>
      <content:encoded><![CDATA[<ul>
<li>Catalog text search finds datasets more reliably.</li>
<li>The Join tool is faster and handles large datasets without running out of memory.</li>
<li>Tools no longer add extra bounding-box columns to their results.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Run accessibility analyses on a network you bring yourself</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#custom-routing-networks</link>
      <guid isPermaLink="false">custom-routing-networks</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>Until now, accessibility analyses ran on the routing networks we provide, which also set the limits of where GOAT could be used. In v3 you upload your own network and the analyses run on that. Take Fukushima: we provide no network there, so the indicators had nothing to run on. Upload the street network and a Catchment Area works the way it does in Munich, and bringing the GTFS data does the same for public transport. That covers most of the world, and local cases too: a planned cycle network, or a campus network missing from OpenStreetMap.</description>
      <content:encoded><![CDATA[<p>Until now, accessibility analyses ran on the routing networks we provide, and that also
set the limits of where GOAT could be used. In v3 you upload your own network and the
analyses run on that.</p>
<p>Take Fukushima. We do not provide a routing network there, so the accessibility indicators
had nothing to run on. Upload the street network and a Catchment Area works the way it
does in Munich. The same holds for public transport: bring the GTFS data for the region
and the transit indicators run on it.</p>
<p>That covers two different situations. One is geographic, everywhere we do not already
cover, which is most of the world. The other is local: a planned cycle network that does
not exist yet, a campus network that is not in OpenStreetMap, or a national dataset a
planning office trusts more than the open one. The network arrives in the Overture format,
a .zip containing <code>segments.geoparquet</code> and <code>connectors.geoparquet</code>.</p>]]></content:encoded>
      <media:content url="https://www.plan4better.de/_astro/04-catchment-uploaded-network.CHs9KgkB_hOdq0.webp" medium="image" type="image/webp" />
      <media:thumbnail url="https://www.plan4better.de/_astro/04-catchment-uploaded-network.CHs9KgkB_hOdq0.webp" />
    </item>
    <item>
      <title>A Home screen that picks up where you left off</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#home</link>
      <guid isPermaLink="false">home</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>Opening GOAT now starts on a Home screen instead of dropping you straight into an empty map. One box searches the whole workspace, and a new project, a dataset and the Catalog are all within reach. Underneath, Jump back in lists the projects you had open most recently, and Start from a template offers the workflow, dashboard and layout templates.</description>
      <content:encoded><![CDATA[<p>Opening GOAT now starts on a Home screen instead of dropping you straight into an empty
map.</p>
<p>It searches the whole workspace from one box, and puts the three things you are most
likely to want next in reach: a new project, a dataset, or the Catalog. Underneath, Jump
back in lists the projects you had open most recently, and Start from a template offers
the workflow, dashboard and layout templates.</p>
<p>Links to the getting-started guide, the documentation and a short isochrones video sit on
the same screen, so the first hour with GOAT does not depend on knowing where to look.</p>]]></content:encoded>
      <media:content url="https://www.plan4better.de/_astro/hero-welcome.CBUEJHn6_Z20pN7F.webp" medium="image" type="image/webp" />
      <media:thumbnail url="https://www.plan4better.de/_astro/hero-welcome.CBUEJHn6_Z20pN7F.webp" />
    </item>
    <item>
      <title>Start from a template instead of an empty map</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#templates</link>
      <guid isPermaLink="false">templates</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <category>new</category>
      <description>An empty map is a bad place to start. v3 adds templates at three levels: a project template opens a prepared project with styled layers, finished analyses and a built Dashboard; a workflow template is a prepared analysis where the only thing missing is your data; and a layout template is a print-ready map you do not have to design from scratch. Workflows and Layouts can now be added from inside a project.</description>
      <content:encoded><![CDATA[<p>An empty map is a bad place to start, especially in your first hour with a new tool.
v3 adds templates at three levels.</p>
<p>A project template opens a prepared project: the layers are styled, the analyses have
been run and the Dashboard is built, so you can see how results are meant to be read as
well as how they were produced. A workflow template is a prepared analysis where the only
thing missing is your data, so ÖV-Güteklassen for your region does not mean building the
chain of steps yourself. A layout template is a print-ready map you do not have to design
from scratch.</p>
<p>Workflows and Layouts can now be added from inside a project, rather than being separate
places you go to.</p>]]></content:encoded>
      <media:content url="https://www.plan4better.de/_astro/02-workflow-template.CHkjfeVR_ZfNi3X.webp" medium="image" type="image/webp" />
      <media:thumbnail url="https://www.plan4better.de/_astro/02-workflow-template.CHkjfeVR_ZfNi3X.webp" />
    </item>
    <item>
      <title>Search more than 30,000 datasets in the Catalog</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#catalog</link>
      <guid isPermaLink="false">catalog</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>Until v3 the Catalog held around 60 datasets, each one found and added by hand. It now holds more than 30,000, collected from national, regional and municipal open data portals across Europe, plus Overture Maps and OpenStreetMap. Search it, filter by area, topic and data type, and add a dataset to your project without downloading or reprojecting anything.</description>
      <content:encoded><![CDATA[<p>Until v3 the Catalog held around 60 datasets, each one found, checked and added by
hand. It now holds more than 30,000.</p>
<p>They are no longer added one at a time. GOAT collects from public geodata catalogs
instead: national open data portals across Europe, regional and municipal portals,
Overture Maps and OpenStreetMap. Everything lands in one index, so a dataset from a
German state portal and a layer from Overture are described the same way and can be
found the same way.</p>
<p>What changes is the first step of a project. Search the Catalog, filter by area, by
topic and by data type, and add the dataset to your project. No download, no
reprojection, no cleaning.</p>]]></content:encoded>
      <media:content url="https://www.plan4better.de/_astro/05-catalog.D-p5vvYM_Zp55a8.webp" medium="image" type="image/webp" />
      <media:thumbnail url="https://www.plan4better.de/_astro/05-catalog.D-p5vvYM_Zp55a8.webp" />
      <goat:spotlight>
        <goat:headline>More than 30,000 datasets</goat:headline>
        <goat:image>https://www.plan4better.de/_astro/05-catalog.D-p5vvYM_Zp55a8.webp</goat:image>
        <goat:url>https://www.plan4better.de/en/post/goat-v3-data-catalog-templates-custom-routing-networks/</goat:url>
      </goat:spotlight>
    </item>
    <item>
      <title>Projects, templates and datasets in one place</title>
      <link>https://www.plan4better.de/en/goat/changelog/2026-09/#content-management</link>
      <guid isPermaLink="false">content-management</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <category>enhancement</category>
      <description>Layers, datasets and projects are organised differently now, and the point of the rebuild was to make moving through them easy. Drag and drop to move things, put folders inside folders, and select several items at once. More importantly, everything is in one view: Projects, Templates, Datasets, Bundles and Folders sit together and you filter by type. Sharing works across all of it, and ownership of an item can be transferred.</description>
      <content:encoded><![CDATA[<p>Layers, datasets and projects are organised differently now, and the point of the
rebuild was to make moving through them easy. Drag and drop to move things, put folders
inside folders, and select several items at once to move or delete them together.</p>
<p>More importantly, everything is in one view. Projects, Templates, Datasets, Bundles and
Folders sit together and you filter by type to see only what you want. That makes one
question much easier to answer than it used to be: which data is connected to which
project.</p>
<p>Sharing works across all of it now, not only on projects, and ownership of an item can be
transferred to someone else. Useful when a colleague leaves, or when a project moves from
the person who built it to the team that runs it.</p>]]></content:encoded>
      <media:content url="https://www.plan4better.de/_astro/03-content-space.B-g2pG3A_jzhdB.webp" medium="image" type="image/webp" />
      <media:thumbnail url="https://www.plan4better.de/_astro/03-content-space.B-g2pG3A_jzhdB.webp" />
    </item>
  </channel>
</rss>
