<?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>thread Restricting access on device in Payments Troubleshooting</title>
    <link>https://community.squareup.com/t5/Payments-Troubleshooting/Restricting-access-on-device/m-p/659691#M40936</link>
    <description>&lt;P&gt;I am Treasurer for a small netball club, and so far have run a cash only canteen on match day.&lt;/P&gt;&lt;P&gt;We have a square reader and iPad with app that we use for uniform purchases, and are looking to expand this into the canteen.&lt;/P&gt;&lt;P&gt;We don't have set staff, but rather parents who volunteer at the tie slot their child is playing.&lt;/P&gt;&lt;P&gt;I want to be able to restrict access (The app is currently logged into with my log in, which access everything.&lt;/P&gt;&lt;P&gt;Ive looked at team permissions, but it seems it needs to be allocated to specific team members.&lt;/P&gt;&lt;P&gt;What I want to do is be able to "lock down" the app on the iPad so &lt;U&gt;anyone&lt;/U&gt; can use it, but only for selected types of transactions.&lt;/P&gt;&lt;P&gt;Any advice would be appreciated.&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;</description>
    <pubDate>Sun, 21 Sep 2025 07:35:02 GMT</pubDate>
    <dc:creator>Phil_J</dc:creator>
    <dc:date>2025-09-21T07:35:02Z</dc:date>
    <item>
      <title>Restricting access on device</title>
      <link>https://community.squareup.com/t5/Payments-Troubleshooting/Restricting-access-on-device/m-p/659691#M40936</link>
      <description>&lt;P&gt;I am Treasurer for a small netball club, and so far have run a cash only canteen on match day.&lt;/P&gt;&lt;P&gt;We have a square reader and iPad with app that we use for uniform purchases, and are looking to expand this into the canteen.&lt;/P&gt;&lt;P&gt;We don't have set staff, but rather parents who volunteer at the tie slot their child is playing.&lt;/P&gt;&lt;P&gt;I want to be able to restrict access (The app is currently logged into with my log in, which access everything.&lt;/P&gt;&lt;P&gt;Ive looked at team permissions, but it seems it needs to be allocated to specific team members.&lt;/P&gt;&lt;P&gt;What I want to do is be able to "lock down" the app on the iPad so &lt;U&gt;anyone&lt;/U&gt; can use it, but only for selected types of transactions.&lt;/P&gt;&lt;P&gt;Any advice would be appreciated.&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 07:35:02 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Payments-Troubleshooting/Restricting-access-on-device/m-p/659691#M40936</guid>
      <dc:creator>Phil_J</dc:creator>
      <dc:date>2025-09-21T07:35:02Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting access on device</title>
      <link>https://community.squareup.com/t5/Payments-Troubleshooting/Restricting-access-on-device/m-p/659958#M40937</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/608143"&gt;@Phil_J&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My understanding from when I was on the free plans is you get your 'owner permissions' - thats you, who can do anything. Then a 'Team Permissions' that applies to everyone else. It's not until you're on paid plans that you get to set up individual, customised permission sets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Perhaps set up one restrictive permission set, perhaps you only need to add one additional user also (which everyone shares).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 01:03:49 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Payments-Troubleshooting/Restricting-access-on-device/m-p/659958#M40937</guid>
      <dc:creator>lawnbrook</dc:creator>
      <dc:date>2023-05-17T01:03:49Z</dc:date>
    </item>
  </channel>
</rss>

