Requisition REST grants
ConceptintermediateThe duty-role grants that decide who may read, create, update or delete a job requisition through the recruitingJobRequisitions REST resource, and the boundary of what the security reference page documents.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That access is a property of the job role. It is a property of the duty-role grant, and one role is listed under both a read-only and a full duty role.
- That a security reference page is enough to write an API integration. It carries no endpoint URI, request schema, response schema or field names.
Recall it
Which duty roles grant access to the recruitingJobRequisitions resource, what does each grant, and which role appears under more than one?
Use REST Service - Job Requisitions Read Only grants Get and Describe. Access Recruiting Activity Center and Use REST Service - Job Requisitions both grant Get, Post, Patch, Describe and Delete. The Human Capital Management Integration Specialist appears under the read-only duty role and under a full-privilege duty role, so access follows the duty-role grant rather than the role.
Memory hook: Check the duty role, not the role. The same job role can be read-only in one tenant and full in another.
Rests on ORC-REST-030, ORC-REST-033, ORC-REST-034, ORC-REST-035.
Taught in
Related
- Terminology glossary — what a term means, and what people get wrong when they use it