Docs: self-hosted distribution & responsibilities guide - #15
Merged
Conversation
…install) New "Installing for your team" page grounded in Google's current docs: - why self-hosted = you own all three components (server, GCP project, Chat app) and there's no shared central Marketplace app - Path A: visibility allowlist (≤5 individuals or a Google Group) + self-add - Path B: private Marketplace listing + admin force-install (zero-touch), with the "publish ≠ install" trap called out - set Authentication Audience = Project Number (the mode AsyncUp verifies) - Google-side responsibility split + "$0 on Google" pricing - "AsyncUp not responding" checklist (empty visibility, publish≠install) Cross-linked from google-chat-setup; added to sidebar.
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.
Adds the operator-facing guide for getting the bot to a team, for the fully self-hosted model. Grounded in Google's current docs (Marketplace SDK, Chat app config, verify-requests) and the Admin-console allowlist/install flow.
guide/distribution.md: allowlist+self-add (small teams) vs private Marketplace + admin install (org-wide); responsibility split; $0-on-Google pricing; "app not responding" checklist.google-chat-setup.md: set Authentication Audience = Project Number; note the add-on-vs-classic UI; hand off distribution to the new page.Docs-only; builds clean with the project base path.