Repository navigation
docs: record the group assignment answer - #34
Merged
Merged
Conversation
State in troubleshooting, assumptions and T3 that assigning groups takes TrustedFacilityAdmin within the VO, which is not granted here, so the VO admins assign groups on request; link to client registration and mark the T3 question as answered. Closes #33 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011FSoqMpmDCfbACLj3uy6xV
Reviewer's GuideDocumentationRecord that assigning groups requires TrustedFacilityAdmin within the VO and that VO admins assign groups on request, marking the question answered and linking the related guidance.
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Documentation build overview
4 files changed± tests/index.html± setup/troubleshooting/index.html± testbed/assumptions/index.html± tests/t3-groups/index.html |
uniqueg
marked this pull request as ready for review
November 11, 2026 11:52
Linked issuesChecked at commit da9e7d9 #33 docs: record the group assignment answer · 1 of 1 met
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Records the answer from #30 (
docs/setup/client-registration.md#who-can-assign-groups) in the places that still described the greyed-out "Assign groups" button as a known problem or an open question:docs/setup/troubleshooting.md: states the cause (TrustedFacilityAdmin within the VO, not granted for this setup) and what to do (ask the VO admins), with a link to the anchor.docs/testbed/assumptions.md: marks the item as answered and links to client registration and T3.docs/tests/t3-groups.md: marks the question as answered and fills in the "Group release" result row.docs/tests/index.md: marks the question as answered, linking to its section.No new facts beyond those in client-registration.md.
Light lane: docs-only change; reviewer subagents skipped, diff reviewed by hand.
Verification
mkdocs build --strict: passedpre-commit run --all-files: all hooks passedCloses #33
🤖 Generated with Claude Code
https://claude.ai/code/session_011FSoqMpmDCfbACLj3uy6xV
Summary by Sourcery
Record the confirmed requirements and workflow for assigning VO groups across the relevant documentation.
Enhancements:
Documentation: