Reducing App Designer Access
Categories:
The Problem
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’s menu path.
The default answer is: give them App Designer.
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.
What App Designer Access Actually Grants
App Designer is a full development environment. When you give someone App Designer access, you are giving them the ability to:
- Open and modify any object definition: records, pages, components, Application Engine programs, PeopleCode, and more
- View all PeopleCode source across the entire application
- Use SQL Editor to run arbitrary queries directly against the database
- Create and migrate projects between environments
- Connect directly to the database. App Designer requires a two-tier connection, which means the user’s workstation has network-level access to the database server.
- Require specialized infrastructure. Because of the two-tier connectivity requirement, organizations often provision dedicated virtual machines or terminal servers just so users can run App Designer. That is additional infrastructure to maintain, patch, and secure, all so someone can look something up.
And critically: App Designer activity is difficult to audit. There is no built-in log of which objects a user opened, viewed, or modified through the tool. You are trusting that users will only do what they are supposed to do, with no way to verify.
The Principle of Least Privilege
Least privilege is straightforward: give people the minimum access they need to do their job. If someone needs to look up a record definition, they should not need a tool that can also modify that record, run SQL against the database, and view every line of PeopleCode in the system.
This is not a theoretical concern. Internal and external auditors (SOX, SOC 2, and others) increasingly ask about developer tool access:
- Who has App Designer access?
- Why do they have it?
- What controls exist to prevent misuse?
When the answer is “they have it because they need to look things up and there is no other way,” that is a gap psLens removes by giving the same researchers a read-only browser UI with no SQL, no PeopleCode write access, and no database connection.
How psLens Compares
| Capability | App Designer | psLens |
|---|---|---|
| View object definitions | Yes (plus can modify) | Yes (read-only) |
| View PeopleCode source | Yes | Yes (read-only) |
| Modify PeopleSoft objects | Yes | No, by design |
| Run SQL queries | Yes (SQL Editor) | No |
| Database connectivity | Direct two-tier connection | None, uses web services API |
| Infrastructure | Desktop client, often a dedicated VM or terminal server | Web browser, no specialized infrastructure |
| Training required | Significant | None, same search box as a Confluence page |
Beyond Security
Removing unnecessary App Designer access has practical benefits beyond risk reduction:
- License savings. PeopleTools client licenses are not free. Every user who moves from App Designer to psLens is a license you do not need to maintain.
- No desktop installation or VM access. App Designer requires installation on a workstation or access to a dedicated virtual machine or terminal server. psLens runs in any browser, no specialized infrastructure needed.
- Immediate productivity. New team members can start researching PeopleSoft configuration on their first day. No App Designer training, no connectivity setup, no waiting for access provisioning.
- Access from anywhere. psLens is a web application. No VPN or direct database connectivity required (depending on your network configuration).
Who This Applies To
Any role that uses App Designer primarily for research rather than development:
- Business Analysts: researching components, records, and page structures for requirements
- Functional Consultants: understanding configuration and tracing security chains
- Auditors: reviewing security setup, permission lists, and access grants
- Support Analysts: looking up object definitions during incident investigation
- Project Managers: understanding scope and impact of proposed changes
- New Team Members: learning the system during onboarding
If they are not writing PeopleCode or building projects, they probably do not need App Designer.