Qiskit / Qiskit/documentation

Document new account reader role

Open
#4,097 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content 📄
Dominant language
Jupyter Notebook
Stars
106
Forks
223
Avg merge
1d 8h
Merged PRs (30d)
72

Description

URL to the relevant guide or resource

https://quantum.cloud.ibm.com/docs/guides/access-groups#compare-pre-defined-service-role-actions
https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actions#quantum-computing-roles

Select all that apply
  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other
Describe the fix or the content request.

SME: Cameron Kurotori

Note: Also might be good to explain that the account actions must be granted in scope of the quantum-computing service on the entire account and not just an instance. This is a little confusing so might be worth to explain it.

Definitely not a high priority item but would be good to do. I wouldn't start work on that though until this new role gets sign off from product to ensure it makes sense for the direction we're going.

For new content requests - if the request is accepted, do you want to write the content?

I will write (or already have written) a draft of the proposed content

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked access-groups and account IAM service-role guides, then confirm the new role has product sign-off with Cameron Kurotori. Update the relevant guide to document the account reader role and clarify that its account actions apply to the quantum-computing service at the entire-account scope, not only an instance.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.