Understanding Users, Roles and Access

Not everyone in an institute needs access to every record or administrative function. bACEic access should reflect each person’s responsibilities. The roles and permissions available to an institute depend on the product configuration.

Users and roles

A user is a person who has an account to access bACEic.
A role represents a set of responsibilities or access permissions.
Permissions determine which areas or actions a user can access, where the product supports that level of control.
An institute administrator is typically responsible for coordinating access, subject to the permissions granted to that account.

Common user groups

Institute owner or administrator: oversees institute configuration and operations where authorised.
Teacher or academic staff: accesses the teaching and learning functions assigned to them.
Admissions or operations staff: works with enquiries, student records or operational tasks assigned to them.
Student or parent: accesses only the relevant learner-facing information and features, where those accounts are supported.

Good access-management practices

Give each person an individual account rather than sharing one login.
Assign access based on the person’s actual responsibilities.
Review access when someone changes role or leaves the institute.
Do not share student, parent, financial or other restricted information with people who do not need it.
Ask an authorised administrator to make access changes rather than attempting to use another person’s account.

Why can’t I see a feature or record?

The feature may not be enabled for your institute.
Your role may not include permission to view or manage it.
The record may belong to a different program, batch or scope.
A filter or status selection may be hiding the record.

What to include when requesting access

Tell the administrator which task you need to perform, which section you need, and why it is required. Do not send your password or ask another user to share their account.