<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Least-Privilege on psLens</title><link>https://pslens.com/tags/least-privilege/</link><description>Recent content in Least-Privilege on psLens</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://pslens.com/tags/least-privilege/index.xml" rel="self" type="application/rss+xml"/><item><title>Reducing App Designer Access</title><link>https://pslens.com/docs/use-cases/reducing-app-designer-access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pslens.com/docs/use-cases/reducing-app-designer-access/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;Someone on the team needs to look something up in PeopleSoft. Maybe a business analyst is writing requirements and needs to see what fields are on a record. Maybe an auditor needs to understand how security is configured. Maybe a functional consultant needs to trace a component&amp;rsquo;s menu path.&lt;/p&gt;
&lt;p&gt;The default answer is: give them App Designer.&lt;/p&gt;
&lt;p&gt;This happens because App Designer is the only tool that lets you browse PeopleSoft object definitions. There is no read-only alternative built into PeopleSoft. So people who only need to look things up end up with the same tool that developers use to build and modify the application.&lt;/p&gt;</description></item></channel></rss>