Home Organization & Settings

Organization & Settings

Configure how BitBooks works for your team.
By Miguel Abascal
5 articles

Organization Settings Overview

Where settings live All organization-level settings are at Admin → Settings. The page is a long form grouped by topic. Click Save at the bottom when you're done. Admin Settings page showing the various sections (Currency, Accounting, Localization, Bitcoin, Approvals, etc.) You need Admin or Owner role to change settings. Members and Viewers see the page but can't modify. What's on the page Currency - Primary accounting currency. Your functional currency. The main currency your books are kept in. See Setting Your Functional Currency. - Functional currency type. FIAT or BITCOIN. Determines whether your functional currency is BTC or a fiat code. - Secondary reporting currency. Optional second currency that shows alongside the functional one on reports. See Setting Your Reporting Currency. - Primary exchange provider and Secondary exchange provider. Where exchange rates come from. Default is Open Exchange Rates for fiat and CoinGecko for BTC. Most users keep defaults. Accounting - Accounting framework. IFRS, US GAAP, or both. Affects how some calculations are presented. See Setting Up Your First Organization for the framework choice. - FX translation method. Historical per Transaction (default), Closing Rate, or Period Average. Controls how multi-currency reports are translated. See How Currency Conversion Works. - Accounting year type. Calendar year (Jan-Dec) or Fiscal (any 12 months). - Fiscal year start month / end month. Only used if Accounting year type = Fiscal. - Journal lock date. The date that closes everything before it. See Period Close. Bitcoin - Bitcoin display preference. BTC High Precision, BTC Consequence, Bitcoins, or Satoshis. See BTC Display Modes. Localization - Number format. US Standard (1,234.56) or European (1.234,56). - Date format. MDY (US), DMY (most of world), or YMD (ISO). - Time format. 12-hour or 24-hour. - Time zone. IANA time zone for the organization (e.g., America/New_York). Approvals - Approval threshold currency. A specific currency for the threshold amount. - Approval threshold amount. Transactions at or above this amount require approval. See Setting Spending Limits per Wallet. Organization metadata - Organization name. What this org is called. - Slug. A URL-friendly version of the name (used in some routes). Auto-generated from the name; you can override. Danger zone - Archive organization. Soft-delete the org (you can restore later). - Delete organization. Permanent delete. Wipes all data. Use only if you're absolutely sure. Saving changes Most changes apply immediately when you click Save: - Currency display changes apply to your next page load - Localization changes apply immediately - Approval threshold changes apply to future transactions A few changes are special: - Functional currency change. Requires an audit reason and an effective date. The change is logged and visible in reports. See Changing Your Functional Currency After Going Live. - Lock date change. Standard save, but the change is logged in the Activity Log. Anyone reviewing knows when periods were closed. Settings vs preferences Organization settings affect everyone in the organization. - Change BTC display preference: every team member now sees BTC the new way. - Change date format: everyone sees dates the new way. - Change functional currency: the books are now in the new currency for everyone. There's no per-user preference for any of these. The whole team operates on a consistent view. If a team member personally prefers a different display (e.g., the developer wants sats, the founder wants BTC): pick one as the org standard. Personal preferences will have to bend to the organization choice for now. Common questions "Can I have different settings for different organizations?" Yes, and you should. Each organization has its own settings, completely independent. A USD-functional org and a CAD-functional org operate side by side under the same user account. "What if I'm not sure what to pick?" Defaults are sensible: - Functional currency: pick your home country's currency - Framework: IFRS - Accounting year: Calendar - BTC display: BTC Consequence - Number format: US Standard if you're in the US, European otherwise - Date format: matches your country (MDY for US, DMY for most others) You can change later. Better to pick something reasonable than agonize. "I'm a Member role; why can't I change settings?" Member is the day-to-day bookkeeping role. Settings are governance-level decisions that affect everyone. They're restricted to Admin and Owner. If you need a setting changed, ask an admin. "Where do user-level preferences (like notification subscriptions) live?" In your user profile, separate from organization settings. Click your avatar in the sidebar → Profile. Where to go next - Setting Up Your First Organization for the initial configuration - User Roles for who can change settings - Setting Your Functional Currency for the most-impactful setting - Period Close for the lock date - Multiple Organizations for managing several orgs at once

Last updated on May 03, 2026

User Roles: Owner, Admin, Accountant, Member, Viewer

