Can we allow Act As to be delegated at Sub Account Levels and not just Global Account admin?
@apaglione No, the User - Act As permission is handled at the root account level and can only be granted at the root level of your Canvas instance.
If you do enable it, be extremely careful as it can allow users to gain access to subaccounts that they won't normally have access to. This may violate your institution's policies. Hope this helps!
Hi @apaglione,
I just to expand on @melodyc_lam's reply a bit, as I know this is a feature that's been asked about quite a bit over the years...
On one hand, I totally understand the desire to limit root account admin access as much as possible, which this could help.
On the other hand, when thinking about hot it could/would work, things can get very complicated very quickly in the varied scenarios that happen often in Canvas. For example, users are often enrolled in courses belonging to different subaccounts (which is why all uses really live in the root Canvas account. if subaccount A admin acts as a user who has an enrollment in subaccount A, would they get to see the other courses the user is enrolled in for subaccount B and C as well? From a strict access perspective, the answer would probably be "no", but to truly get the user's identical experience for support issues, the answer would have to be "yes".
It could be argued that root admins could have some option checkboxes to set and control some of the above behavior as they want to, but that would likely also complicate the codebase very quickly, which I'm sure Instructure wants to avoid.
Depending on the size of your school, the approach we use may work for you, as it's somewhat a blend of functionality and security. We give our subaccount admins their "normal" permissions at the subaccount level. In addition, we created a custom admin role with just a few permissions, including acting as users, and enroll our subaccount admins with that role in the root account. This may get unwieldy for larger schools/institutions, but it does work for us and it does help make it explicitly clear to everyone the permissions we're giving to each admins and at what level those permissions come in at.
So the bottom line right now is exactly what Melody said... At this time, this can't be done at the subaccount level. That could change in the future though, and there are some workarounds like the one I mentioned that may help.
I hope this extra info helps make things slightly clearer for you.
-Chris
With the new SpeedGrader UI, we are seeing student names appear in the page title even when the “Hide student names” setting is enabled. When using Classic Quizzes, there is no option within the quiz settings to enable anonymous grading, so we rely on instructors using the hide student names setting in SpeedGrader to…
Speedgrader chaning file name when being downloaded. Speedgrader: When downloading a submitted assignment, the file name is being changed to an unrecognizable name — (Student's actual name was part of the file name — changed for privacy.) Ideas???
We are all familiar with the standard Course Calendar, where assignment due dates are automatically added. However, at my institution, we structure our assignments as Challenges that develop over a period of time, rather than just a single deadline. Currently, the calendar only highlights the "end point." It would be a…
The current placement of the "Submit" button creates a "slip" in user behavior where habit-clicking "Next" leads to an accidental final submission. I think Canvas could easily fix this by: Moving the Submit button away from the navigation buttons (maybe above the question instead of below it) and/or Adding a "Confirm…
Hi everyone! I would love to hear your suggestions and best‑practice tips on implementing copyright settings. https://embed.app.guidde.com/playbooks/8eYgHHmwTXKMLxDW4LqEDX
