<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/af095d47b5bc4cc8ae88dd970c99e9c3&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/af095d47b5bc4cc8ae88dd970c99e9c3-cc42acde4ca06de2.gif</thumbnail_url><duration>157.202</duration><title>Team Member Permissions and Spend Logs</title><description>In this Loom I explain how team member permissions affect access to spend logs across a theme. With the Member setting, I can see spend locks and spanlogs for the entire team, including logs created using the proxy admin key tied to the team. I log in as that user and show I only see the one log that was generated, while another team has none because we did not use their key. I also point out we can filter logs by team.</description></oembed>