Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the use of coursearchiver to manager system role #40

Open
canatojr opened this issue Apr 7, 2022 · 1 comment
Open

Allow the use of coursearchiver to manager system role #40

canatojr opened this issue Apr 7, 2022 · 1 comment

Comments

@canatojr
Copy link

canatojr commented Apr 7, 2022

Hello!

On our website we need the coursearchiver to be used by users in the manager system role.

To do so, I did the following:

  • A) Created a capability (tool/coursearchiver:view) in the database table (mdl_capabilities)
  • B) Changed the code in the cousearchiver/settings.php file, commenting out the lines 27, 75, 76 and adding the capability information to the line 72: $ADMIN->add('courses', new admin_externalpage('toolcoursearchiver', get_string('coursearchiver', 'tool_coursearchiver'), "$CFG->wwwroot/$CFG->admin/ tool/coursearchiver/index.php", 'tool/coursearchiver:view'));
  • C) Assigned that capability to the manager system role.

It's working fine, but I don't know if this way is the best and if it doesn't involve security issues.

So I'm reporting this experience just to suggest inserting a feature in the coursearchiver that allows its use for users allocated as managers but not as site administrators.

Best regards,

Osvaldo

@drfyzziks
Copy link

drfyzziks commented Jan 30, 2024

I'd like to add my vote for being able to run Course Archiver under other users/roles besides admin. One of the schools whose Moodle I manage has a large number of old courses they need to archive (going back years). Because it's such a large task, they have divided the work among 4 people. In order to run Course Archiver, we've had to give them admin privileges, with a warning not to touch anything else in the system - which is not ideal.

Alternatively, we could have created a single user account w/admin privileges and let them share that, but that has its own issues.

Ideally, having a "tool/coursearchiver" capability that we could assign to a manager or similar role would solve both our access and accountability problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants