Rights by role

Who can do what in the ERP. 49 rights in 9 domains, 13 roles: all of them are in the table. A person can hold several roles — a board member who is also an instructor gets the rights of both.

Legend

● granted · ◐ granted, limited to the committees the person heads or deputises · empty: not granted. The Super-administrator is a technical role reserved to the ERP maintainer: it holds every right and is given to nobody else.

The matrix

Right	Bureau	Treasurer	Administrative	Chief pilot	Committee	Committee head	Instructor	Maintenance	Duty officer	Employee	Audit	Club admin
Members
View members	●	●	●	●	●	●
Manage members records, registrations, portal password, anonymisation	●		●
Configure registrations documents, required pieces, deadlines	●		●
Email members	●		●
Validate duty desk and expense claims and reimburse expense claims		●	●
Manage committees	●					◐
Register a visiting pilot external file, FFVP no., right to fly			●	●			●		●
Force the end date of a registration from a member's edit form
Manage the flying functions (instructors, activity managers, winch)				●
Flights
View flights	●	●	●	●	●		●				●
Manage flight billing		●	●
Correct a flight record create or rewrite directly in the ERP	●		●	●			●
Sync with GesAsso			●	●
Sync with OSRT			●	●
Trial flights
View trial flights	●		●	●	●		●				●
Manage vouchers and types			●	●
Schedule trial flights dates, notes, flight links	●		●	●			●
Import HelloAsso payments			●	●
Collect, bill, refund a voucher and convert to a member			●
Equipment and fuel
View equipment	●	●	●	●	●		●	●			●
Manage equipment		●
Change the status and maintenance information status, CEN expiry, last APRS, notes — without editing the asset				●				●
View fuel	●		●	●	●		●	●
Record fuel			●
Correct a fuel entry already recorded			●	●
Finance
View finance entries, ledger, reports	●	●	●		●						●
Prepare the accounts drafts, cheque remittances, imports, reversals		●	●
Post an entry final lock		●
Validate and issue invoices sales invoices and credit notes	●	●
Bank reconciliation		●
Accounting settings chart of accounts, journals, year-end close		●
Close and reopen a fiscal year carry-forward entries		●
Manage the budget	●	●	●
View prices	●	●	●
Manage prices		●
Prepare a tax receipt	●		●
Sign tax receipts	●
Human resources
View HR profiles, balances, attendance	●		●		●
Manage HR	●
Approve leave	●
File and follow own leave requests										●	●
Club planning
View the club planning	●		●	●	●	●	●		●		●
Manage the planning courses, lessons, duty desks	●		●		●	◐
Keep the list of planning resources rooms, hangar, bookable machines												●
Planche
Day-to-day operations logbook, presences, today's flights	●		●	●			●		●
Configure Planche				●								●
Platform
Manage accounts and roles												●
System settings email, storage, HelloAsso, log purge												●
Read the sign-in log												●

Own leave requests are reserved to employees (Employee role) and Audit. The member portal has its own sign-in and depends on no right. The Committee head and Duty officer roles are club-specific and are not part of the validated reference matrix.

What sets the roles apart

• The club administrator manages accounts, roles, settings and the sign-in log. They do not do day-to-day operations (members, flights, accounting): each person has a business role.
• The administrative role prepares, the treasurer posts. The administrative role enters draft entries and creates cheque remittances; only the treasurer posts them for good and reconciles the bank.
• The bureau finds the tax receipts to sign, approves the budget and leave; they can read every domain without editing records or accounts.
• The committee reads members, flights, VI, assets, fuel, finance and HR, and manages the planning.
• Audit reads flights, VI, assets, finance and the planning, and changes nothing.
• A committee head manages the record, members and activities of their own committees only.
• Reading human resources is limited to the bureau, the administrative role and the committee.
• The club planning is managed by the bureau, the administrative role and the committee for the whole club, and by each committee head for their own activities.
• A Reports menu gathers the reports by domain (finance, members, machines, activity); each tab is visible to whoever can read the domain.

Who manages access

In Administration → Utilisateurs, the administrator picks each person's role(s) and, for committee heads and deputies, the committees concerned. In Administration → Rôles, each role is a matrix of checkboxes by domain. An administrator can only grant rights they hold themselves; the Super-administrator role is a system role, and the rights catalogue is defined by the application (view-only in the interface).

Default rights only apply when a role is created: a right that is removed does not come back at restart.

• Closing a fiscal year is a right of its own, held by the treasurer.
• An asset's status and maintenance information can be changed by maintenance and the chief pilot without the right to edit the asset itself.
• Fuel and Duty are sub-menus of Machines and Finance.