Skip to main content
A business account is a shared pot of money owned by a job or gang instead of one character - police funds, a mechanic’s till, a gang stash. Awoken Banking calls these society accounts and keeps one per job and one per gang automatically. You control who can reach the money and how they hook into your server. Everything here is in config/accounts.lua.
A business account is owned by a job/gang. A shared account is a personal account one player opens and invites others onto. Both use the same three roles below - only the owner differs.

The three roles

Every shared account hands each member one of three roles (the same roles used on any account). On a business account, a member’s rank decides which they get.

Owner

Full control. Moves money and manages members.

Contributor

Moves money in and out. Can’t manage members.

Viewer

Read only. Sees balance and history, moves nothing.

Who can access the money

Set access per rank from inside the bank app: the boss opens the business account, opens its members, and grants each rank a role. This always wins. Config.Society is only a legacy fallback, ignored for any job or gang with in-app per-rank permissions (or a grade bankAuth flag) set. Used only when neither is set: members at or above minGrade get money access, and the boss is always an admin.
config/accounts.lua

Creating society accounts on start

By default the bank pre-seeds an account for every job and gang on server start, so the money exists before anyone logs in.
config/accounts.lua

The society bridge

Your framework has its own society-account store behind boss menus and paychecks (qb-management on QBox/QBCore, esx_society on ESX). With the society bridge on, Awoken Banking becomes that store, so boss menus and wages route through the bank. One balance, everywhere.
config/accounts.lua
Leave this on unless another resource manages society accounts. Awoken Banking answers under the qb-management and esx_society names (declared with provide lines in its manifest), which lets other scripts find it - see Installation.
The bridge is only about money. Hiring, firing, and setting ranks stay with your framework (qbx_core / qb-core / es_extended) - Awoken Banking never touches them.
If you turn the bridge off, you must also delete the matching provide 'qb-management' and provide 'esx_society' lines in fxmanifest.lua. provide is static, so without that step other scripts still detect Awoken Banking as qb-management / esx_society, but with the bridge off those exports won’t answer and you’ll get errors.