<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sql on psLens</title><link>https://pslens.com/tags/sql/</link><description>Recent content in Sql on psLens</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pslens.com/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Who Can Access This PeopleSoft Component? The SQL, and the Gotchas</title><link>https://pslens.com/blog/who-can-access-this-peoplesoft-component/</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate><guid>https://pslens.com/blog/who-can-access-this-peoplesoft-component/</guid><description>&lt;p&gt;&amp;ldquo;Who can get to this component?&amp;rdquo; is one of the most common questions a PeopleSoft security administrator gets, and PeopleSoft has no delivered screen that answers it in one place. The data lives in three tables, and the joins are easy to get subtly wrong.&lt;/p&gt;
&lt;h2 id="the-security-chain"&gt;The Security Chain&lt;/h2&gt;
&lt;p&gt;PeopleSoft component access flows through a fixed chain:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;PSOPRDEFN&lt;/code&gt;&lt;/strong&gt; — user accounts&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;PSROLEUSER&lt;/code&gt;&lt;/strong&gt; — which roles each user holds&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;PSROLECLASS&lt;/code&gt;&lt;/strong&gt; — which permission lists each role carries&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;PSAUTHITEM&lt;/code&gt;&lt;/strong&gt; — what each permission list grants: menu, component, and page entries with their authorized actions&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A user can reach a component if &lt;em&gt;any&lt;/em&gt; permission list on &lt;em&gt;any&lt;/em&gt; of their roles has a &lt;code&gt;PSAUTHITEM&lt;/code&gt; row for it.&lt;/p&gt;</description></item></channel></rss>