# Read\_job\_admin\_activity OAuth Scope

**URL:** <https://community.servicem8.com/t/read-job-admin-activity-oauth-scope/1199>\
**Category:** Developer\
**Created:** [September 21, 2026, 3:09am UTC](https://community.servicem8.com/t/read-job-admin-activity-oauth-scope/1199 "2026-09-21T03:09:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hamish\_burns](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@hamish\_burns](https://community.servicem8.com/u/hamish_burns)\
**Post date:** [September 21, 2026, 3:09am UTC](https://community.servicem8.com/t/read-job-admin-activity-oauth-scope/1199/1 "2026-09-21T03:09:51Z")

</div>

Hi I am trying to access the jobadminactivity via this endpont [Retrieve a Job Activity](https://developer.servicem8.com/reference/getjobadminactivities)

When trying to add the scope **read\_job\_admin\_activity** I get an error that the scope is invalid , and the scope is not listed on the authentication page [Authentication](https://developer.servicem8.com/docs/authentication)

---

<div class="post-metadata">

**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\
**Post date:** [September 24, 2026, 3:11am UTC](https://community.servicem8.com/t/read-job-admin-activity-oauth-scope/1199/2 "2026-09-24T03:11:46Z")

</div>

Hi Hamish,

You’re right, the endpoint reference says `GET /jobadminactivity/{uuid}.json` requires `read_job_admin_activity`, but that scope isn’t included in the Authentication page’s supported scope table.

We can’t confirm an alternative OAuth scope for `jobadminactivity` from the current documentation, so this discrepancy needs review rather than substituting `read_schedule` or `staff_activity`. The documented `read_schedule` scope applies to the JobActivity and JobAllocation endpoints, while `staff_activity` covers staff clock-on, lunch-break and clock-off information.

Could you email [support@servicem8.com](mailto:support@servicem8.com) with the failed request and response, with any secrets removed, so we can pass it on for review?

Thanks,  
Cody