Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Regional Manager Roles | Event Espresso - Staging Server
I have Permissions Pro 2.0.5 and have created several “Regional Managers” for difference Locales/Regions. They can log in and view their events, but they aren’t able to export the Attendee information like you can as a main admin user. When the Regional Manager clicks “Export to Excel” and opens the spreadsheet, it says ” No participant data has been collected.”
But when I go to that same event through my admin account and Export to Excel, it gives me a complete spreadsheet with all the attendee information.
Is it possible for a Regional Manager to accurately export attendee information?
Hmm… Well, they currently have access to the events created by the admin that are assigned to their locale. They just can’t export the attendee data. But they are definitely able to view, and even edit, the event information for their locale (even though the events were created by Admin account).
I just tested it by created two new “test” Regional Manager accounts assigned to the same locale.
Test Manager #1 created an event assigned to the locale. And both Test Manager #1 and Test Manager #2 can view the event and registration info, but can’t export attendees to excel. However, when I log in using my main Admin account, I can view the event that was created by Test Manager #1 and I can also export the attendee information to excel and view that information.
So, my question is, is there any possible way for a Regional Manager to be able to export their event attendee information as an excel document?
The support post ‘Regional Manager Roles’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.