Skip to main content
Solved

ClickShare puck, user unable to "Allow" screen recording.

  • April 25, 2025
  • 4 replies
  • 140 views
D
Forum|alt.badge.img+2

We are deploying ClickShare to all of our conference rooms and have run into an interesting deal.

Naturally, when the program starts from the puck, after plugging it in to the Mac, it needs to be allowed to record the screen.

For installed programs, I would just do a PPPC configuration policy.  But I can't get it working for this.

I have tried to get the Team Id, and it responds that the Clickshare. App on the puck is not a valid program.  I tried using Path (Which I have not used before), and that doesn't do the trick either.

I used the IDs on Barco support site, but that is for the installable app, and doesn't work for the puck app.

Has anyone come across this?


Thanks

Dave

Best answer by dona545mi

Hello,

What You Can Do:
1. Encourage Use of the Installed Version
Barco offers a full ClickShare Desktop App which can be deployed and managed like a normal application. This is the version that can be granted screen recording permissions using a PPPC profile, and it's more manageable overall.

Link (official site): https://www.barco.com/en/clickshare/app

If users install this version, it removes the need to rely on the puck’s auto-launch version.

2. Educate Users to Manually Grant Permission
If you must use the puck version:

Users will see the macOS prompt to allow screen recording the first time.

You’ll need to provide clear instructions or a support page on how to go to: System Settings > Privacy & Security > Screen Recording and check the box for “ClickShare”.

Note: The application needs to quit and relaunch after permission is granted.

3. Workarounds with Limited Success
Some admins have tried scripting or using tools like tccutil or tccplus, but these don’t work reliably with apps launched from USB volumes due to the sandboxing and SIP protections in macOS.

Why the PPPC Profile Fails : 
The puck launches the app from a volatile path (e.g., /Volumes/ClickShare/ClickShare.app) and doesn’t report a valid Team ID macOS accepts. This prevents MDM profiles from properly applying permissions.

 

Hope that useful.

 

Best regard,

Dona

    4 replies

    D
    Forum|alt.badge.img+11
    • daniel_behan
    • Valued Contributor
    • April 25, 2025

    Mine is working so far.

     

    Identifier: com.barco.clickshare

    Code Requirement: identifier "com.barco.clickshare" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P6CDJZR997

    Screen Capture, Allow Standard Users to Allow Access

    shrisivakumaran
    wakco11
    brandonharshe
    D
    Forum|alt.badge.img+2
    • dona545mi
    • New Contributor
    • Answer
    • April 30, 2025

    Hello,

    What You Can Do:
    1. Encourage Use of the Installed Version
    Barco offers a full ClickShare Desktop App which can be deployed and managed like a normal application. This is the version that can be granted screen recording permissions using a PPPC profile, and it's more manageable overall.

    Link (official site): https://www.barco.com/en/clickshare/app

    If users install this version, it removes the need to rely on the puck’s auto-launch version.

    2. Educate Users to Manually Grant Permission
    If you must use the puck version:

    Users will see the macOS prompt to allow screen recording the first time.

    You’ll need to provide clear instructions or a support page on how to go to: System Settings > Privacy & Security > Screen Recording and check the box for “ClickShare”.

    Note: The application needs to quit and relaunch after permission is granted.

    3. Workarounds with Limited Success
    Some admins have tried scripting or using tools like tccutil or tccplus, but these don’t work reliably with apps launched from USB volumes due to the sandboxing and SIP protections in macOS.

    Why the PPPC Profile Fails : 
    The puck launches the app from a volatile path (e.g., /Volumes/ClickShare/ClickShare.app) and doesn’t report a valid Team ID macOS accepts. This prevents MDM profiles from properly applying permissions.

     

    Hope that useful.

     

    Best regard,

    Dona

    e-zpassma
    D
    Forum|alt.badge.img+2
    • Doctor_K
    • Author
    • New Contributor
    • April 30, 2025

    Thanks @dona545mi, that was my fear, but I had to ask. :-)

    Thanks @daniel_behan those are the settings I had tried, and no-go.

     

     

    D
    Forum|alt.badge.img+11
    • daniel_behan
    • Valued Contributor
    • April 30, 2025

    Thanks @dona545mi, that was my fear, but I had to ask. :-)

    Thanks @daniel_behan those are the settings I had tried, and no-go.

     

     


    @Doctor_K I'm glad you found a solution that works for you.  I built my profile by dragging the clickshare app from the dongle into Jamf's PPPC Utility.  So far, so good.  I had the Desktop App @dona545mi mentioned in my Self Service catalog, but ultimately took it out because the firmware on the dongles was too outdated for the number of conference rooms we support.

    Terms & ConditionsCookie settingsAccessibility statement