Joining/leaving
Joining an alliance grants access to alliance coordination surfaces and shared systems according to your role. Leaving removes those permissions and may affect your access to alliance-only views or actions.
Before joining or leaving, check any alliance policy constraints and active obligations. Coordination costs are lower when membership changes are intentional, not reactive. For leadership teams, a simple join/leave checklist reduces administrative overhead: confirm role assignment, verify bank policy visibility, and record expected contribution norms.
Deposits/withdrawals
The alliance bank is a controlled shared pool for approved economic activity. Deposits move assets into alliance control; withdrawals move assets back to a nation context subject to policy and role checks.
Always verify bank actions in the ledger or outcomes-equivalent activity view. For shared funds, auditability matters as much as speed. Good treasury hygiene includes documenting why a transfer happened, not only that it happened. Short notes tied to strategic intent reduce confusion during high-pressure periods.
Roles/permissions (high level)
Roles define who can view balances, set policy, deposit, or withdraw. Permissions are intentionally restrictive to prevent abuse and reduce accidental transfers. If an action is blocked, first confirm your role rather than assuming the bank is broken.
Good alliance operations depend on explicit permissions and documented expectations. Technical guardrails help, but process clarity is equally important. When onboarding new members, review bank policy before granting elevated access. Clear expectations up front prevent most role-related disputes.