| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Attach the role-manipulation privileges to the resource rather than
the group, because the roles actually act on the resource itself -
thus each role needs to track which resource it acts on.
|
|
|
|
|
|
|
|
Provide a new migration to create tables to handle the InbredSet
resources. The migration also sets up the resource category and the
related privileges.
|
|
|
|
Add a new `public-view` role to be assigned to all users on all
resources that are defined as publicly viewable.
Update code to make assign `public-view` role to a newly registered
user for all publicly viewable roles.
Update the code to assign/revoke the `public-view` role to/from users
whenever the resource is toggled to and from being publicly viewable.
Ensure that `public-view` is not revoked from system-administrators.
Ensure that `public-view` is not revoked from the group administrators
of the group that owns the resource.
|
|
* Link the `role_id` field to the `roles` table rather than the
`group_roles` table.
* Merge the data in the `group_user_roles_on_resources` table in the
`user_roles` table to have a single point-of-truth for all user
roles on resources.
|
|
Add a 'system' resource to allow users to have roles they can use to
act on the system itself.
|
|
|
|
Drop the `group_id` from the `resources` table and update all
dependent tables to fix FOREIGN KEY constraints to ensure integrity of
the data.
|
|
|
|
New table to link resources to groups, where relevant.
|
|
|
