Understanding Permissions

Nimbu operates on a Role-Based Access Control system, ensuring that every user has the exact level of access required for their specific duties. By assigning roles: Admin, Trainer, Content Editor, or Student - Administrators can maintain a secure environment where sensitive compliance, financial, and student data are only accessible to authorised personnel.

This system is designed to be both rigid for security and flexible for operational needs, allowing for granular permission adjustments at the individual user level.

What's Covered in This Article

This article breaks down Nimbu's permission hierarchy and explains how to tailor access for each member of your team.

Admin Permissions: Managing the "Command Centre" of the RTO.
Trainer Permissions: Facilitating delivery and student progress.
Editor Permissions: Architecting the curriculum and content assets.
Customisation: How to adjust individual permissions beyond the default role.

Administrator Permissions

The Admin role is the highest level of access, typically reserved for RTO Managers and System Owners.

Security Note: Two permissions: Billing & Subscriptions and Login as User are treated as sensitive and default to off when the Admin role is first assigned. Only the organisation owner can grant these permissions to other Admins.

Key controllable Admin permissions include:

User Management: The ability to add, edit, or deactivate other users. Includes the Login as User permission, which allows an Admin to access the platform as another user for troubleshooting and account setup purposes.
RTO & Brand Settings: Controls for official RTO details and the visual look and feel of the platform, including logos, colours, and domain settings.
Engagement Metrics: Access to high-level dashboards showing class health and student engagement levels.
Billing & Subscriptions: Oversight of the Nimbu subscription, invoices, and Stripe Connect payment integrations.
Integrations: Manage third-party tool connections, including LTI integrations such as Evokio.
AVETMISS: Access to export AVETMISS compliance data for regulatory reporting.
Microsite: Manage the public-facing microsite, including Online Registration settings and course listings.

Trainer Permissions

Trainer permissions are centered around the "Live Learning" phase of the Nimbu hierarchy.

Key controllable Trainer permissions include:

Student Management: Permissions to view student progress, add and edit student details, and manage student enrolments in classes.
Class & Webinar Management: The ability to activate and deactivate classes, add units to a class, and manage live webinar sessions.
Course Subscriptions: Access to view and manage student subscription information for courses.
Marking: The critical permission to evaluate student submissions and assign final results.

Content Editor Permissions

The Content Editor role is designed for curriculum developers and instructional designers.

Key controllable Editor permissions include:

Course & Unit Management: The ability to access the course registry, create new courses, and remove outdated ones. This permission also covers duplicating existing courses to create new variations.
Unit Management: The ability to build and manage units, including creating new draft versions of published units. This permission also covers unit duplication.
Resource Management: Permissions to manage the Content Library, including uploading learning materials and creating assessments and observations.

Customising Permissions per User

Nimbu does not force you into "one-size-fits-all" roles. You can customise permissions for each individual to fit their unique job description.

Hybrid Roles: A single user can hold multiple roles simultaneously. For example, a staff member who both delivers training and builds content can be assigned both the Trainer and Content Editor roles.
Feature Toggles: Within any role, individual permissions can be switched on or off. For example, you may allow a Trainer to view all student progress but restrict their ability to mark submissions.
Internal Notes: Each user profile includes an Internal Note field — a general-purpose space for Admins to record any relevant information about the user, such as their position, access history, or other context useful for the team.