-
Type: Sub-task
-
Status: Open (View Workflow)
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 0.17 Swallows
-
Fix Version/s: backlog
-
Labels:
When going to the page of creating Permission Schemas, it should show a list of all of them. There should be an ability to add new Permission Schema with specified groups, their permissions and their properties.
Suggested entity structure:
/** * There can be different permission schemas, but only one will be active. * Active schema defines what groups are used to place users into when they are registered * or banned. Also, when Admin creates a new branch, he'll be provided with a list * of Permission Schemas which he can choose from. So when the branch is being created, * the active Permission Schema will be chosen by default. */ PermissionSchema { List<GroupPermission> groupPermissions { /** * Each GroupPermission contains a Group inside, its properties and what permissions * are allowed/restricted to that group by default when a new branch is created. */ GroupInfo groupInfo { Group group; /** * defines whether user should added to this group when someone is banned */ boolean isBannedUsers; /** * defines whether user should added to this group when new user is registered */ boolean isRegisteredUsers; } /** * These permissions will be allowed to the group when a new branch is created. * E.g. we have Global Moderators group. When a new branch is created, it will be * provided with the moderating permissions on the newly created branch. */ List<BranchPermission> allowed; /** * These permissions will be restricted to the groups when a branch is created. * E.g. we have a Banned Users group which will be restricted to posting * in the newly created branch. */ List<BranchPermission> restricted; } }