​@ABaker 813353e southcountry 

Thanks for submitting your question Al! You can easily turn off the ability for Guest role users to submit tickets for events through the permission policy in the Events module. The active permission policy GLOBAL - GUEST ROLE PERMISSION in the screenshot below allows guest users and external requestors to log in and submit tickets for Events.
 

Archiving this policy will take those abilities away from guest users.

Please be aware that archiving the policy remove all permissions for ALL guest users for Events only. You have the ability to unarchive it from the Archive tab on the main permissions page. If you have any guest users you would like to still have permissions another policy will need to be created for that group of users. Your CSM can assist with this if you have any questions.

HI Lwoods, 

Thanks for the quick reply. This is different than what I ended up doing after confirming with tech support that it works. 

I ended up turning off the ‘remote support enabled switch. Would that serve the same purpose? 

I did the opposite of this article basically.

Also, how would I limit internal non-admins from booking events while allowing admins to still view, delete, and modify booked events? 

Thanks, 

Al

​@ABaker 813353e southcountry  Yes that would accomplish the same goal to remove the ability for anyone to submit tickets via remote ticketing. The beauty of iiQ is you can accomplish similar tasks in various ways.

For your non-admins are you referring to staff members? 

You can control the visibility of certain Ticket Types by iiQ role under Admin > Issues > Ticket Types. 

The other option is through permission policies to ensure the users you referenced has the correct level of access in the Events module.

Lwoods, 

Basically I was able to prevent external users from booking external events. Thans for confirming the way I did it will work. That is all set.

Next I want to prevent internal staff from booking events. But still want them to be able to at least view them afterwards. 

And Admin should continue to be able to view, edit and manager internal events. 

Thanks, 

Al