Documentation for public sharing level and entity-specific permissions #483
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
marcua
commented
Nov 14, 2024
|
|
||
| # The default setting: no entity will be able to access the database | ||
| # (unless they specifically get permissions). | ||
| ayb client update_database marcua/test.sqlite --public-sharing-level no-access |
There was a problem hiding this comment.
Make these consistent with the other CLI examples (e.g., prefix with $, consider showing output). Not sure about showing output as the commands themselves are clear.
marcua
commented
Nov 14, 2024
| ayb client update_database marcua/test.sqlite --public-sharing-level read-only | ||
| ``` | ||
|
|
||
| To provide a specific user with access to a database, select one of the following: |
There was a problem hiding this comment.
Everything below here is not yet implemented
8 tasks
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.
As part of #281, introduces documentation for the two types of access control that are possible. I won't merge this until the features are on
mainso as to not confuse users, but it was helpful write it up to aid in the implementation.