The five roles BitBooks has five roles, ordered from most powerful to least: | Role | Power level | Typical use | |---|---|---| | Owner | Top | The founder or principal of the business | | Admin | Almost top | Co-founder, CFO, anyone who needs to configure everything | | Accountant | Books-focused | External CPA, fractional CFO, controller | | Member | Day-to-day | In-house bookkeeper, junior accounting staff | | Viewer | Read-only | Investor, board member, partner, auditor reviewing | You assign one role per user per organization. A user can be Owner in one org and Viewer in another. What each role can do Owner Everything. There's only one Owner per organization, and they can: - Access every screen - Edit every setting - Invite, change, and remove users - Promote anyone (including transferring Ownership to someone else) - Delete the organization (this is one of the few actions only the Owner can do) You can transfer Ownership to another user via the Users page if needed (e.g., business sold, founder leaves). Admin Same as Owner, except: - Can't delete the organization - Can't transfer Ownership For 99% of day-to-day decisions, Admin = Owner. Use Admin for co-founders, CFOs, and other senior team members. Use Owner only for the actual principal. Accountant Full access to the books, but limited on configuration: - Can post any transaction or journal entry, including in any currency, including reversals - Can run all reports - Can close periods - Can manage chart of accounts - Cannot change organization settings (functional currency, framework, etc.) - Cannot invite or manage users - Cannot delete or archive the organization Use for external CPAs, fractional controllers, and anyone whose job is the books but who shouldn't touch the org configuration. Member Day-to-day bookkeeping: - Can create and edit transactions and journal entries - Can review and post Drafts - Can run reports (read-only) - Cannot delete or reverse posted entries - Cannot close periods - Cannot manage chart of accounts (only view it) - Cannot manage users - Cannot change settings Use for in-house bookkeepers, junior accounting staff, anyone doing data entry. Viewer Read-only across the board: - Can run reports - Can browse transactions and balances - Cannot create, edit, post, or reverse anything - Cannot manage anything Use for investors, board members, business partners, auditors who just need visibility. What every role can do A few things every role has: - Sign in with their own email and password - See the organization name and basic identity - Switch to other organizations they belong to - Change their own profile (their name, avatar, password, 2FA setup) The minimum sign-in privilege is Viewer. There's no role lower than Viewer. Picking the right role A simple decision tree: 1. Is this person the principal owner of the business? → Owner 2. Are they a senior team member who should be able to configure the org? → Admin 3. Are they an accounting professional who needs full books access but shouldn't change configuration? → Accountant 4. Are they a junior bookkeeper or data entry person? → Member 5. Are they a stakeholder who just needs visibility? → Viewer When in doubt, pick the lower role. Demoting someone is harder than promoting (psychologically and practically). Start small and promote when you're confident. Approval thresholds and roles If your organization uses approval thresholds (transactions above a certain amount require approval), the approver roles are: - Owner: can approve - Admin: can approve - Accountant: can approve - Member: cannot approve (their own submissions need approval) - Viewer: cannot approve (and can't submit either) So a Member submitting a $10,000 transaction needs an Admin or Accountant to sign off before it posts. Changing someone's role 1. Admin → Users 2. Click the user 3. Change role 4. Save The change applies on their next page load (or immediately, if they're not actively using the system). If they're mid-task and you demote them, the in-progress action might fail. Talk to them ahead of time when possible. What roles can do across organizations Roles are per-organization. So: - A user can be Member in Org A and Admin in Org B - Switching organizations switches their effective role - Their account list shows all orgs they belong to with their role in each The role doesn't follow them; it's tied to the org membership. A worked example You run a small Bitcoin business. Your team: | Person | Real role | BitBooks role | |---|---|---| | You (founder) | CEO | Owner | | Co-founder (CTO/COO) | Operations | Admin | | External CPA | Tax + monthly close | Accountant | | In-house bookkeeper | Day-to-day | Member | | Lead investor | Quarterly review | Viewer | Each person can do exactly what their job requires. The CPA can post adjustments without needing to change settings. The bookkeeper can do daily entry without being able to change the framework. The investor can run reports without any risk of changing data. This is the typical small Bitcoin business setup. Common questions "What if I'm a solo operator with no team?" You're the Owner. No other roles needed. You'll handle everything yourself. When you grow, add team members one at a time and pick the role per person. "Can I have two Owners?" No. One Owner per organization. The closest equivalent is two Admins (which gives both equivalent power except for the delete-org and transfer-ownership actions). "Can I limit a Member to specific wallets?" Not yet. Today, Members have access to all wallets in the organization. Per-wallet permissions are on the roadmap. "What happens to a user's actions if I remove them?" The actions stay in the audit log with their name. Only their access to the organization ends. They can't sign in or take new actions, but historical actions remain. Where to go next - Inviting Team Members for the invite process - Two-Factor Authentication for hardening sign-in - Multiple Organizations for managing several - Setting Spending Limits per Wallet for approval threshold setup - Activity Log to see what each user has done

