Skip to main content
GullySystem
Financial services

Roles and Permissions for Cooperative banks

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

Tellers post cash, the manager approves loans, and auditors only read. Committee members see loan files but not other members’ passbooks. Every login is tied to one named person.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Cooperative banks

How the business operates.

A cooperative bank serves a membership that knows its staff by name. Account holders are also owners, so a share certificate, a savings book, a recurring deposit and a loan guaranteed by a neighbour can all belong to one person. The board is elected from the members. Reports go to the general body and to the supervisory authority, each in a different format and on a different date.

Member register and share capital

Hold each member once, with share holdings, nominee, occupation and linked accounts, and record allotments, transfers and withdrawals.

Savings and current accounts

Post deposits and withdrawals by branch, keep passbook and statement history, and flag dormant accounts for follow-up.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Member register and nominees. One person, one record. Address, occupation, nominee, joint holders and every linked account are held together, with each change dated and attributed to the clerk who made it.
  • Share capital ledger. Record allotments, transfers and refunds on withdrawal. Paid-up capital is then compared against the ceiling in the bye-laws and the limits the registrar has set for the bank.
  • Savings and current accounts. Post deposits and withdrawals, print passbook lines, record cheque leaf issues and produce statements. Accounts untouched beyond the dormancy period you set are listed as inoperative for the manager to review.
  • Term and recurring deposits. Lien marks. A deposit that backs a loan carries one on its receipt. Maturity, auto-renewal and premature closure are tracked, and interest is worked on the compounding cycle your scheme offers, quarterly or at maturity.

Operational bottlenecks to check

Share capital sits apart from accounts

Shares sit in a ledger, savings in a core system and the loan in a file. One question needs three lookups.

Daily collections reach the books late

Agents hand in a sheet at the end of the beat. Entries are keyed the next morning, so a member’s balance shows yesterday’s figure.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Membership

    Enrol first. A new member is entered with a nominee, any joint holder and an opening share allotment, then a savings account is opened and linked to that person.

  2. 2. Deposits

    Counter or agent. Deposits arrive at the teller window or through an agent, and each fixed or recurring deposit receipt prints the maturity date and the renewal instruction.

  3. 3. Loan application

    Members apply. They name sureties and offer a plot, a vehicle or a pledged deposit as security. The officer files the valuation, the income papers and a note on repayment capacity.

  4. 4. Committee decision

    The committee reads the file. Approval, conditions and directors present are recorded in one entry, and the sanction letter prints from those terms with no retyping of the amount or the security clause.

  5. 5. Repayment

    Instalments reach the counter or an agent and are set against principal and interest. Accounts that miss a due date fall onto the loan officer’s follow-up list, ranked by age.

  6. 6. Day-end and year-end

    Each branch closes cash and books daily. Year end brings the interest posting. Dividend proposals, auditor schedules and the board pack are all drawn from the ledger entries that the branches already closed.

Industry reports to connect with

  • Deposit position by scheme and branch
  • Fixed and recurring deposits maturing in the next month
  • Overdue loans by age band and asset classification
  • Sureties with combined exposure per member

Questions before implementation.

When should cooperative banks consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements