Permission before access
Bank access follows the permission model the rest of the platform uses. An officer can hold withdrawal rights in one guild and read-only access in another, without juggling shared passwords.
Features
Guild Bank
The bank is a ledger, not a spreadsheet. Deposits and withdrawals are recorded against members, permissions decide who can touch what, and the history is searchable.
Every deposit, withdrawal and tax β on the record.
Deposits and withdrawals recorded per member
Role-based permissions on the bank and its tabs
Guild taxes calculated from the same ledger
Searchable history of every movement
Taxes that reconcile
Set a guild tax and Guildify calculates what each member owes from the same ledger that records their deposits, so the numbers add up without a manual reconciliation night.
An audit trail, not a vibe
Every movement of items and currency is recorded with who, when and how much. When something is missing, the question is answerable inside the platform rather than in a private message.
Frequently asked questions
Can different officers have different bank permissions?
Yes. Access is granted per role, and a role can be scoped so that it only applies to the guild or community it belongs to.
Does the bank track items as well as currency?
Yes. Both currency and items are tracked, and every movement is attributed to a member.
Is there a history of withdrawals?
Every deposit and withdrawal is stored with its timestamp and the responsible member, and the history is searchable.
Built to work together
Every feature shares one roster, one permission model and one audit log. A member added once is recognised everywhere: raids, loot, bank and applications.