<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Require User to be [Role]</title>
		<link>https://legacy.forums.gravityhelp.com/topic/require-user-to-be-role</link>
		<description>Gravity Support Forums Topic: Require User to be [Role]</description>
		<language>en-US</language>
		<pubDate>Thu, 16 Apr 2026 21:24:26 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/require-user-to-be-role" rel="self" type="application/rss+xml" />

		<item>
			<title>msd_lab on "Require User to be [Role]"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/require-user-to-be-role#post-346598</link>
			<pubDate>Wed, 26 Jun 2013 20:42:57 +0000</pubDate>
			<dc:creator>msd_lab</dc:creator>
			<guid isPermaLink="false">346598@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;That's some pretty sharp thinking there. Thanks, that does the trick.&#60;/p&#62;
&#60;p&#62;Next, to write a registration form that also allows for &#34;upgrading&#34; the user role. This same logic should do it.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Rob Harrell on "Require User to be [Role]"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/require-user-to-be-role#post-332259</link>
			<pubDate>Wed, 19 Jun 2013 12:21:47 +0000</pubDate>
			<dc:creator>Rob Harrell</dc:creator>
			<guid isPermaLink="false">332259@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;What if you used this: &#60;a href=&#34;http://gravitywiz.com/dynamically-populating-user-role/&#34; rel=&#34;nofollow&#34;&#62;http://gravitywiz.com/dynamically-populating-user-role/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;And then relied on conditional logic to show/hide fields/submit button, etc&#60;/p&#62;
&#60;p&#62;You could put all of your form fields under a section break and apply conditional logic to that section break to show or hide and then you could add an HTML field that shows via conditional logic if they don't have rights to use the form.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>msd_lab on "Require User to be [Role]"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/require-user-to-be-role#post-330507</link>
			<pubDate>Tue, 18 Jun 2013 14:44:59 +0000</pubDate>
			<dc:creator>msd_lab</dc:creator>
			<guid isPermaLink="false">330507@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I want to allow only logged in users of a certain role/capability to use a form. There is already &#34;Require user to be logged in&#34;. I was hoping there might be something as simple as a filter I can hook to.&#60;/p&#62;
&#60;p&#62;Any ideas? I know I can do it a trickier way, I was hoping to do it real smooth like, without a whole bunch of shortcode logic.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
