[Roles] Separate platform admin from account role allocations

[Mikee]

Problem statement:

Assigning roles appropriate for these users should be separated from the account's platform administration engineering team who need what's called "Admin" in canvas.

Proposed solution:

We are a large institution with varying roles and responsibilities spread across our central support teams, faculty support, school support, central disability support teams, faculty administration, school administration, central development team, learning and teaching support, L&T dev, analytics views.... you get the idea. Separating those who work "on" the platform is important to be able to see who's able to modify the platform against those who have globally elevated privileges.

User role(s):

admin

[brian_mullins]

@Mikee Are you wanting a new set of permissions for the 'platform' admin that aren't currently available? If not, can't you just create a role based on that admin default role and call that 'elevated permissions', limiting it to what they can do?

[Mikee]

No, @brian_mullins - I would like non-subject roles that are not administrators to be taken from the Administration area.

Having a helpdesk role (as we do) that can see all subjects but no content is in no way or shape an admin. Providing access for disability support teams platform-wide is also not an admin.

We have sufficient scale that our admin list is huge and unwieldy; it's nearly impossible to clearly see who can do what.

[KristinL]

Thank you for sharing this idea with the Instructure Community!

The Product Team reviewed all feature proposals recently, and unfortunately, this thread was identified as one that they would not be able to include in their current or future plans. While we appreciate your proposal, we also want to be transparent about the likelihood of something like this making it to production.

Thank you for collaborating, and we hope that you submit another idea in the future!