docs: Added limited staff role

[bpedx]

Add a description of your changes with links to any relevant material.

Date Needed (optional)

If the release date of a feature is known or estimated, provide it to give reviewers guidance on turnaround time.

Reviewers

Possible roles follow. The PR submitter checks the boxes after each reviewer finishes and gives 👍.

• Subject matter expert:
• Subject matter expert:
• Product review:
• Partner support:
• PM review:

FYI: Tag anyone else who might be interested in this PR here.

Testing

• Ran ./run_tests.sh without warnings or errors

HTML Version (optional)

• Build an RTD draft for your branch and add a link here

Sandbox (optional)

• Point to or build a sandbox for the software change and add a link here

Post-review

• Add a comment with the description of this change or link this PR to the next release notes task.
• Squash commits

[openedx-webhooks]

Thanks for the pull request, @bpedx! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

⚠️ We can't start reviewing your pull request until you've submitted a signed contributor agreement or indicated your institutional affiliation. Please see the CONTRIBUTING file for more information. If you've signed an agreement in the past, you may need to re-sign. See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed. After this time, you can re-run the CLA check by adding a comment here that you have signed it. If the problem persists, you can tag the @openedx/cla-problems team in a comment on your PR for further assistance.

[mphilbrick211]

Hi @bpedx! Thanks for this contribution. Are you a 2U/edX employee? If so, you'll need to be added to their entity CLA (have your manager reach out to [email protected]. If you're contributing as an individual, you'll need to fill out the individual CLA as indicated above.

[bpedx]

Hi Michelle, It’s Ben Piscopo on the 2U Product team. Ned B and Jeremy R both submitted info for me today. Do you mind also checking for me under ***@***.*** ? Thanks, Ben

…

On Thu, Sep 14, 2023 at 16:33 Michelle Philbrick ***@***.***> wrote: Hi @bpedx <https://github.com/bpedx>! Thanks for this contribution. Are you a 2U/edX employee? If so, you'll need to be added to their entity CLA (have your manager reach out to ***@***.*** If you're contributing as an individual, you'll need to fill out the individual CLA as indicated above. — Reply to this email directly, view it on GitHub <#2185 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEA6F362ITKNWWWW422ZM3X2NS3NANCNFSM6AAAAAA4YTUVJA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[feanil]

FYI, I just updated Ben's records so the CLA bot should update overnight tonight.

[mphilbrick211]

FYI, I just updated Ben's records so the CLA bot should update overnight tonight.

Thanks, @feanil! FYI @bpedx

[feanil]

No, you are covered by the 2U Entity Agreement.

[bpedx]

Nevermind, the checklist just updated itself... but now "this branch is out-of-date with the base branch". Should I Update Branch or should I Update with Rebase? @feanil

[mphilbrick211]

Hi @bpedx! Rebasing should fix it.