Resolve effective permissions
Review field access by role and status. See which permission block wins when later rules override earlier ones.
- Requisition and application scopes
- Field and status-oriented views
- Source-block provenance
Job Requisition XML workbench
A clearer way to work with JRDM XML.
Permistry helps SAP SuccessFactors® Recruiting consultants inspect permissions, make deliberate changes, and review the exact result before exporting a template.
- Runs in your browser
- No file uploads
- No account required
job-requisition-template.xml
Local only
Unchanged
0 errors
Requisition status
Pre-screen
5 fields · 3 roles
FieldRGO
jobTitletext
WRR
departmentderived
RRR
targetStartDatedate
WR
internalNotestextarea
W
locationobject
WRR
Built for configuration work
Understand the template before you change it.
JRDM files are readable, but they are not easy to reason about at scale. Permistry turns the relationships in the XML into views a consultant can inspect and verify.
Make targeted changes
Work through a permission matrix instead of editing blocks by hand. Permistry keeps each change limited to the stated intent.
- Write, read-only, and hidden states
- Undo and redo
- Measured change review
Review before export
Inspect validation findings, semantic impact, and the source diff before creating a modified XML file.
- Cross-reference validation
- Template comparison
- Exact source diff
A controlled workflow
From export to reviewed XML.
Permistry supports the work around Provisioning. It does not connect to your tenant or bypass the established import process.
-
01
Open the template
Select a Job Requisition Data Model export from your computer. The browser reads it locally; the original file is not overwritten.
-
02
Inspect and edit
Move between permissions, fields, blocks, features, and findings. Make changes through structured controls while the XML remains inspectable.
-
03
Prove the result
Review what changed, check validation findings, and export a new XML file for your normal review and Provisioning procedures.
Local by design
Your template stays on your machine.
Opening a template does not upload it. Parsing, validation, comparison, and editing happen inside your browser.
No document storage
Template contents are not sent to a Permistry server.
No tenant connection
The tool does not ask for or use SuccessFactors credentials.
No analytics in the tool
Your configuration work is not tracked or profiled.
Deliberate export
A modified file is created only when you choose to export it.
Practical details
What to expect.
Which templates does Permistry support?
The current scope is the Job Requisition Data Model XML,
including field permissions and the
<application-status-config> section within that file.
Does it modify my original file?
No. Permistry keeps the loaded source in memory and exports a separate modified XML file when you ask it to.
Does it replace Provisioning validation?
No. Permistry adds focused inspection and cross-reference checks, but the final validation and import remain part of your authorized Provisioning process.
Do I need to create an account?
No. Open the tool in a supported browser and select a local template when you are ready to work.
Use the template you already have
See the configuration clearly.
Open Permistry and work locally in your browser.
Try the JRDM tool