Bumping this post.  Has anyone figured this out yet?  I cannot seem to allow Privacy accessibility for any applications via config profile or the PPPC tool.

To resolve this issue do the following steps: Use logitech Options plus for this.

1. Install LogiOptions Plus
2. Grant all of the permissions manually in Accessibility/Input Settings
3. Go to Privacy & Security in system settings > Go to Accessibility or Input settings
4. Right click Logi Options+ > Click "Show in finder"
5. There you will find the true path of the componant of the application that the access is granted to
6. Drag that into PPPC utility, there you will see the actual name of "logioptionplus_agent"
7. Grant that Accessibility & Input monitoring
8. Upload to Jamf, and scope it to machines with Logitech Options+ installed

This will work as of Ventura 13.2.1 and should work on 13.0 onwards.

Hope that helps. 

You should have  2 different bundle id s here for approval with accessibility and input monitoring :

one for logi option + app :

com.logi.optionsplus
identifier "com.logi.optionsplus" 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] = "QED4VVPZWA"

There is daemon present in  library too  which has different bundle id 

com.logi.cp-dev-mgr
identifier "com.logi.cp-dev-mgr" 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] = QED4VVPZWA

We've tried granting accessibility to both the logi options plus and agent bundle ids but users still can't enable accessibility without admin prompts:

@Dobson From my experience (also known as known issue in jamf courses) what you see in the local GUI (PPPC) is not really correct. This means, that its shown as not enabled, but in reality it is enabled. I made this experience also with other tools and configuring PPPC for it.

The best way to find out if it is working is to testing. With LogiOptions+ no messages from enabling with admin are shown after installation and opening the tool are showing. 

I am actually in the same boat with logioptions+, so i will report if its working or not. 
From my side it looks that actually only 

com.logi.cp-dev-mgr
identifier "com.logi.cp-dev-mgr" 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] = QED4VVPZWA

is necessary, but i have to test again on fresh enrolled device to be sure.

From my side its working fine with only the one identifier 

com.logi.cp-dev-mgr
identifier "com.logi.cp-dev-mgr" 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] = QED4VVPZWA

for:

Input Monitoring - ListenEvent

Accessibility

Its shown as not enabled in Input Monitoring,

and not showing at all in accessibility

how i told before. The PPPC Configuration is working fine. No windows while installing for input monitoring and not window for admin while starting the app the first time for accessibility

Have you found a resolution to this yet? We are also attempting to add PPPC entries as you have listed here and while standard users are able to enable Input Monitoring without Admin credentials, they still cannot enable  Accessibility without being prompted.

I ran across this link trying to deploy a later instance of this software and I think I may have a solution for anyone who is running into trouble getting the accessibility to not prompt for an admin. 

It's an order of operations issue. The PPPC profile has to be in place before the application is installed.  Once the application puts the entitlement into accessibility during install it will be auto approved.