✨ Frequently Asked Question
This article forms part of our Inclusion Module FAQ series.
Overview
Yes. The Inclusion Module allows permissions to be configured at role level, enabling Centres to define default access settings that are automatically applied to users.
This helps ensure consistent access across your organisation and reduces the need to configure permissions individually for each user.
How Default Permissions Work
Permissions are typically configured against user roles, such as:
- Centre Manager
- Assessor
- Employer
- Learner
- Support Coordinator
Once permissions are assigned to a role, all users assigned to that role automatically inherit those settings.
This means Centres can manage access centrally without needing to update every user account individually.
Available Permission Levels
Each area of the Inclusion Module can be configured using the following permission levels:
- Inherit
- No Access
- Read Only
- Read/Write
Permissions can be applied separately to different areas of the module, allowing Centres to control access to specific functionality.
Can Permissions Be Overridden for Individual Users?
Yes. Although role permissions provide the default configuration, Centres can apply user-specific permission overrides where required.
This is useful when a particular user needs more or less access than others within the same role.
⚠️ Important: User-level permission overrides take precedence over role-level settings.
Can Visibility Be Set by Learner?
Visibility settings for individual records can be managed on a learner-by-learner basis.
For example, when creating a Barrier to Learning, Support Need, or Support Plan, you can decide whether that specific record is visible to:
- Learners
- Employers
These visibility settings are applied to individual records and are separate from the role permissions that control access to the module itself.
What Is the Default Learner Access Setting?
Learner access to the Inclusion Module is disabled by default.
This means learners cannot access Inclusion functionality until access has been explicitly enabled.
This helps Centres configure permissions and visibility settings before making the module available to learners.
Example
A Centre may configure default permissions as follows:
- Assessors – Read/Write access to learner support areas.
- Support Coordinators – Full access to support records and notifications.
- Employers – Read Only access to approved support information.
- Learners – No Access until enabled.
If one Assessor requires additional permissions, a user-level override can be applied without affecting the permissions of other Assessors.
Tips & Notes
- Permissions should generally be managed at role level wherever possible.
- User-level overrides should only be used where an exception is required.
- Learner access is disabled by default.
- Record visibility settings are separate from role permissions.
- Inherited permissions help maintain consistency across your Centre.
Terminology
The terminology used in this article may differ depending on your Centre’s configuration.
Related Articles
- Can Inclusion Information Be Hidden from Learners?
- Can Inclusion Information Be Hidden from Employers?
- Turning on the Inclusion Module and Controlling Access
Need Help?
If you need assistance, please contact Onefile Support or your internal support team.