Fluent Support User Restrictions
I have a site that uses CRM + Forms + Community + Support and want to restrict access to the support system portal to members only. What is the best way to do this?
Non-members will be email only support via a Form, members are assigned access to the community via a CRM trigger from Surecart Purchase.
I use the plugin "User Menus" to restrict access to different menu items based on role or logged in logged out state. I have my Tech Support Portal/Page set in my main header menu and restricted to "Logged In Users Only", so when they are logged into the Community portal if they visit the frontend of the website, they'll see this "Tech Support" option. If they aren't logged in, they don't see it. I've also added a link to the "User Menu" in the backend settings of FluentCommunity and added the link to the Tech Support Page there in the dropdown menu.
David Fore Good idea however I was looking for something internal in the Fluent group of products without adding another plug-in. Ideally, it's connected to or could be used by automations
You can use FCRM’s Conditional Display feature (Gutenberg block), which allows you to show or hide blocks based on contact tags.
For example, you could use a tag to indicate that support is active.
Then:
- Show the Fluent Support block when the contact has the tag.
- Create an alternative block for contacts who don’t have the tag, redirecting them to email instead.
It’s pretty straightforward. I’m sure you can get this working in just a few minutes :)
Jorge de los Reyes that makes a lot of sense.... no additional tools/plugins required.
Jorge de los Reyes but only if block editor - i need page level
Mark Whitby what do you mean by “page level”? 🤔
Jorge de los Reyes Page Level Access: Where a control is implimented on page e.g. /support, based on the access given by the tools. Often this is a membership plugin. That plugin 1st checks condition rgwn allows access: a page, a widget, a subdirectory, a menu item etc
For this site, currently a sale tags a purchaser (via CRM), and that tag allows access to the community spaces. I just wanted the same level of access to the support area. Members get tickets & support area, while the public get email-only support.
Mark Whitby That will probably be possible with Fluent Members once it’s released.
That said, while having page-level controls would certainly be handy, I’m not sure they’re really necessary for this use case.
With the current tools, you can simply have a single page (e.g. /support/) and conditionally display:
- The Fluent Support portal to logged-in users and/or users with a specific FCRM tag.
- A different block (e.g. a CTA to contact you by email) to everyone else.
We’ve implemented this setup on several sites, and it works fantastically well.
You can even control which products are available to specific users in Fluent Support’s product selector using hooks. So FCRM + Fluent Support alone should already cover what you’re trying to achieve.
If that’s still not enough and you’re looking for more granular, membership-like access control, then I’d probably just wait for Fluent Members rather than adding another layer to the stack.
Jorge de los Reyes I'm waiting for Fluent Members, which is why I won't use 3rd party plugin.
I use a pagebuilder so Gutenberg blocks are viable. I found that elementor has user role restrictions which is worth a try...
Thanks for the hints... will try to find a simple slution for now.