thread Re: Cannot Pair Readers in Archived Discussions (Read Only)

How can I give team members permission to app settings?

swendt — Fri, 06 Mar 2020 18:42:35 GMT

[The title of this thread has been edited from the original: Team Permissions]

I have users for a scout troop that have mobile access authorization. They used to be able to go to settings and then see the business info to verify they were in the right account. They no longer seem to have permission to do that or to get into the hardware section to pair a reader. There has been an update since last year when we all used the account. How do I give everyone access to that?

Re: Team Permissions

isabelle — Fri, 06 Mar 2020 18:37:08 GMT

Hey @swendt.

Thanks for posting in the Seller Community.

You should be able to make that adjustment from Permissions within the Team section of the Online Dashboard.

I believe the one you're looking for would be under the Account and Settings > Device area:

I hope this helps! Let me know if you have any questions about this.

How can I allow employees to pair reader to the POS device

Bodacious — Thu, 07 May 2020 15:38:41 GMT

The title of this thread has been edited from the original: Cannot Pair Readers

I use one POS system for my store. It was suggested to me to log into the POS using the store's email rather than my email as business owner. This limits the access to information on the POS for the employees. But now the store cannot pair with the new reader. What do I need to activate in the permission to allow to pair the new device?

Re: Cannot Pair Readers

JustinC — Thu, 07 May 2020 15:37:17 GMT

Sounds like you need to enable the Account & Settings > Configure hardware settings permission for their role under Team Permissions. This will allow them access into the Settings tab of the device and pair the reader.

@Bodacious

Re: Cannot Pair Readers

Bodacious — Fri, 08 May 2020 14:51:01 GMT

Thanks. I will give it a try!

Re: Cannot Pair Readers

Joe — Fri, 08 May 2020 14:58:31 GMT

Let us know if anything else comes up, @Bodacious!