Skip to main content
Agatabo’s Settings area is your control center for every configuration decision that affects how your organization operates. From establishing the rules that govern loan eligibility to controlling who can view sensitive financial reports, settings determine what Agatabo does and who can do it. Only users with the appropriate permissions can make changes, so the right people stay in control while everyone else works safely within guardrails you define.

The Three Settings Sections

Agatabo organizes its configuration surface into three distinct sections, each with a different focus and a different permission requirement.

Organization Settings

Organization Settings control how your tontine runs day-to-day. Here you configure the organization’s display name, accounting period type, email and SMS notifications, loan policy parameters, and dividend distribution rules. Some fields — like currency, timezone, and decimal precision — are set once at organization creation and remain permanently fixed to protect historical data integrity. Required permission: settings:write to modify; settings:read to view.

Permissions & Access Control

Agatabo uses a role-based access control (RBAC) model. Administrators define roles (for example, Treasurer or Loan Officer), attach a curated set of permission grants to each role, and assign roles to organization members. Every permission operates under either a SELF scope (access to your own data only) or an ANY scope (access to all members’ data). You can create as many custom roles as your organization needs. Required permission: organization_user_roles:write to manage role definitions; organization_user_roles:assign to assign roles to users.

Audit Logs

The Audit Trail captures every CREATE, UPDATE, DELETE, and CONFIGURE action performed in your organization — recording who acted, what resource was affected, when it happened, and whether the operation succeeded or failed. Logs are permanent and immutable; they cannot be deleted by any user. Use the Audit Logs tab to investigate discrepancies, satisfy external auditors, and monitor staff activity. Required permission: audit_logs:read with ANY scope.

Permission Quick Reference

TaskPermission Required
View organization nameNone — visible to all members
Edit organization settingssettings:write
View audit logsaudit_logs:read (ANY scope)
Create or edit role definitionsorganization_user_roles:write
Assign roles to usersorganization_user_roles:assign
Close an accounting periodperiods:close

Common Tasks

Change Your Organization Name

1

Open Settings

Click Settings in the left sidebar. The Organization Settings page opens on the Basic Info tab by default.
2

Edit the name field

Locate the Organization Name field and type the new name.
3

Save your changes

Click Update. The new name takes effect immediately across the entire application — dashboards, reports, and member communications all update at once.

Enable Email Notifications

1

Open Settings

Navigate to Settings in the left sidebar.
2

Find the Notifications section

On the Basic Info tab, locate the Email Notifications toggle.
3

Turn on notifications

Enable the Enable Email toggle.
4

Save

Click Update to apply the change. Agatabo will now send email alerts for loan approvals, payment reminders, and contribution notices to all members who have email addresses on file.
Email notifications require members to have valid email addresses in their profiles and your email service to be configured by your system administrator.
Send a test notification to your own account immediately after enabling the feature. Confirming delivery end-to-end before you rely on it for member communications prevents surprises.

Review Audit Logs

1

Open Settings

Click Settings in the left sidebar.
2

Switch to Audit Logs

Click the Audit Logs tab at the top of the settings page.
3

Filter the log

Use the filter controls to narrow results by actor type, resource type, action type, date range, or keyword search. Combine filters for precision — for example, filter by DELETE action and a specific date range to review all deletions in a given month.
See Audit Trail for the complete filtering and response field reference.

Settings You Cannot Change

A small set of fields is locked after your organization is created. Changing these after transactions have been recorded would corrupt historical data and break accounting records.
SettingWhy It’s Fixed
CurrencyAll recorded transactions, balances, and reports are denominated in this currency — changing it would corrupt every monetary value in the database
Amount scale (decimal precision)Stored amounts would become ambiguous if the precision changed mid-operation
TimezoneHistorical transaction timestamps would become ambiguous if the timezone shifted
Date formatConsistency across all historical records depends on a single, stable format
Organization typeAlways TONTINE — the type determines core system behavior
Organization IDA system-generated identifier referenced by every record in the database
Created dateA historical timestamp that anchors your entire audit history
Verify currency, timezone, and decimal precision before recording any transactions. Once financial records exist, these values cannot be changed. If a correction is needed before any transactions are posted, contact your system administrator immediately — it requires direct database intervention.

Explore Each Settings Area

Organization Settings

Configure your organization name, accounting period, notifications, loan policies, and dividend rules.

Permissions & Access Control

Understand scopes, build roles, assign permissions, and apply the principle of least privilege.

Audit Trail

Filter and interpret the permanent activity log for compliance, security, and troubleshooting.