Skip to content
  • There are no suggestions because the search field is empty.

Managing Requests for Places Accounts

How to review, approve, or deny event requests from providers as a Location manager — including the menu where requests appear and how to write a helpful denial.

 📍 This article is for Locations. 

One of the core benefits of a CEU Events Location account is the ability to review event requests from providers your Places admin has approved. As a Location manager, you decide which requests become events on your Location's calendar. This article walks you through where to find requests and the actions you can take on each one.

Before you begin
  • You need an active Location account to view and manage requests. If you haven't activated yet, see Activating Your Location Account.
  • Only approved providers can submit requests to your Location. Your Places admin controls who's on the approved list. If you're seeing requests from unexpected providers — or not seeing them from providers you expected — talk to your Places admin. See Approving Providers.
  • Every requested course has been reviewed and recognized by CEU Events. Providers can only submit requests for courses that have cleared CEU Events review, so credits will count for state licenses and association memberships.
How to view your requests
  1. Sign in to www.ceuevents.com with your Location account credentials.
  2. Click the Requests menu.
  3. Review the list of incoming requests for your Location, including date, time, course, and provider details.

From here, you can take one of two actions on each request: approve or deny.

Approving a request

Approving a request signals to the provider that you agree to the event details as submitted.

When you approve:

  • The request becomes an event on your Location's calendar.
  • The instructor is notified that the event is confirmed and can begin promoting it and inviting attendees.
  • You can access the event going forward under the Events menu in your Location account.

💡 Tip: Before approving, double-check the date, time, and any logistical details (expected attendance, room or space requirements, AV setup). Approving a request commits your Location to hosting — re-scheduling or canceling after approval requires coordinating with the provider and instructor directly.

Denying a request

If a request doesn't work for your Location, deny it with a clear, constructive reason. A good denial helps the provider re-request in a way that has a better chance of working.

When you deny a request:

  • Provide detailed information on the reason. Vague denials ("doesn't work for us") leave providers guessing and often produce a near-identical re-request.
  • Suggest an alternative if possible. If the issue is timing or capacity, propose what would work instead.

💡 Tip — example denial: "This date and time won't work for us, but if you request DD/MM/YY at HH:MM, we'll be able to accommodate you." This tone — acknowledging the request, naming the obstacle, suggesting a path forward — turns a denial into the start of a productive conversation rather than a dead end.

What happens next
  • Approved requests appear as events under your Events menu, where you'll manage them through the run-up to event day.
  • You'll get instant access to the event's invitation link, which you can forward to your employees or anyone else you'd like to invite. See Retrieve an Event Invitation Page URL.
  • The provider and instructor are notified automatically — you don't need to message them separately about an approval.
  • Denied requests are returned to the provider with your reason. They can revise and resubmit, or move on.
  • You'll receive new requests as approved providers submit them. There's no fixed cadence; requests come in whenever a provider's instructor wants to schedule at your Location.
Best practices
  • Review requests promptly. Providers and their instructors need lead time to plan, promote, and invite attendees. Sitting on a request slows their planning and may cost the event participants.
  • Always include a reason when denying. It costs you a sentence and saves the provider a duplicate request.
  • Suggest alternatives whenever you can. A denial with a counter-offer is far more productive than a denial alone.
  • Check the calendar before approving. Don't double-book your space, and confirm the timing works for any internal staff, AV setup, or building access requirements.
  • Coordinate with your Places admin if you see unexpected gaps or surprises — whether that's requests from unfamiliar providers, no requests at all, or a request that conflicts with broader Place policy.
  • Communicate special requirements directly with the provider. The Requests menu handles the approve/deny decision; logistical details like load-in time, parking, or AV are best handled in a quick message or call after approval.

Troubleshooting

  • You don't see the Requests menu. Confirm you're signed in as the Location manager with an activated account. If you haven't activated yet, see Activating Your Location Account.
  • You're not receiving any requests. Two common reasons: your Places admin hasn't approved providers yet (no one can request at your Location until they do), or approved providers don't have instructors actively scheduling. Check with your Places admin to confirm the approval list is set up.
  • You see a request from a provider you don't recognize. Your Places admin controls the approved provider list. Coordinate with them to confirm the provider should have access, or to remove them if they shouldn't.
  • You need to change or cancel a request after approving. Approving turns the request into an event, so changes need to be coordinated with the provider and instructor directly. For significant changes, contact CEU Events support.
  • A provider is asking why their request was denied. They can see the reason you provided when denying. If they're asking for more detail, respond to them directly — the platform doesn't relay follow-up messages.
  • Still have questions? Contact CEU Events support and we'll help.
Report an issue with this article