Repository navigation
multi-ingress: Document to disable public account creation - #125
Merged
Merged
Conversation
supersven
force-pushed
the
sventennie/multi-ingress-team-settings-docs
branch
from
September 24, 2026 14:05
118d7af to
d40290d
Compare
supersven
force-pushed
the
sventennie/multi-ingress-team-settings-docs
branch
from
October 7, 2026 07:23
d40290d to
16bc883
Compare
mohitrajain
reviewed
Oct 7, 2026
supersven
force-pushed
the
sventennie/multi-ingress-team-settings-docs
branch
2 times, most recently
from
October 7, 2026 09:14
9b5d951 to
426dd62
Compare
Team settings is not multi-ingress ready, so this won't work anyways. Also, allowing everyone to create accounts is certainly not what on-prems want.
supersven
force-pushed
the
sventennie/multi-ingress-team-settings-docs
branch
from
October 7, 2026 13:08
426dd62 to
935a622
Compare
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
Only an optional grammar correction remains; no blocking issues were identified.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Documents how to disable public account creation in multi-ingress deployments.
Changes:
- Adds optional Brig restrictions and team-owner provisioning guidance.
- Disables registration in the webapp example and explains team settings’ multi-ingress limitation.
| File | Description |
|---|---|
| src/how-to/install/multi-ingress.md | Adds account-creation restrictions and updates webapp configuration guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Fix typo and clarify usage of team settings app. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
Team settings is not multi-ingress ready, so this won't work anyways. Also, allowing everyone to create accounts is certainly not what on-prems want.
Change type
Basic information
Testing
Tracking