Last updated on May 02, 2026

Two-Factor Authentication

What 2FA is Two-factor authentication (2FA) is a second step at sign-in. After your password, BitBooks asks for a code from a separate device (your phone, usually). The point: even if someone learns your password (phishing, leak, breach at another service where you reused it), they still can't sign in without your phone. For accounting books that contain financial data and Bitcoin wallet credentials, 2FA is a smart investment. How to set it up 1. Click your avatar in the sidebar (bottom-left) 2. Click Profile (or Account Settings) 3. Find the Security or Two-Factor Authentication section 4. Click Enable Profile page with the Security section visible and the Enable 2FA button highlighted You'll choose a method: Authenticator app (recommended) Use an app like: - Authy (free, multi-device sync) - Google Authenticator (free, simple) - 1Password (built into the password manager) - Bitwarden (built in) - Aegis or Raivo (open-source, mobile) The setup flow: 1. BitBooks shows a QR code 2. Open your authenticator app 3. Tap "Add account" (or scan a QR code) 4. Scan the BitBooks QR code with the app 5. The app shows a 6-digit code that changes every 30 seconds 6. Type that code into BitBooks to confirm 7. 2FA is enabled 2FA setup screen with QR code visible and a confirmation field for the first code SMS (less secure but available) If you can't use an authenticator app, BitBooks can send a code by text message: 1. Pick SMS as the method 2. Enter your phone number 3. BitBooks sends a test code 4. Enter it to confirm SMS is less secure than authenticator apps because: - SMS can be intercepted via SIM-swap attacks - SMS depends on cellular network availability Use SMS only if you can't run an authenticator app. Authenticator apps are strongly preferred. What 2FA looks like at sign-in After 2FA is enabled, sign-in becomes a two-step: 1. Enter your email and password (same as before) 2. BitBooks shows a 2FA prompt 3. Open your authenticator app, get the current 6-digit code 4. Enter the code in BitBooks 5. You're in The code changes every 30 seconds. Make sure your phone's clock is accurate; an off-by-a-minute clock will reject codes. Recovery codes When you set up 2FA, BitBooks should give you recovery codes. These are one-time-use codes that work in case you lose your authenticator (phone broken, app deleted, SIM swapped). Save them somewhere safe. Options: - Your password manager (best) - Printed and stored in a safe place - An encrypted note If you lose both your authenticator AND your recovery codes, you'd need to contact support to disable 2FA on your account. We'd verify your identity through other channels before doing so. Required by your organization Owners can require 2FA for everyone in the organization. If this is set, every member must enable 2FA before they can use BitBooks. The setting is in Admin → Settings under Security (when shipped). Today, 2FA is per-user opt-in. For sensitive organizations (Bitcoin treasuries, multi-million-dollar books), enabling org-wide 2FA is strongly recommended. What 2FA does NOT protect against - A compromised device. If your phone is stolen and unlocked, the attacker has both the password (in your password manager) and the 2FA app. Lock your phone and use device-level security. - Phishing in real-time. A sophisticated phishing site can prompt for both password and 2FA, then forward to BitBooks. Hardware keys (FIDO2/WebAuthn) protect against this; standard 2FA does not. - Social engineering of support. If someone convinces support to disable your 2FA, they bypass the protection. Support has procedures to verify identity, but this is a risk. For the highest security, use a hardware security key (when supported in BitBooks) plus 2FA. Common questions "What if my phone breaks and I don't have recovery codes?" Contact support. We'll verify your identity through other channels (email, ID document, etc.) and disable 2FA so you can sign in. Then you can re-enable with a new device. This process takes time (typically 24-48 hours), so prevention (saving recovery codes) is much better than recovery. "Can I have multiple authenticator devices?" If you use Authy, yes. Authy syncs across devices. If you use Google Authenticator (no sync), you have one device. To switch, you'd disable 2FA, re-enable on the new device, and save the new QR code there. 1Password and Bitwarden both sync across devices. "Is the 6-digit code different on every site?" Yes. Each service generates its own. Your authenticator app holds many "accounts" (BitBooks, Gmail, Twitter, etc.) and shows a different rolling code for each. "What if I'm temporarily without my phone?" Use a recovery code (you saved them, right?). Each one is single-use. Where to go next - User Roles for who has access to what - Inviting Team Members for setting up team accounts - Organization Settings Overview for org-wide settings (when 2FA enforcement is configurable)

