Skip to content

Registry: Add info about SA access to different types of registries#2753

Open
ngrayluna wants to merge 5 commits into
mainfrom
sa_registry_access
Open

Registry: Add info about SA access to different types of registries#2753
ngrayluna wants to merge 5 commits into
mainfrom
sa_registry_access

Conversation

@ngrayluna

Copy link
Copy Markdown
Contributor

Description

Add info about SA access to different types of registries.

Related issues

https://coreweave.atlassian.net/browse/DOCS-2549

@ngrayluna ngrayluna requested a review from a team as a code owner June 11, 2026 19:30
Copilot AI review requested due to automatic review settings June 11, 2026 19:30
@mintlify

mintlify Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
wandb 🟢 Ready View Preview Jun 11, 2026, 7:36 PM

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation clarifying how service accounts (SAs) get access to registries depending on registry visibility and team roles, and updates related cross-references within the registry access docs.

Changes:

  • Adds a new “Service account access” section describing SA access behavior for Organization vs Restricted visibility registries.
  • Expands the service account footnote to link readers to the new section.
  • Updates the “registry role permissions” link near the “Add a user or a team” section.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread models/registry/configure_registry.mdx Outdated
Comment thread models/registry/configure_registry.mdx Outdated
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

📚 Mintlify Preview Links

🔗 View Full Preview

📝 Changed (1 total)

📄 Pages (1)

File Preview
models/registry/configure_registry.mdx Configure Registry

🤖 Generated automatically when Mintlify deployment succeeds
📍 Deployment: 2d500b1 at 2026-06-12 18:36:47 UTC

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🔗 Link Checker Results

All links are valid!

No broken links were detected.

Checked against: https://wb-21fd5541-sa-registry-access.mintlify.app

Comment thread models/registry/configure_registry.mdx
Comment thread models/registry/configure_registry.mdx
Comment thread models/registry/configure_registry.mdx
The following describes the default access level for a service account:

- **Registries with Organization visibility**: a service account automatically has **Member** access.
- **Registries with Restricted visibility**: service acount access depends on the role assigned to the service account's team:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Registries with Restricted visibility**: service acount access depends on the role assigned to the service account's team:
- **Registries with Restricted visibility**: service acount access depends on the role assigned to the service account's team or the service account itself:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this still reads to me as though one needs to assign a team role for the service account to receive a role in a restricted registry. i think we should instead focus on how service accounts dont inherit higher permissions just because a team they're in gets assigned "admin" in a registry. (and this is true for both restricted and non-restricted registries)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants