{{Workplace}}

== Overview ==
Web services for the Moodle Workplace [[Migrations]] feature.

The following web services are available in the Moodle Workplace for export and import:
* tool_wp_perform_export
* tool_wp_perform_import
* tool_wp_retrieve_export_file

Standard Moodle LMS functionality is available for uploading a file, see [https://docs.moodle.org/dev/Web_services_files_handling Web services files handling]

To see the exact description of the parameters and return values of these web services in your version of Moodle Workplace, please turn on the admin setting '''$CFG->enablewsdocumentation''' and navigate to '''Site administration > Plugins > Web services> API Documentation'''

== Set up ==

* Create a new service with the functions: '''tool_wp_perform_export''', '''tool_wp_perform_import''', '''tool_wp_retrieve_export_file''' or add these functions to the existing service
* Allow this service for everybody or for users who you want to be able to use them
* Create tokens for the users, enable protocols, add capabilities to use protocols

See more information under [[Using web services]]

== Export ==

The following examples use command-line calls using the REST protocol. The output is piped through '''jq''' command to display JSON in a more readable way. There are many ways to call web-services and there are other alternatives of how to parse JSON. Adjust commands as needed. Do not forget to replace the site name and the token with your token.

=== Dry run ===

First execute the web-service tool_wp_perform_export with the parameter dryrun=1, it will validate input, show some information but will not actually schedule an export. You must pass parameter exporter. If the exporter is not available the error message will be displayed. The error message contains the list of all available exporters. For example:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"exception": "invalid_parameter_exception",
"errorcode": "invalidparameter",
"message": "Invalid parameter value detected (Could not find exporter ''\nChoose from: tool_certification\\tool_wp\\exporter\\certifications, tool_dynamicrule\\tool_wp\\exporter\\rules, tool_organisation\\tool_wp\\exporter\\jobs, tool_organisation\\tool_wp\\exporter\\orgstructure, tool_program\\tool_wp\\exporter\\programs, tool_reportbuilder\\tool_wp\\exporter\\customreports, tool_tenant\\tool_wp\\exporter\\tenants, tool_wp\\tool_wp\\exporter\\certificates, tool_wp\\tool_wp\\exporter\\cohorts, tool_wp\\tool_wp\\exporter\\coursecategories, tool_wp\\tool_wp\\exporter\\courses, tool_wp\\tool_wp\\exporter\\site, tool_wp\\tool_wp\\exporter\\users)"
}
</code>

Now try again with the exporter name:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=tool_organisation\tool_wp\exporter\orgstructure&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 0,
"settings": [
{
"name": "export_instances",
"value": "all"
},
{
"name": "select_frameworks",
"value": ""
}
]
}
</code>

Because it is a dry-run, the id=0 is returned (export was not actually scheduled). The web service also returns the list of settings that will be applied to the export. You may wish to change some of these settings, for example, we can export only positions by adding '''&settings[0][name]=export_instances&settings[0][value]=positions''' to the URL (to pass more settings use a different index).

=== Schedule export ===

Call the web service tool_wp_perform_export without the dryrun=1 parameter. For example:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=tool_organisation\tool_wp\exporter\orgstructure&settings[0][name]=export_instances&settings[0][value]=positions&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 19,
"settings": [
{
"name": "export_instances",
"value": "positions"
},
{
"name": "select_frameworks",
"value": ""
}
]
}
</code>

This call returned id 19, we will need it in the next command

=== Retrieve export file ===

After the next cron run on the server you can retrieve the export file. If the cron has not run yet this command will return an error "Export not ready". Successful return will look like this:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_retrieve_export_file&exportid=19&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

[
{
"filename": "organisation-structure-frameworks-export-20210115-1534.zip",
"filepath": "/",
"filesize": 3396,
"fileurl": "https://SITENAME/webservice/pluginfile.php/1/tool_wp/export/19/organisation-structure-frameworks-export-20210115-1534.zip",
"timemodified": 1610721298,
"mimetype": "application/zip",
"isexternalfile": false
}
]
</code>

