<?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 Re: how to &amp;quot;recycle&amp;quot; a passcode in Staff &amp; Payroll</title>
    <link>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/837465#M2898</link>
    <description>&lt;P&gt;After entering the proposed code &amp;amp; hitting "next", the page does not progress, and instead displays "&lt;SPAN&gt;This passcode has been taken."&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Mar 2026 21:47:29 GMT</pubDate>
    <dc:creator>Lynn_TRU</dc:creator>
    <dc:date>2026-03-05T21:47:29Z</dc:date>
    <item>
      <title>how to "recycle" a passcode</title>
      <link>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/834220#M2817</link>
      <description>&lt;P&gt;We have had quite a few volunteer cashiers move on, and I'm presently in the process of deactivating their accounts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order to **bleep** "now what was my code again?" questions in the bud, we're in the habit of letting our volunteer cashiers pick their own 4 digit passcode to unlock the register.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A quick test shows that should a new volunteer request a passcode that had previously been assigned to a prior cashier, that code may not be reassigned, &lt;STRONG&gt;even if the prior owner is deactivated&lt;/STRONG&gt;. Old data cluttering current data seems like a bug.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And, I haven't yet found a way to query who is assigned a passcode, to ascertain if it's assigned to an inactive cashier, in which case I could change it on the old inactive cashier so that the new cashier can use it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And, changing it on the old record entails 1) reactivating the record, 2) performing the change, and then 3) re-deactivating it. Clunky.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would help tremendously if the ability to query a passcode were added. It would also help if duplicate passcodes would be prevented only among &lt;STRONG&gt;active&lt;/STRONG&gt; records.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 22:01:04 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/834220#M2817</guid>
      <dc:creator>Lynn_TRU</dc:creator>
      <dc:date>2026-02-05T22:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: how to "recycle" a passcode</title>
      <link>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/834231#M2818</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/596173"&gt;@Lynn_TRU&lt;/a&gt;&amp;nbsp;What is the message/error you get when you try to set a passcode that is being used? Can you share that?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 22:44:15 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/834231#M2818</guid>
      <dc:creator>mitin</dc:creator>
      <dc:date>2026-02-05T22:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: how to "recycle" a passcode</title>
      <link>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/837465#M2898</link>
      <description>&lt;P&gt;After entering the proposed code &amp;amp; hitting "next", the page does not progress, and instead displays "&lt;SPAN&gt;This passcode has been taken."&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2026 21:47:29 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Staff-Payroll/how-to-quot-recycle-quot-a-passcode/m-p/837465#M2898</guid>
      <dc:creator>Lynn_TRU</dc:creator>
      <dc:date>2026-03-05T21:47:29Z</dc:date>
    </item>
  </channel>
</rss>

