User policies: Difference between revisions
Helen Foster (talk | contribs) m (Tsala moved page Roles settings to User policies over redirect) |
Paul Holden (talk | contribs) m (Document 255 character limit on user profile fields.) |
||
| (18 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{Roles}} | {{Roles}} | ||
==User policies== | ==User policies== | ||
The following settings may be changed by an administrator in '' | The following settings may be changed by an administrator in ''User policies'' in the Site administration. | ||
===Role for visitors=== | ===Role for visitors=== | ||
| Line 9: | Line 9: | ||
This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password. | This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password. | ||
(If you wish to deny guest access to a site altogether, the guest login button should be set to hide in ''Manage authentication'' in the Site administration.) | |||
===Default role for all users=== | ===Default role for all users=== | ||
| Line 17: | Line 15: | ||
It is recommended that the default role for all users is set to [[Authenticated user]]. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none. | It is recommended that the default role for all users is set to [[Authenticated user]]. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none. | ||
Note: It is not recommended that the default role for all users is set to student | Note: It is not recommended that the default role for all users is set to student. | ||
===Creators' role in new courses=== | |||
Moodle will automatically enroll the user creating a new course in the course with the role specified in this setting. Moodle checks that the role used for creating the course e.g. "Course creator" has the right to assign the specified role in the new course. This means that the following capabilities needs to be set on the course creator role before the user is enrolled automatically : | |||
* moodle/course:create | Allow | |||
* moodle/course:manageactivities | Allow | |||
* moodle/course:viewparticipants | Allow | |||
* moodle/role:assign | Allow | |||
If the course creator role is not setup correctly the user will be enrolled in the course without any roles. | |||
===Auto-login guest=== | ===Auto-login guest=== | ||
| Line 23: | Line 30: | ||
If not set, then visitors must click the "Login as a guest" button before entering a course which allows [[Guest|guest access]]. | If not set, then visitors must click the "Login as a guest" button before entering a course which allows [[Guest|guest access]]. | ||
Note: If auto-login guest is set, the guest login button also needs to be set to show | Note: If auto-login guest is set, the guest login button also needs to be set to show in ''Manage authentication'' in the Site administration, even though visitors won't necessarily use it. | ||
===Hide user fields=== | ===Hide user fields=== | ||
| Line 37: | Line 44: | ||
Any of the following fields may be shown to users with the capability [[Capabilities/moodle/site:viewuseridentity|moodle/site:viewuseridentity]] when searching for users and displaying lists of users. | Any of the following fields may be shown to users with the capability [[Capabilities/moodle/site:viewuseridentity|moodle/site:viewuseridentity]] when searching for users and displaying lists of users. | ||
This setting is useful for sites with large number of users, where the likelihood of users with the same name is high. | |||
*Username | |||
*ID number | *ID number | ||
*Email address | *Email address | ||
| Line 43: | Line 53: | ||
*Department | *Department | ||
*Institution | *Institution | ||
*City/town | |||
*Country | |||
{{New features}}New in 3.11: Custom profile fields (shown with an asterisk against their name) may now be selected to appear in certain locations. Note that only "Text input" fields are currently supported, and that their character limit must not exceed 255. | |||
Locations where user identity fields are shown are as follows: | Locations where user identity fields are shown are as follows: | ||
| Line 50: | Line 63: | ||
*User selectors ([[Assign roles]] in some places, [[Groups|groups]], forum subscribers) | *User selectors ([[Assign roles]] in some places, [[Groups|groups]], forum subscribers) | ||
*[[Browse list of users]] | *[[Browse list of users]] | ||
* | *[[Participants]] | ||
*[[Gradebook|Grader report]] | *[[Gradebook|Grader report]] | ||
*[[Quiz reports]] | *[[Quiz reports]] | ||
| Line 57: | Line 70: | ||
*[[Using Course completion|Course completion report]] | *[[Using Course completion|Course completion report]] | ||
*[[Using Activity completion|Activity completion report]] | *[[Using Activity completion|Activity completion report]] | ||
Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two fields otherwise tables become very wide. | Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two fields otherwise tables become very wide. | ||
| Line 63: | Line 75: | ||
===Full name format=== | ===Full name format=== | ||
See [[Additional name fields]] for details, also about the alternative full name format | See [[Additional name fields]] for details, also about the alternative full name format. | ||
===Maximum users per page=== | ===Maximum users per page=== | ||
| Line 71: | Line 83: | ||
===Enable Gravatar=== | ===Enable Gravatar=== | ||
[http://gravatar.com/ Gravatar] (an abbreviation for globally recognized avatar) is a service for providing globally | [http://gravatar.com/ Gravatar] (an abbreviation for globally recognized avatar) is a third party service for providing globally personal avatars. | ||
If Gravatar service is enabled by the administrator and a user has not uploaded any user picture, Moodle will check whether the user's email address has an associated gravatar account and if so, will use the gravatar as the user's picture. | |||
===Gravatar default image URL=== | ===Gravatar default image URL=== | ||
If gravatars are enabled, an alternative default user picture may be specified. The options are: | |||
* A gravatar default image - by entering a code such as mm | * A gravatar default image - by entering a code such as ''mm'' or ''identicon'' - See https://en.gravatar.com/site/implement/images/ for codes of other gravatar default images. | ||
* A specified image - by entering the image URL | * A specified image - by entering the image URL | ||
| Line 90: | Line 100: | ||
Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context. | Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context. | ||
Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments | Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments. | ||
In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur. | In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur. | ||
[[Category:Site administration]] | [[Category:Site administration]] | ||
| Line 125: | Line 109: | ||
[[fr:Réglages des rôles]] | [[fr:Réglages des rôles]] | ||
[[ja:ユーザポリシー]] | [[ja:ユーザポリシー]] | ||
[[es: | [[es:Políticas para el usuario]] | ||
Latest revision as of 10:54, 28 March 2022
User policies
The following settings may be changed by an administrator in User policies in the Site administration.
Role for visitors
Users who are not logged in to the site will be treated as if they have the role specified here, granted to them at the site context. The role of Guest is the default and the recommended setting for standard Moodle sites. The user will still be required to login to participate in an activity.
Role for guest
This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password.
(If you wish to deny guest access to a site altogether, the guest login button should be set to hide in Manage authentication in the Site administration.)
Default role for all users
It is recommended that the default role for all users is set to Authenticated user. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none.
Note: It is not recommended that the default role for all users is set to student.
Creators' role in new courses
Moodle will automatically enroll the user creating a new course in the course with the role specified in this setting. Moodle checks that the role used for creating the course e.g. "Course creator" has the right to assign the specified role in the new course. This means that the following capabilities needs to be set on the course creator role before the user is enrolled automatically :
- moodle/course:create | Allow
- moodle/course:manageactivities | Allow
- moodle/course:viewparticipants | Allow
- moodle/role:assign | Allow
If the course creator role is not setup correctly the user will be enrolled in the course without any roles.
Auto-login guest
If not set, then visitors must click the "Login as a guest" button before entering a course which allows guest access.
Note: If auto-login guest is set, the guest login button also needs to be set to show in Manage authentication in the Site administration, even though visitors won't necessarily use it.
Hide user fields
The following user fields appear on users' profile pages. Certain user fields are also listed on the course participants page. You can increase student privacy by hiding selected user fields.
Description, city/town, country, web page, ICQ number, Skype ID, Yahoo ID, AIM ID, MSN ID, last access, My courses and first access and groups
- User fields on users' profile pages are hidden from all users with the capability moodle/user:viewhiddendetails not set.
- User fields on the course participants page are hidden from all users with the capability moodle/course:viewhiddenuserfields not set.
Show user identity
Any of the following fields may be shown to users with the capability moodle/site:viewuseridentity when searching for users and displaying lists of users.
This setting is useful for sites with large number of users, where the likelihood of users with the same name is high.
- Username
- ID number
- Email address
- Phone number
- Mobile phone
- Department
- Institution
- City/town
- Country
New feature
in Moodle 3.11!
New in 3.11: Custom profile fields (shown with an asterisk against their name) may now be selected to appear in certain locations. Note that only "Text input" fields are currently supported, and that their character limit must not exceed 255.
Locations where user identity fields are shown are as follows:
- User selectors (Assign roles in some places, groups, forum subscribers)
- Browse list of users
- Participants
- Grader report
- Quiz reports
- SCORM reports
- Assignment submissions
- Course completion report
- Activity completion report
Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two fields otherwise tables become very wide.
Full name format
See Additional name fields for details, also about the alternative full name format.
Maximum users per page
You can choose here the maximum number of users to be displayed when searching in courses, groups, cohorts etc. The default is 100 but if your Moodle site is very large you can increase the number here.
Enable Gravatar
Gravatar (an abbreviation for globally recognized avatar) is a third party service for providing globally personal avatars.
If Gravatar service is enabled by the administrator and a user has not uploaded any user picture, Moodle will check whether the user's email address has an associated gravatar account and if so, will use the gravatar as the user's picture.
Gravatar default image URL
If gravatars are enabled, an alternative default user picture may be specified. The options are:
- A gravatar default image - by entering a code such as mm or identicon - See https://en.gravatar.com/site/implement/images/ for codes of other gravatar default images.
- A specified image - by entering the image URL
If the field is left empty then the theme's default user picture is used.
Unsupported role assignments
Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context.
Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments.
In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur.