Last updated on May 03, 2026

Multiple Organizations: Switching and Managing

When you'd have multiple organizations Common cases: - You run several businesses. Each is its own legal entity with its own books. - You're a bookkeeper or accountant with several clients, each in their own org. - A test or sandbox org plus a production org. - Different geographic operations that need separate currency / tax handling. Each organization in BitBooks is fully independent: its own wallets, contacts, transactions, journal entries, reports, settings, and team members. Creating a new organization 1. Click Admin in the sidebar 2. Click the Organizations tab 3. Click New Organization 4. Fill in the wizard (same as the initial setup): name, currency, framework, etc. 5. Save Admin Organizations tab showing a list of orgs with the New Organization button The new organization appears in your switcher dropdown. You're automatically the Owner. Switching between organizations The switcher is at the top of the sidebar: Sidebar with the organization switcher dropdown open, showing several orgs Click to open, click an org name to switch. When you switch: - The page reloads with the new org's data - The Insights page, wallets, transactions, reports all show the new org - Your role might be different in the new org (Member vs Admin, etc.) - Settings, contacts, chart of accounts are all the new org's Switching is fast (a second or two). You can switch as often as you want. What's shared and what's not Shared (across all your orgs) - Your user account (one email, one password, one 2FA setup) - Your profile (name, avatar) - Your authenticator and 2FA recovery codes Per-organization (NOT shared) - Wallets and balances - Transactions and journal entries - Contacts - Chart of accounts - Reports - Settings (functional currency, lock dates, BTC display, etc.) - Team members - Bitcoin Connections vault (each org has its own vault password) So: signing in is a single act, but everything you see after sign-in depends on which organization is active. Bookkeeper / accountant workflow If you manage several client books, the typical flow: 1. Sign in once 2. Switcher dropdown shows: Client A, Client B, Client C, Your Company 3. Pick a client to work in 4. Do their bookkeeping (enter transactions, reconcile, run reports) 5. Switch to next client 6. Repeat Each client's data is fully isolated. You can't accidentally enter Client B's transaction in Client A's books because the active org gates everything. Cross-organization views A few things you can do that span organizations: Bulk-invite to all orgs When inviting a user who should access multiple orgs (e.g., your bookkeeper who handles all your businesses), the invite form has an option Add to all my current organizations. Tick it; the user is invited to every org you own with the same role. Saves several invitation rounds. Multi-org reporting (future) Cross-org consolidated reports (e.g., "show me total revenue across all my orgs") aren't a feature today. You'd run reports per org and combine in a spreadsheet. A roadmap item: explicit consolidation. For now, single-org reporting only. Archiving an organization If you stop using an org (business closed, client relationship ended): 1. Admin → Organizations 2. Click the org 3. Click Archive Archived orgs: - Disappear from your switcher dropdown by default - All data preserved - Restorable any time - Can be permanently deleted from the archived state if you're sure To see archived orgs, toggle Show archived on the Organizations page. Deleting an organization Permanent removal. Available only to the Owner of the org. From the org's settings page: 1. Scroll to the danger zone 2. Click Delete Organization 3. Confirm by typing the org's name After deletion: - All data is gone (wallets, transactions, journal entries, contacts, reports) - Audit logs may be retained for a brief period as backup - Cannot be undone Use only when you're absolutely certain. Most cases call for archiving instead, which preserves data and keeps your option open. Common questions "Can I have unlimited organizations?" Practically yes. There's no hard cap on the number of orgs per account. If you have hundreds, performance might lag in some views; talk to support if that happens. "Can I move data from one organization to another?" Not in the current UI. Each org is fully isolated. To "move" something, you'd export from one (e.g., to Excel) and import to the other. "What if a client wants to take over their org from me?" Transfer ownership. From the client's org → Admin → Users → click yourself → Transfer Ownership to the client (assuming they have an Admin or higher role). After transfer, you're no longer Owner; the client is. You can stay on as Admin, Accountant, or whatever role they want, or be removed entirely. "Can I pre-create organizations for clients before they sign up?" Yes. Create the org under your account, configure the basics, then invite the client as Owner. They get the magic link, sign in, and become the principal of their org. Where to go next - Setting Up Your First Organization for the org creation walkthrough - Inviting Team Members for adding users to an org - User Roles for the role distinctions - Organization Settings Overview for per-org configuration

