Custom job set not requiring custom privilege

Summary:

user guide is very clear on this topic:

but reality is different. Created a custom job set for cycle count alike the seeded job set but without the report. It works immediately. No need to link a privilege. And privilege was not even found. So unclear as to why this is behaving like this while documentation clearly mentions the need to link a custom privilege.

Content (please ensure you mask any confidential information):

User guide specific note in section:

Note

When you create a job set, a privilege with the same name as the job set is automatically created with a Run prefix. For example, for a job set named ExportAppsData, with display name Export Application Data, the privilege code is RUN_EXPORTAPPSDATA, with Run Export Application Data as the name. Make sure to use the Security Console to assign this privilege to roles so that users who need to run the process set can do so.