
GoHighLevel Product Access Granted Trigger: Setup Guide (2026)
How to use the Product Access Granted trigger to welcome, tag and onboard every new course member the moment they get in, whichever way their access arrived.
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.
The GoHighLevel Product Access Granted trigger starts a workflow the moment a contact is given access to a specific course or membership product. It is the cleanest way to run onboarding that fires every time someone gets in, not just when they pay.
In this guide I cover what fires it, the filter you will actually use, how it differs from Offer Access Granted, a step-by-step setup, four recipes we deploy for Australian coaches and course creators, and how to test it without spamming real students.
| Trigger name | Product Access Granted |
| Where to find it | Workflow builder trigger list, in the Courses / Memberships group (or search "Product Access") |
| Fires when | A contact is granted access to a specific product (course) in Memberships |
| Main filter | The product (course) you choose from the dropdown; no filter means any product |
| Companion triggers | Product Access Removed, Product Completed, Offer Access Granted |
| Source | HighLevel Support Portal articles on the trigger and on granting course access via workflows |
What the Product Access Granted trigger actually does
In HighLevel Memberships, a product is the course you build under Memberships > Courses. An offer is the commercial wrapper you build under Memberships > Offers, and it attaches one or more products to a price or a free enrolment.
The Product Access Granted trigger listens at the product level. When a contact ends up with access to the course you selected, the workflow enrols them, regardless of which offer or method delivered that access.
That distinction matters more than it looks. If you sell the same course in three bundles, one product-level trigger replaces three offer-level workflows.
What fires the Product Access Granted trigger in GoHighLevel
HighLevel's own help documentation describes the trigger firing when a customer is granted access to a specific product. In practice, access reaches a contact through a handful of routes:
- Offer purchase — a contact buys or claims an offer that includes the product, through a funnel order form, checkout or the offer's own page.
- Manual grant — you or a team member assign the offer or product from the contact record or the Memberships members area.
- Workflow action — another workflow uses the grant-offer action (labelled "Membership Grant Offer" in older accounts and "Course Grant Offer" in newer HighLevel docs) to hand out access after a tag, form or payment.
- Integrations — an external tool or API call that grants access on your behalf.
Bulk imports of existing students are the grey area. I have not found HighLevel documentation that confirms imports fire the trigger, so test one imported contact before you migrate a whole list, or keep the workflow switched to draft during a migration and back-fill onboarding separately.
For the full background on building the courses themselves, start with our GoHighLevel memberships and courses setup guide.
Filters available on the trigger
The filter you will use every time is the product selector. HighLevel's support article walks through picking a specific course from the dropdown so the workflow only runs for that product.
Leave the filter empty and the trigger fires for any product access granted in the sub-account, so most accounts should filter by product and give each course its own onboarding voice.
Filter options in the trigger panel change between HighLevel releases, so check the "Add filters" dropdown in your own account. If you need finer targeting than product, add an If/Else condition straight after the trigger and branch on tags, custom fields or the contact's source.
Product Access Granted vs Offer Access Granted: which one to use
We covered the offer-level version in detail in our Offer Access Granted trigger setup guide. Here is how the two compare side by side.
| Question | Product Access Granted | Offer Access Granted |
|---|---|---|
| Listens to | A course (product) under Memberships > Courses | An offer under Memberships > Offers |
| Fires when the course is in several offers? | Yes, whichever offer delivered access | Only for the offer you selected |
| Best for | Course onboarding, login nudges, community invites | Purchase-specific messaging, bonuses, upsell paths, pricing tiers |
| Bundle with 3 courses | Can fire once per course in the bundle | Fires once for the bundle |
| Typical pairing | Product Access Removed, Product Completed | Offer Access Removed, payment triggers |
My rule of thumb: offer triggers talk about the purchase, product triggers talk about the learning. Receipts, bonus delivery and upsells belong on the offer. Logging in, first lesson and community belong on the product.
How to set up the Product Access Granted trigger step by step
Before you start, make sure the course is published and attached to at least one offer, and that you have a test contact using an email address you control.
- Go to Automation > Workflows and click Create Workflow, then Start from scratch.
- Click Add New Trigger and search for Product Access Granted.
- Give the trigger a clear name, for example "Course A – access granted".
- Click Add filters and select the product (course) this workflow should listen to.
- Save the trigger, then add your actions underneath (recipes below).
- In workflow Settings, decide whether contacts can re-enter. For a welcome sequence, usually leave re-entry off so a re-grant after a payment hiccup does not repeat it.
- Set the workflow time window and timezone to your audience. For Australian students, use the sub-account's AEST/AEDT timezone and avoid SMS outside reasonable hours.
- Publish, then test with your own contact before telling anyone it is live.
If you are newer to the builder, our walkthrough of GoHighLevel workflow triggers, actions and recipes explains waits, If/Else branches and goal events in more depth.
Offer triggers talk about the purchase. Product triggers talk about the learning. Keep them in their lanes and your onboarding stops contradicting itself.
Four Product Access Granted workflow recipes that work
These are the four patterns we build most often for membership clients. Each sits under a single Product Access Granted trigger filtered to one course.
1. Welcome email and SMS
- Send Email: "You're in – here's how to log in", with the Client Portal login link and a one-line tip on where to start.
- Wait 5 minutes.
- Send SMS: a short, friendly nudge pointing to the email, plus a reply-to-ask line so questions land in Conversations.
Keep the SMS plain and identify your business. Australian SMS rules under the Spam Act 2003 expect consent, sender identification and a way to opt out, so only text students who agreed to SMS at checkout.
2. Onboarding tag and pipeline stage
- Add Contact Tag:
course-a-enrolled. - Create or Update Opportunity: move the contact into a "Student Onboarding" pipeline at the "Access granted" stage.
- Internal Notification or Create Task: tell the coach to send a personal voice note within 24 hours.
The tag gives you a clean segment for broadcasts and reporting. The pipeline stage gives your team a visual board of who has been onboarded and who has gone quiet.
3. Community invite
- Wait 1 day so the student focuses on the course first.
- Send Email with your community invite link, or grant group access if your community is set up as a private group.
- Wait 2 days, then Send Email: "Introduce yourself in the community", with a prompt for their first post.
Communities are where retention lives. Our guide to building and monetising a GoHighLevel community covers private channels, gamification and paid groups.
4. Drip nudges if no login
- Wait 3 days.
- If/Else: check for a tag your lesson-level workflows add when the student starts (for example
course-a-started, applied by a Lesson Completed workflow on lesson one). - No branch: send a "Need a hand getting started?" email, wait 4 more days, then an SMS or a task for the coach to call.
- Yes branch: end the workflow quietly.
This is the recipe that saves refunds. Students who never log in in week one are the ones who ask for their money back in week three.
Testing the trigger without annoying real students
Create a test contact with your own email and mobile, then grant the offer that contains your course from the contact record. Open the workflow's Execution Logs and confirm the contact entered and each action ran.
If nothing happens, check three things in order:
- The workflow is published, not saved as draft.
- The product filter matches the exact course you granted, not a similarly named duplicate.
- Re-entry settings are not blocking a contact who already went through once.
When you are done, remove the test contact's access so it does not inflate your member counts. That removal will fire any Product Access Removed workflows too, which is a free way to test the off-boarding side.
For the official walkthrough, see HighLevel's support articles on the Product Access Granted workflow trigger and granting access to membership courses using workflows.
Where it sits in the full course lifecycle
If your course is sold on a recurring plan, pair this guide with our GoHighLevel subscription trigger guide so failed or cancelled payments revoke access cleanly and your onboarding never welcomes someone who has already churned.
Common mistakes to avoid
- Leaving the product filter empty, so every course in the sub-account sends the same welcome.
- Building identical welcome emails on both the offer and product triggers, so buyers get two "you're in" messages.
- Forgetting bundles: three product-level workflows can fire within seconds of one bundle purchase.
- Allowing re-entry on a welcome sequence, so a re-granted student starts onboarding from scratch.
- Sending SMS to students who never opted in, which is a compliance risk in Australia.
- Running a bulk student migration with the workflow published and no test on a single imported contact first.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
What is the Product Access Granted trigger in GoHighLevel?
It is a workflow trigger that starts a workflow when a contact is granted access to a specific product, meaning a course built under Memberships > Courses. You filter it to the course you care about so each course can run its own onboarding.
What is the difference between Product Access Granted and Offer Access Granted?
Product Access Granted listens to a course, so it fires whichever offer delivered access. Offer Access Granted listens to one offer, so it only fires when that specific offer is granted. Use the product trigger for learning and onboarding, and the offer trigger for purchase-specific messages and bonuses.
Does the trigger fire when I grant access manually?
Manual assignment from the contact record is one of the common ways access is granted, and it is the easiest way to test the trigger. Grant the offer containing your course to a test contact and check the workflow's execution logs to confirm it ran.
Can a workflow action fire the Product Access Granted trigger?
Yes, granting an offer through the workflow grant-offer action (Membership Grant Offer or Course Grant Offer, depending on your account) gives the contact access to the products in that offer. That access can then start any Product Access Granted workflow filtered to those products.
Will importing students fire the Product Access Granted trigger?
HighLevel's documentation does not clearly confirm how bulk imports behave, so test with one imported contact first. During a large migration, keep the onboarding workflow in draft and send a separate migration email instead.
Why is my Product Access Granted workflow not firing?
Check that the workflow is published, that the product filter matches the exact course you granted, and that re-entry settings are not blocking the contact. Then review the execution logs for your test contact.
How do I stop bundle buyers getting several welcome emails?
Either move the welcome email to an Offer Access Granted workflow for the bundle, or add waits and tag checks to each product workflow so only the first one sends the general welcome. Keep course-specific tips on the product workflows.








