You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m struggling a bit with the permission system as we can’t freely set permissions.
Say I have an assignment document that I as a student (team:xxx/member) created and I only want me and my teachers (team:xxx/owner) to see.
As far as I know I have 3 options:
Create a function that does the work and make the collection “read only” (sketchy as documents can still be created through the sdk, we would need Collection permission to disable that, together with document permission to complete this use case.)
Create a team for every student-teacher pair (not realistic, way too many teams)
Create a team role for every student so that each teacher that has this role can see the students assignments. (Many roles of teacher will probably have big impact performance)
Other Use cases
I can think of a few more cases where a team member wants to freely set permissions:
Say I have a registration app for employees to submit the hours they have worked. These documents must be visible for himself and 'team administration' (team:xxx/admin) so that only he and the business owners can see the worked hours.
Say I have a game where a player sends private messages to someone in my current game (team). The player creates a message and sets the permissions for user:himself and user:receiver.
Proposed solution
Make it possible for users to freely set permissions on their documents.
Maybe missing some important security or performance related details why the permission system works the way it does.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Background
I’m struggling a bit with the permission system as we can’t freely set permissions.
Say I have an
assignmentdocument that I as a student (team:xxx/member) created and I only want me and my teachers (team:xxx/owner) to see.As far as I know I have 3 options:
Create a function that does the work and make the collection “read only” (sketchy as documents can still be created through the sdk, we would need Collection permission to disable that, together with document permission to complete this use case.)
Create a team for every student-teacher pair (not realistic, way too many teams)
Create a team role for every student so that each teacher that has this role can see the students assignments. (Many roles of teacher will probably have big impact performance)
Other Use cases
I can think of a few more cases where a
team memberwants to freely set permissions:Say I have a registration app for
employeesto submit the hours they have worked. These documents must be visible forhimselfand 'team administration' (team:xxx/admin) so that only he and the business owners can see the worked hours.Say I have a game where a
playersends private messages to someone in my current game (team). The player creates amessageand sets the permissions foruser:himselfanduser:receiver.Proposed solution
Make it possible for users to freely set permissions on their documents.
Maybe missing some important security or performance related details why the permission system works the way it does.
What are your thoughts?
All reactions