Who issues coins?
A leader who has the matching permission in the action matrix. A member only files a request, and the decision on it is recorded in the log.
Coinsand your internal economy.
A member requests coins for work done or spends them in the shop, and a leader approves the requests. Every move stays in the log.How coins movefrom request to purchase.
Balances are kept separately for each server, and the word “coins” can be renamed — to points, for example.A request to award coinsA member asks for coins for work done, and a leader approves or rejects it. The decision goes to notifications and to the log.
A shop you fill yourselfYou decide what coins can be spent on. A purchase deducts the balance and stays in the history of operations.
A ledger of operationsEvery award and deduction is visible in the log: who, to whom, how much and what for. Balances are kept per server.
When workneeds something in return.
An internal currency runs on trust right up to the first argument about who got how much. The transaction log settles that.Rewards handed out by hand
A member files a request for work done, a leader approves or rejects it. The decision goes to notifications and stays in the log.
Nothing to spend them on
You fill the shop yourself: a role, an access, an internal prize. A purchase deducts the balance and lands in the transaction history.
The word coins does not fit
Rename it in Terms — points, for example. Only the labels change; data and permissions stay as they were.
Common questionsabout coins.
Do balances add up across servers?
No. The balance is kept per server, just like positions, permissions and reports.
Can I see what the coins were for?
Yes. The transaction log shows who, to whom, how much and what for — every credit and debit is stored.
What about stalled requests?
Add a rule in Automations: it reminds the member or the leadership that a coin request is still undecided.