Last updated on May 03, 2026

Managing Team Members: Adding, Changing, Removing

Where team management lives Everything is at Admin → Users. Admin Users tab showing a table of team members with their roles The page lists every user with access to the current organization, plus pending invitations. Adding a user (invite) See Inviting Team Members for the full walkthrough. The summary: 1. Admin → Users → Invite User 2. Enter email and role 3. Send The invitee receives a magic link, sets up their account, and they're in. If they should access multiple organizations, you can tick Add to all my current organizations to invite them everywhere at once. Changing a user's role To promote, demote, or change role type: 1. Admin → Users 2. Click the user 3. Change the role from the dropdown 4. Save The change applies on the user's next page load. If they're actively in BitBooks, the page they're on may show stale permissions briefly. When changing roles: - Promote when you trust them with more - Demote when their responsibilities have shrunk or you want tighter controls - Change kind (Member to Accountant) when their function has changed Communicating ahead of time avoids surprise. "Hey Brandon, I'm bumping you up to Admin so you can change settings without going through me" goes a long way. Removing a user When someone leaves the company, ends a contract, or you want to revoke access: 1. Admin → Users 2. Click the user 3. Click Remove Confirm. The user's access to this organization ends immediately. They can no longer sign in or take any actions. What stays: - Their historical actions in the audit log (preserved with their name) - Transactions they created (linked to them by user ID forever, for audit) - Their account in any other organizations they belong to (only this org's access is revoked) What's gone: - Their ability to view or change anything in this organization - Their notifications for this organization If you accidentally remove someone, re-invite them. They'll get a fresh magic link. Pending invitations Invitations that haven't been accepted show as Pending on the Users page. From there you can: - Resend (in case they didn't see the original email) - Revoke (cancel an invitation that's no longer needed) Pending invitations expire after a default period (typically 7 days). Expired ones can be resent. Special cases The Owner There's one Owner per organization. To change who the Owner is: 1. Promote another user to Admin first (so they have most permissions already) 2. As the current Owner, click Transfer Ownership in the Users section 3. Pick the new Owner 4. Confirm After transfer, you become Admin (or whatever role they pick for you), and the new Owner has Owner power. Useful when the founder is selling the business or stepping back. Yourself You can't remove yourself from your own organization (that would lock you out). To leave an org you don't own: have the Owner remove you. To "leave" an org you own: archive or delete it. Suspended users Some scenarios call for temporarily disabling a user without permanently removing (e.g., they're on extended leave). The current UI doesn't have a Suspend/Pause toggle; the workaround is: - Change their role to Viewer (read-only access) - When they return, change back Or: - Remove them - Re-invite when they return A formal Suspend feature is on the roadmap. Common questions "Can I see what each user has done?" Yes, in the Activity Log. Filter by user. See Activity Log. "Can I require 2FA before a user can sign in?" Today: 2FA is per-user opt-in. You can encourage but not enforce. Org-wide 2FA enforcement is on the roadmap. "What happens to a Draft transaction if the user who created it is removed?" The Draft stays. The "created by" field still references the removed user (their name preserved in the audit trail). Other users can edit and post the Draft normally. The original creator just can't sign in anymore. "My team is growing. How many users can I have?" No hard cap. Practical limits depend on your subscription. For most growing businesses, plenty of room. "Can a contractor have access for one specific project, then lose it?" The cleanest path: invite, give a Member or Viewer role for the duration, remove when done. The audit log preserves their actions. A worked example A new bookkeeper joins your team. You want them to have day-to-day access but not be able to change settings. 1. Admin → Users → Invite User 2. Email: bookkeeper@example.com 3. Role: Member 4. Send invite They get the email, sign up, are now a Member. A month later, you decide to promote them to Accountant so they can post adjusting entries: 1. Click their name on the Users page 2. Change role from Member to Accountant 3. Save Done. They now have full books access. Six months later, the contract ends: 1. Click their name 2. Click Remove Their access ends. Their work in the audit log stays. Where to go next - Inviting Team Members for the full invite walkthrough - User Roles for the role-by-role permissions - Two-Factor Authentication for hardening sign-in - Multiple Organizations for managing teams across orgs - Activity Log for tracking what each user has done

Last updated on May 03, 2026