-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Control / Permissions #642
Comments
You would just return a sensible error code to Member D and handle that client-side (show some alert for example), just as with a traditional HTTP API. |
If you put access control rules in the middleware on the server, the changes from Member D will be sent to the server but not actually ever applied to the document. See the docs here: https://share.github.io/sharedb/middleware/op-submission#apply |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A very fine project!
I'm new to OT/CRDT, and I was wondering how/if a (central) user/role/group permission based access control can be added?
For example, for a Notes PoC. Also, how would conflicts like these be handled?
note Test
. Member D opens it.note Test
toprivate
(not accessible by D)note Test
, and various other edits toother notes
The text was updated successfully, but these errors were encountered: