Custom Fields for JSM PortalThe problem
“Has my manager approved it yet?” is the most common HR enquiry, and the answer is a field on the request. Yet HR requests are also where the wrong person changing a value does the most harm, and where a request is often shared with a whole organization.
What to show, and what to open
| Field | Treatment |
|---|---|
| Case category | Show. Confirms the request landed in the right queue. |
| Effective date | Show. For onboarding, leave and contract changes it is the value that matters. |
| Approval status (a select field) | Show, never open. Anything with a compliance trail stays read-only. |
| Preferred name, equipment preference | Open. Details the employee owns anyway. |
Step by step
- Give the HR project its own configuration. It replaces the default for that project, so no IT field ever appears on an HR request.
- Choose “Only the reporter” under Editing in the portal. A colleague the request was shared with can read it, but not change it.
- Keep “only while the request is open”. A closed case stays as it was closed.
- Let the HR desk maintain it. Their project administrator can change fields and labels under Project settings, without a site admin.
What to watch out for
“Anyone who can see the request” includes everyone it was shared with through their organization. For HR, the narrow audience is the right default.