Simplifying permissions
If you've ever had to configure permissions for other administrators, you'll know there are a lot to choose from. Some of them make more sense than others. If you're not already familiar with permissions, now might be a good time to stop reading—it's going to get a bit intense.
The problem: too many permissions
Currently, for most “things” (e.g. news, links, FAQs), we have 3 levels of permissions: view, edit and delete. And you can grant each of these permissions individually. So you can do clever things, like say that an admin can delete links, but they can't view or edit them. Insert maniacal laugh here.
Taking links as an example, of the 8 possible combinations of view/edit/delete, only 2 really make sense. They are:
- you can only view links
- you can do anything with links—view, edit and delete them
How we're going to fix this problem
Starting with news and links, we're going to condense the permissions for each resource down to just 1, “edit”—which means “do anything” with this resource. So, Link.Edit or News.Edit. If you don't have, say, News.Edit, you can still see news in admin (and in the student console), but you can't write, edit or delete news. If you do have that permission, you can do anything related to news.
We'll be fixing permissions for FAQs and Info Sheets (a.k.a. documents) too over the coming months.
