Registrar default privacy #2855
Merged
Conversation
This file contains 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
|
Good call on "registrators" |
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.
This PR adds a field to the Registrar model, indicating whether they want newly-created orgs in their network to default to public or private Perma Links. Public is the norm; on request, administrators can set a Registrar to default to private, either via the Django admin or via the manage/registrars page.
Registrars can't configure this themselves, just like they can't change the Registrar's name, email address, or website: the manage/registrars page is admin-only.
I also added info to the docs about the configuring a single org's default privacy, and a link to contact us about registrar-level config:
/docs/libraries#privacy