23 docs tagged with "permissions"

A transaction is any operation implying changes in the balance of an account such as deposits, withdrawals or disbursements. Mambu tracks all transactions and associates them to the clients' accounts where they occurred.

API consumers are an abstraction similar to an OAuth client. The primary purpose of an API consumer is to generate API keys, which are used to authenticate API requests by including them in an apiKey header.

To approve a loan account, select the Approve button, and confirm the dialog box. This will change the account state to Approved, and it will be ready for disbursal as the Disburse button becomes visible.

The audit trail capability tracks all activities that have been performed in the Mambu Core Banking system via the UI or API v1 and v2. Audit records are grouped per tenant. You can search and filter through stored events using a simple API or periodically pull batches of events into your own log management software for further analysis.

The complete Audit Trail V2 API documentation can be found here: Audit Trail V2

Blocking funds in an account essentially means you prevent clients from withdrawing or transferring a specified amount. Clients can still withdraw any remaining funds and receive deposits including their paycheck, but the freeze stops withdrawals or transfers over a certain amount from going through. Therefore, a set amount deposited stays in the account and later gets transferred to the creditor.

Mambu allows you to select a journal entry booking date different from the value date of transactions.

A branch in Mambu is the default label for an organization's subdivision. Often branches represent:

A client models any customer that is just an individual. A group models any customer that is not an individual.

Business case

This page describes the client life cycle. For general information on individual clients, see Clients and Groups Overview.

This page describes how to create, edit, and delete client types. For general information on individual clients and how they are used, see Clients and Groups Overview.

Business case

When a client finishes repaying a loan, the account balance goes to zero due and you can close that loan account.

Closing a deposit account with zero balance

A user is anyone who accesses and uses Mambu via the UI or the API. Each user has a user account that stores the access credentials, the details of the person using the system, the role, and the permissions.

By default, Mambu runs a daily series of automated tasks outside of business hours and an hourly series of additional processing tasks. These are grouped into a general category called End-of-Day processing (EOD processing):

Group role names are used to determine specific roles for members within a group. For more information, see Group Role Names.

A permission is the authorization given to users that enables them to view a type of information or to perform an action in Mambu. You can either assign individual permissions to users or you can group permissions by creating a role and then assigning that role to a user.

This article describes profile and password management for users with a Mambu password.

A role is a way to to group permissions and to control other forms of access within Mambu.

A user is anyone who accesses and uses Mambu via the UI or the API. Users are assigned permissions which determine the information they can access and the tasks they can perform. Each permission has a name and covers one action or a small subset of action - for example VIEWCLIENTDETAILS. Permissions can be assigned to users either directly or through a role. A role is a way to group permissions and to control other forms of access within Mambu.

Permissions allow users to view different types of information or to perform actions in Mambu. You can either assign individual permissions to users, or you can group permissions by creating a role and then assigning that role to a user. The user will then have all the permissions that are a part of that role. For more information see Understanding Users, Roles, and Permissions and Roles.