To retrieve the file you need to add your token to the fileurl:

<code>
$ curl https://SITENAME/webservice/pluginfile.php/1/tool_wp/export/19/organisation-structure-frameworks-export-20210115-1534.zip?token=cf3788edbe41d7a89e963d9432b15331 > exportfile.zip
</code>

=== Additional parameters ===

Additionally, the tool_wp_perform_export web service has parameters:
* tenant (int|string) - Database ID or non-numeric idnumber of the tenant where the export should be made
* notenant (bool) - Perform export without the tenant (only for exporters that support this).

They can be used by global administrator or another user who has permission to switch between tenants.

== Import ==

The web service '''tool_wp_perform_import''' is responsible for importing.

You can perform an import from an export file or upload a local file. To perform import from a previous Workplace export with id 19 add '''exportid=19''' to the parameters. To perform import from a file you need to first upload a file and then use a draft item id as an argument, for example '''file=123456678''' . Similar to the export, you can use '''dryrun=1''' parameter to validate parameters without actually scheduling import.

=== Upload file ===

In this example we upload a local file '''positions.csv'''. It will be placed in a draft area for the current user. The script returns itemid of the draft area. It can be used only by the same user and will be automatically deleted by Moodle after two days.

Imagine we have a file with the name '''positions.csv''' with the following contents:

<code>
idnumber,parent,name,description,ismanager
CEO,,Chief Executive Officer,Chief Executive Officer position,1
COO,CEO,Chief Operating Officer,Chief Operating Officer position,1
HMD,COO,Head of Marketing and Design,Head of Marketing and Design position,1
MCO,HMD,Marketing Consultant,Marketing Consultant position,0
OM,COO,Office Manager,Office Manager position,0
</code>

''Note1: To demonstrate custom column mappings in this tutorial we called the last column "ismanager". If you call it "manager" or "globalmanager" you will not need to change the default mappings.''
''Note2: File name is important. If you choose to create a new framework during the import (default behavior), the file name will become a framework name''

Standard Moodle LMS functionality is available for uploading a file, see [https://docs.moodle.org/dev/Web_services_files_handling Web services files handling], for example:

<code>
$ curl -X POST -F "image=@positions.csv" https://SITENAME/webservice/upload.php?token=cf3788edbe41d7a89e963d9432b15331 \
| jq

[
{
"component": "user",
"contextid": 567,
"userid": "123",
"filearea": "draft",
"filename": "positions.csv",
"filepath": "/",
"itemid": 880413439,
"license": "allrightsreserved",
"author": "User User",
"source": "O:8:\"stdClass\":1:{s:6:\"source\";s:13:\"positions.csv\";}"
}
]
</code>

=== Dry-run ===

Example importing the export with id 19:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&exportid=19&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq
</code>

Example importing the file that is located in the draft area with itemid 880413439. This is a CSV file and there are several available importers, therefore an error will be raised. The error message will contain the list of available importers:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&file=880413439&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"exception": "invalid_parameter_exception",
"errorcode": "invalidparameter",
"message": "Invalid parameter value detected (More than one importer is available, importer must be specified\nChoose from: tool_organisation\\tool_wp\\importer\\departments_csv, tool_organisation\\tool_wp\\importer\\positions_csv)"
}
</code>

At the moment of writing this, there are two CSV importers in the Moodle Workplace distribution:
* tool_organisation\tool_wp\importer\positions_csv
* tool_organisation\tool_wp\importer\departments_csv

More importers may be added later to the Moodle Workplace and also more importers may be implemented by the plugins.

Let's execute the same web service '''tool_wp_perform_import''' specifying the positions importer:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
> --data 'wsfunction=tool_wp_perform_import&file=880413439&importer=tool_organisation\tool_wp\importer\positions_csv&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
> | jq

{
"id": 0,
"settings": [
{
"name": "target_framework",
"value": "new"
},
{
"name": "hierarchy",
"value": "selected"
},
{
"name": "identifier",
"value": "idnumber"
},
{
"name": "csvmapping:name",
"value": "name"
},
{
"name": "csvmapping:idnumber",
"value": "idnumber"
},
{
"name": "csvmapping:description",
"value": "description"
},
{
"name": "csvmapping:descriptionformat",
"value": ""
},
{
"name": "csvdefault:descriptionformat",
"value": "1"
},
{
"name": "csvmapping:parentid",
"value": "parent"
},
{
"name": "csvmapping:globalmanager",
"value": "manager"
},
{
"name": "csvmapping:departmentmanager",
"value": ""
},
{
"name": "select_framework",
"value": null
}
]
}
</code>

The mapping of columns in the CSV file is picked automatically in the most cases, however the column "'''ismanager'''" was not mapped because the importer expects it to be called '''globalmanager''' (or '''manager'''). We can correct the mapping by adding to the request: settings[0][name]=csvmapping:globalmanager&settings[0][value]=ismanager

=== Scheduling import ===

Now we can execute the tool_wp_perform_import web service without dryrun parameter. The result will return the import id:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&file=880413439&settings[0][name]=csvmapping:globalmanager&settings[0][value]=ismanager&importer=tool_organisation\tool_wp\importer\positions_csv&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 56,
"settings": [
...
{
"name": "csvmapping:globalmanager",
"value": "ismanager"
},
...
]
}
</code>

The next cron run will execute this import.

=== Retrieving the import logs ===

Currently you can only see the import logs via the web interface. We will add a new web service for it soon.

[[File:wp_ws_import_log_example.png]]

=== Additional parameters ===

Additionally, the tool_wp_perform_import web service has parameters:
* tenant (int|string) - Database ID or non-numeric idnumber of the tenant where the import should be made
* notenant (bool) - Perform import without the tenant (only for importers that support this).

They can be used by global administrator or another user who has permission to switch between tenants.

Migration Web services

2021-01-15T20:07:16Z

Marina.glancy: /* Retrieving the import logs */

{{Workplace}}

== Overview ==
Web services for the Moodle Workplace [[Migrations]] feature.

The following web services are available in the Moodle Workplace for export and import:
* tool_wp_perform_export
* tool_wp_perform_import
* tool_wp_retrieve_export_file

Standard Moodle LMS functionality is available for uploading a file, see [https://docs.moodle.org/dev/Web_services_files_handling Web services files handling]

To see the exact description of the parameters and return values of these web services in your version of Moodle Workplace, please turn on the admin setting '''$CFG->enablewsdocumentation''' and navigate to '''Site administration > Plugins > Web services> API Documentation'''

== Set up ==

* Create a new service with the functions: '''tool_wp_perform_export''', '''tool_wp_perform_import''', '''tool_wp_retrieve_export_file''' or add these functions to the existing service
* Allow this service for everybody or for users who you want to be able to use them
* Create tokens for the users, enable protocols, add capabilities to use protocols

See more information under [[Using web services]]

== Export ==

The following examples use command-line calls using the REST protocol. The output is piped through '''jq''' command to display JSON in a more readable way. There are many ways to call web-services and there are other alternatives of how to parse JSON. Adjust commands as needed. Do not forget to replace the site name and the token with your token.

=== Dry run ===

First execute the web-service tool_wp_perform_export with the parameter dryrun=1, it will validate input, show some information but will not actually schedule an export. You must pass parameter exporter. If the exporter is not available the error message will be displayed. The error message contains the list of all available exporters. For example:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"exception": "invalid_parameter_exception",
"errorcode": "invalidparameter",
"message": "Invalid parameter value detected (Could not find exporter ''\nChoose from: tool_certification\\tool_wp\\exporter\\certifications, tool_dynamicrule\\tool_wp\\exporter\\rules, tool_organisation\\tool_wp\\exporter\\jobs, tool_organisation\\tool_wp\\exporter\\orgstructure, tool_program\\tool_wp\\exporter\\programs, tool_reportbuilder\\tool_wp\\exporter\\customreports, tool_tenant\\tool_wp\\exporter\\tenants, tool_wp\\tool_wp\\exporter\\certificates, tool_wp\\tool_wp\\exporter\\cohorts, tool_wp\\tool_wp\\exporter\\coursecategories, tool_wp\\tool_wp\\exporter\\courses, tool_wp\\tool_wp\\exporter\\site, tool_wp\\tool_wp\\exporter\\users)"
}
</code>

Now try again with the exporter name:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=tool_organisation\tool_wp\exporter\orgstructure&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 0,
"settings": [
{
"name": "export_instances",
"value": "all"
},
{
"name": "select_frameworks",
"value": ""
}
]
}
</code>

Because it is a dry-run, the id=0 is returned (export was not actually scheduled). The web service also returns the list of settings that will be applied to the export. You may wish to change some of these settings, for example, we can export only positions by adding '''&settings[0][name]=export_instances&settings[0][value]=positions''' to the URL (to pass more settings use a different index).

=== Schedule export ===

Call the web service tool_wp_perform_export without the dryrun=1 parameter. For example:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_export&exporter=tool_organisation\tool_wp\exporter\orgstructure&settings[0][name]=export_instances&settings[0][value]=positions&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 19,
"settings": [
{
"name": "export_instances",
"value": "positions"
},
{
"name": "select_frameworks",
"value": ""
}
]
}
</code>

This call returned id 19, we will need it in the next command

=== Retrieve export file ===

After the next cron run on the server you can retrieve the export file. If the cron has not run yet this command will return an error "Export not ready". Successful return will look like this:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_retrieve_export_file&exportid=19&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

[
{
"filename": "organisation-structure-frameworks-export-20210115-1534.zip",
"filepath": "/",
"filesize": 3396,
"fileurl": "https://SITENAME/webservice/pluginfile.php/1/tool_wp/export/19/organisation-structure-frameworks-export-20210115-1534.zip",
"timemodified": 1610721298,
"mimetype": "application/zip",
"isexternalfile": false
}
]
</code>

To retrieve the file you need to add your token to the fileurl:

<code>
$ curl https://SITENAME/webservice/pluginfile.php/1/tool_wp/export/19/organisation-structure-frameworks-export-20210115-1534.zip?token=cf3788edbe41d7a89e963d9432b15331 > exportfile.zip
</code>

=== Additional parameters ===

Additionally, the tool_wp_perform_export web service has parameters:
* tenant (int|string) - Database ID or non-numeric idnumber of the tenant where the export should be made
* notenant (bool) - Perform export without the tenant (only for exporters that support this).

They can be used by global administrator or another user who has permission to switch between tenants.

== Import ==

The web service '''tool_wp_perform_import''' is responsible for importing.

You can perform an import from an export file or upload a local file. To perform import from an export file add '''exportid=19''' to the parameters. To perform import from a file you need to first upload a file and then use a draft item id as an argument, for example '''file=123456678''' . Similar to the export, you can use '''dryrun=1''' parameter to validate parameters without actually scheduling import.

=== Upload file ===

In this example we upload a local file '''positions.csv.''' It will be placed in a draft area for the current user. The script returns itemid of the draft area. It can be used only by the same user and will be automatically deleted by Moodle after two days.

Imagine we have a file with the name '''positions.csv''' with the following contents:

<code>
idnumber,parent,name,description,ismanager
CEO,,Chief Executive Officer,Chief Executive Officer position,1
COO,CEO,Chief Operating Officer,Chief Operating Officer position,1
HMD,COO,Head of Marketing and Design,Head of Marketing and Design position,1
MCO,HMD,Marketing Consultant,Marketing Consultant position,0
OM,COO,Office Manager,Office Manager position,0
</code>

''Note: For the purpose of this tutorial we called the last column "ismanager". If you call it "manager" or "globalmanager" you will not need to change the mapping.''

Standard Moodle LMS functionality is available for uploading a file, see [https://docs.moodle.org/dev/Web_services_files_handling Web services files handling], for example:

<code>
$ curl -X POST -F "image=@positions.csv" https://SITENAME/webservice/upload.php?token=cf3788edbe41d7a89e963d9432b15331 \
| jq

[
{
"component": "user",
"contextid": 567,
"userid": "123",
"filearea": "draft",
"filename": "positions.csv",
"filepath": "/",
"itemid": 880413439,
"license": "allrightsreserved",
"author": "User User",
"source": "O:8:\"stdClass\":1:{s:6:\"source\";s:13:\"positions.csv\";}"
}
]
</code>

=== Dry-run ===

Example importing the export with id 19:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&exportid=19&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq
</code>

Example importing the file that is located in the draft area with itemid 880413439. This is a CSV file and there are several available importers, therefore an error will be raised. The error message will contain the list of available importers:

<code>
curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&file=880413439&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"exception": "invalid_parameter_exception",
"errorcode": "invalidparameter",
"message": "Invalid parameter value detected (More than one importer is available, importer must be specified\nChoose from: tool_organisation\\tool_wp\\importer\\departments_csv, tool_organisation\\tool_wp\\importer\\positions_csv)"
}
</code>

At the moment of writing this, there are two CSV importers in the Moodle Workplace distribution:
* tool_organisation\tool_wp\importer\positions_csv
* tool_organisation\tool_wp\importer\departments_csv

More importers may be added later to the Moodle Workplace and also more importers may be implemented by the plugins.

Let's execute the same web service '''tool_wp_perform_import''' specifying the positions importer:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
> --data 'wsfunction=tool_wp_perform_import&file=212744242&importer=tool_organisation\tool_wp\importer\positions_csv&dryrun=1&wstoken=cf3788edbe41d7a89e963d9432b15331' \
> | jq

{
"id": 0,
"settings": [
{
"name": "target_framework",
"value": "new"
},
{
"name": "hierarchy",
"value": "selected"
},
{
"name": "identifier",
"value": "idnumber"
},
{
"name": "csvmapping:name",
"value": "name"
},
{
"name": "csvmapping:idnumber",
"value": "idnumber"
},
{
"name": "csvmapping:description",
"value": "description"
},
{
"name": "csvmapping:descriptionformat",
"value": ""
},
{
"name": "csvdefault:descriptionformat",
"value": "1"
},
{
"name": "csvmapping:parentid",
"value": "parent"
},
{
"name": "csvmapping:globalmanager",
"value": "manager"
},
{
"name": "csvmapping:departmentmanager",
"value": ""
},
{
"name": "select_framework",
"value": null
}
]
}
</code>

The mapping of columns in the CSV file is picked automatically in the most cases, however the column "'''ismanager'''" was not mapped because the importer expects it to be called '''globalmanager''' (or '''manager'''). We can correct the mapping by adding to the request: settings[0][name]=csvmapping:globalmanager&settings[0][value]=ismanager

=== Scheduling import ===

Now we can execute the tool_wp_perform_import web service without dryrun parameter. The result will return the import id:

<code>
$ curl 'https://SITENAME/webservice/rest/server.php?moodlewsrestformat=json' \
--data 'wsfunction=tool_wp_perform_import&file=212744242&settings[0][name]=csvmapping:globalmanager&settings[0][value]=ismanager&importer=tool_organisation\tool_wp\importer\positions_csv&wstoken=cf3788edbe41d7a89e963d9432b15331' \
| jq

{
"id": 56,
"settings": [
...
{
"name": "csvmapping:globalmanager",
"value": "ismanager"
},
...
]
}
</code>

The next cron run will execute this import.

=== Retrieving the import logs ===

Currently you can only see the import logs via the web interface. We will add a new web service for it soon.

[[File:wp_ws_import_log_example.png]]

=== Additional parameters ===

Additionally, the tool_wp_perform_import web service has parameters:
* tenant (int|string) - Database ID or non-numeric idnumber of the tenant where the import should be made
* notenant (bool) - Perform import without the tenant (only for importers that support this).

They can be used by global administrator or another user who has permission to switch between tenants.

File:wp ws import log example.png

2021-01-15T20:06:16Z

Marina.glancy:

2021-01-15T19:38:08Z

Marina.glancy:

Migration Web services

2021-01-15T19:31:02Z

Marina.glancy: /* Overview */

2021-01-15T14:36:58Z

Marina.glancy:

2020-12-01T12:56:19Z

Marina.glancy: Created page with "{{Workplace}} * Allows to control authentication settings inside the current tenant in the Workplace Multi-tenancy feature * This capability may only be applied in the sy..."

{{Workplace}}

* Allows to control authentication settings inside the current tenant in the Workplace [[Multi-tenancy]] feature
* This capability may only be applied in the system context.
* The default [[Tenant administrator role]] has this capability set to allow in the new installations, however it is not allowed automatically in the sites upgraded from a version below 3.10 for security reasons

==See also==

* [[Moodle Workplace]]
* [[Multi-tenancy]]

[[Category:Capabilities]]

Multi-tenancy capabilities

2020-11-05T10:33:46Z

Marina.glancy:

{{Workplace}}
{{Work in progress
|info = This page will apply to the version 3.10 of Moodle Workplace
}}

Workplace and core capabilities and how they affect permissions to work with users

{| class="wikitable" border="1"
|-
! Capability
! Description
! Tenant admin
|-
| [[Capabilities/tool/tenant:manage|tool/tenant:manage]]
| Can browse users in any tenant
|
|-
| tool/tenant:allocate
| Can see all tenants, browse users in all tenants, move users between tenants
|
|-
| tool/tenant:manageusers
| Can browse, edit, delete, suspend users in the current tenant or its sub-tenants [https://tracker.moodle.org/browse/WP-1124 WP-1124]
|
|-
| tool/tenant:browseusers
| Can browse users in the current tenant or its sub-tenants
| Yes
|-
| tool/tenant:authconfig
| Can edit authentication settings in the current tenant and its sub-tenants
| Yes
|-
| moodle/restore:createuser
|
| No [https://tracker.moodle.org/browse/WP-929 WP-929]
|-
| moodle/site:viewuseridentity
|
| Yes
|-
| moodle/site:uploadusers
|
| Yes
|-
| moodle/user:create
|
|
|-
| moodle/user:delete
|
|
|-
| moodle/user:update
|
|
|-
| moodle/user:viewdetails
|
|
|-
| moodle/user:viewalldetails
|
| Yes
|-
| moodle/user:viewlastip
|
|
|-
| moodle/user:viewhiddendetails
|
|
|-
| moodle/user:loginas
|
|
|-
| moodle/user:managesyspages
|
|
|-
| moodle/user:manageblocks
|
|
|-
| moodle/user:manageownblocks
|
|
|-
| moodle/user:manageownfiles
|
|
|-
| moodle/my:configsyspages
|
|
|-
| moodle/course:reviewotherusers
|
|
|-
| moodle/course:bulkmessaging
|
|
|-
| moodle/course:viewhiddenuserfields
|
|
|-
| moodle/site:viewparticipants
|
| No [https://tracker.moodle.org/browse/WP-1520 WP-1520]
|-
| moodle/user:editprofile
|
|
|-
| moodle/badges:awardbadge
|
| Yes
|-
| moodle/badges:revokebadge
|
|
|-
| moodle/badges:viewawarded
|
| Yes
|-
| moodle/site:messageanyuser
|
|
|-
| moodle/role:assign
|
| Yes
|-
|
|
|
|-
|
|
|
|}