Add Workers RBAC updates#16213
Conversation
github-actions
Bot
added
product:fundamentals
product:workers
Deploying cloudflare-docs with
|
| Latest commit: |
314bff1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3eb0e5ff.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://jye-workers-rbac.cloudflare-docs-7ou.pages.dev |
irvinebroque
left a comment
irvinebroque
left a comment
There was a problem hiding this comment.
Am glad we are adding a table for this
|
|
||
| To check the list of members in your account, or to manage roles and permissions, refer to our [Account setup](/fundamentals/setup/manage-members/) documentation. | ||
|
|
||
| The following roles have permissions not restricted to Cloudflare [Workers](/workers/) but to related developer platform products too. This includes [Pages](/pages/), [Durable Objects](/durable-objects/), [KV](/kv/) and [R2](/r2/). It also provides read access to Zones, [Zone Analytics](/analytics/account-and-zone-analytics/zone-analytics/) and [Page Rules](/rules/). |
There was a problem hiding this comment.
- This should live within the section below
- It seems like we should be able to enumerate these more specifically — otherwise how does someone reading this know something like, one needs the
Workers Adminpermission in order to deploy a Pages project?
There was a problem hiding this comment.
For 2, what do you have in mind? The copy is from a pre-existing description of Cloudflare Workers Admin role and outlines all the devplat products the role impacts.
There was a problem hiding this comment.
Right now, when I read this, I know that which Workers role I have somehow impacts what I am allowed to do with Pages, KV, etc. — but it's not explicit how.
I am saying that we should go figure out specifically things like, if I have the Workers Read role — what does that mean for whether I can or can't deploy a Pages project?
...and enumerate them on this page.
If we can't right now, then I don't think we should include this content about Pages, KV, etc on this page. It leaves you with more questions than answers.
|
|
||
| ## Workers roles | ||
|
|
||
| Only Super Administrators will be able to assign or remove the following roles from users in their account. They also have all the permissions of a Workers Admin. Scroll to the right to see a full list of permissions for each role. |
There was a problem hiding this comment.
Scroll to the right to see a full list of permissions for each role.
@kodster28 should we track something internally around making it more intuitive and visible that a table that extends horizontally beyond the viewport is scrollable, so that docs authors don't need to explain it in words?
There was a problem hiding this comment.
Yeah... tables are an ongoing issue that we're discussing.
I think that's one potential solution... but there's a lot of stuff in the works + mobile and tables just really don't go together.
| | Vectorize Read only | Can read [Vectorize](/vectorize/) configurations. | | ||
| | Waiting Room Admin | Can edit [Waiting Room](/waiting-room/) configuration. | | ||
| | Waiting Room Read | Can read [Waiting Room](/waiting-room/) configuration. | | ||
| | Workers Admin | Can manage Cloudflare [Workers](/workers/), [Pages](/pages/), [Durable Objects](/durable-objects/), [KV](/kv/) and [R2](/r2/). Also provides read access to Zones, [Zone Analytics](/analytics/account-and-zone-analytics/zone-analytics/) and [Page Rules](/rules/).| |
There was a problem hiding this comment.
It seems helpful for this in some way to link to the new page in the Workers docs that you are adding? (think fine if unique to Workers and other products don't do this on this page)
There was a problem hiding this comment.
Good idea, unfortunately only Zero Trust does this too. If we think two products is enough, we could add a note that links to their specific role pages.
Co-authored-by: Brendan Irvine-Broque <birvine-broque@cloudflare.com>
Co-authored-by: Brendan Irvine-Broque <birvine-broque@cloudflare.com>
Co-authored-by: Brendan Irvine-Broque <birvine-broque@cloudflare.com>
8 participants
Summary
Screenshots (optional)
Documentation checklist