Repository navigation
docs: each operator creates their own Google file and keys - #67
Merged
Merged
Conversation
…keys An Internal Google client only works inside one organization, so a shared connection file fails for operators in different organizations. A Slack user token acts as whoever generated it, so sharing one let its holder search that person's DMs and post as them. README step 3 now creates the connection file, and step 5 asks an admin only for access: Drive, Slack app collaborator and Luma calendar admin. The operator then generates both keys. aaif-check-setup points at those steps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
Self-ReviewImportant (5)
Suggestions (6)
Strengths
Generated using wayfare. |
- Step 4 and the setup check say a missing-access line is expected until step 5 - Access blocked covers Internal and External separately - Removing a person names how to end a token only they hold, and covers any token or key that was passed around - Step 5 explains replacing a saved key - Tests pin step 5 and the new fix pointers Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Adding and removing a person cover private organizer rooms and the Ops staff roster, because a personal token only sees rooms its owner is in - The setup skill says when not to run the printed sign-in command - README names the disabled-service line the check actually prints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
Self-Review: ImprovementsImportant (7 / 7 fixed):
Suggestions (7 / 7 addressed, 1 partly):
Skipped:
Not tested: the Slack collaborator route for a personal token, and the Slack, Luma and Google console screens. These need one live pass with a second account. Generated using wayfare. |
rparundekar
marked this pull request as ready for review
November 4, 2026 06:47
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.
What changed
aaif-check-setup: its fixes point at those steps instead of asking an admin for a file or key.This replaces the one-shared-token decision in #66. A Slack user token acts as whoever generated it, so a shared one let its holder search that person's DMs and post as them.
Testing
test_check_setup.py, library tests andpre-commitpass.🤖 Generated with Claude Code