Operator guide

Going live with Forte

Connecting Forte in test mode (sandbox) lets you click through the whole billing flow with test cards and eChecks before a single real dollar moves. Going live is two separate switches — one in Forte, one in SpaceBloom — and you do it per organization: each operator connects their own Forte account, so there is no platform-wide "go live" button, and one organization going live never affects another.

Before you start

Your sandbox Dex account is a throwaway for testing. A live connection needs a real, approved Forte merchant account, which is a different organization with different IDs.

1. Enroll with Forte and complete their approval (underwriting). You end up with a live Organization ID and Location ID — both different from your sandbox ones.
2. In the live Dex portal (log in at login.forte.net, not the sandbox portal): Developer → API Credentials → Create to generate a live API Access ID and API Secure Key. The secure key is shown only once — copy it somewhere safe before you close the dialog. If you lose it, you regenerate a new one.
3. If you take eCheck / ACH (not just cards), make sure your live location is set up for eCheck processing with Forte. Card-only accounts can skip this.

Don't create the live webhook in Dex yet — its URL changes in the next step.

Switch SpaceBloom to your live credentials

Until you make this switch, everything you do runs in Forte's test mode and no real money moves. Make it when you are ready to take real payments.

On your organization's Billing tab at https://spacebloom.app:

1. Disconnect the sandbox connection. (Your live account is a different location, and SpaceBloom keeps one Forte location per organization, so you replace the connection rather than edit it in place.)
2. Connect Forte again and enter your live Organization ID, Location ID, API Access ID, and API Secure Key, with Environment = Live. If your account takes eCheck, leave Accept eCheck on. SpaceBloom verifies the credentials against Forte before saving — on success the status shows live and charges enabled.
3. Register the webhook. A new webhook URL appears (reconnecting issues a fresh one). Copy it and, in your live Dex portal, go to Developer → Webhooks → Create, paste the URL, and subscribe to transaction.sale, transaction.credit, transaction.void, paymethod.create, and paymethod.delete. This is how a payment or a saved card still confirms if a member closes the tab mid-checkout; without it, those confirm on the nightly run instead.
4. Test with one real transaction. Run a small live payment (and a live eCheck if you take them), then confirm it shows as paid — an eCheck shows as processing and settles over the next few business days — on the member's billing page.

What changes automatically

Once the connection is set to Live, SpaceBloom switches to Forte's live systems on its own — the live API and the live hosted card/eCheck form. There is nothing else to configure.

Good to know

• Reversible. Disconnecting Forte stops online payments for your organization until you connect an account again; your invoices and history are untouched.
• Your API secure key is stored encrypted and tied to your organization — it is never shown back to you or included in any page or export. The masked last four of your Access ID is all that's displayed.
• You are the merchant of record. Payouts, refunds, disputes, and settlement all live in your Forte account — SpaceBloom never holds your money.
• Members re-save their payment method after you switch. Disconnecting clears every saved card and bank account for your organization (a method saved against your old Forte account can't be charged on the new one), so members are simply asked to add it again on their next payment — nothing shows as a card "on file" that doesn't work. Their autopay preference is kept. It is least disruptive to switch before many members have saved a method.

Moving from another platform

Switching from Nexudus, Optix, a spreadsheet or anything else is a sequence, not one button. The data comes across in minutes; the parts that take time are your members signing in and saving a payment method. Run the old and new platforms side by side until both are done, then pick a night to switch billing over. This is the order that works.

1. Pick a switch-over date

Decide the first date SpaceBloom will invoice and enter it as the Switch-over date on the Billing tab. Everything before it stays in the old platform: its invoices, its charges, its receipts. The import starts every contract from that date, and the nightly run skips (never issues) anything a contract would have billed earlier. Give yourself two to four weeks between importing and that date — that is how long it takes for a roster to sign in and re-save payment methods.

2. Export from the old platform

You need, at most, five lists: members, locations, plans, contracts and open balances. From Nexudus these are the grid exports under Coworkers, Tariffs, Products, Contracts and Invoices; from a spreadsheet, one wide sheet is fine — the importer can read several kinds of row from one file. Column names don't matter and can be in any order; you'll map them in the next step.

3. Import

Open the Import tab. Drop the files in, confirm what each one is, press Continue to mapping and map the columns (the assistant proposes a mapping; you confirm it). Preview import runs a dry run that shows every row with what would happen and lists anything to fix; then Apply. Rows go in as locations → plans → products → members → contracts → open balances, and re-running an import matches what is already there instead of duplicating it, so fix the file and apply again as often as you like.

Two things to check in the preview:

• Next invoice date on each contract. This is the date SpaceBloom first bills that member. If the old platform has already billed the current period, set it to the start of the next one so nobody is charged twice. A date in the past is refused unless you tick Move past next-invoice dates forward to the next billing day.
• Open balances come in as open invoices dated as they were. SpaceBloom never auto-charges an invoice more than 30 days past due, so old balances are collected deliberately — the member's Pay now or your Charge now — never as a surprise batch on the first night.
• One source per balance. If a member's balance reaches the importer from two files — an invoice export and a roster sheet's "balance owed" column, say — the numbers differ, so both would import and the member would owe it twice. The preview flags a roster balance that equals one of the member's invoices, or the total of them, in another file; drop one of the files (or its balances view) and preview again.

Members arrive as invites. They are billable immediately, so contracts and balances attach to them before they have ever signed in.

4. Get members in

Tell your members the portal address (<your-slug>.spacebloom.app) and that a SpaceBloom invite is coming. Send the invites from the roster (see Inviting members); each person gets a link, and signing in with that email address links them automatically. Watch the Members tab for who is still an open invite, and Resend to the stragglers.

5. Payment methods do not move

Cards and bank details live in the old platform's payment processor and cannot be exported. Every member who should be on autopay has to open Billing on the portal and Save a payment method once. Until they do, their invoices are issued but not charged. The Payment methods card on your Billing tab shows how many members with an active contract have saved one, and lists who has not — with whether they have signed in yet. Say this plainly in your announcement; it is the step people put off.

6. Doors

If members already have badges or codes in your access system, connect it on the Access tab and use Members who already have a badge to link them — nothing is re-issued, and access starts following the contract from then on. See Door access.

7. Switch over

On the day: stop the old platform from generating new invoices (end or pause its contracts), check that SpaceBloom's contracts show the right next invoice dates, and make sure your gateway is live (Going live with Forte, or Stripe connected). The nightly run does the rest. Keep the old platform readable for a while for history; nothing needs to stay active there.

If something is wrong after the first billing night, the Invoices tab shows what was issued and charged, and every invoice can be voided or marked paid by hand.

The first invoice date

Every contract carries the date SpaceBloom first invoices it. Leave it blank and you get the sensible answer: the start date if that is still ahead, otherwise the next billing day. You only need to think about it when you want something else, and SpaceBloom will stop and ask in two cases.

"That first-invoice date is in the past." You have asked to bill periods that have already gone by. Submitting again issues one invoice for each of them, back to that date. That is what you want when you are taking over mid-month from another platform and those periods were never billed. It is not what you want if you simply mistyped the year, so nothing is created until you press the button a second time.

"Billing would normally start … starting … instead skips the periods between." The opposite: you have pushed the first invoice past where billing would have begun, so the periods in between are never invoiced at all. A free first month is a real reason to do this. A wrong year is not. Again, nothing happens until you confirm.

Both questions are asked about one specific contract. Change the member, the plan or either date and SpaceBloom asks again, because the answer may no longer be the same. If you save a contract as a draft with an unusual date, you are asked once more when you activate it — saving a date is not the same as agreeing to bill from it.

Two things SpaceBloom will not let you do at all, because no confirmation makes them sensible: a first invoice more than five years after the start date (that is a typo), and one on or after the contract's own end date (it would never be invoiced).

Importing. An import cannot stop and ask, so it tells you in the preview instead. A row that reads "First invoice …, not … — nothing is invoiced before then" has a date later than where billing would otherwise start. Check the column you mapped: a spreadsheet of renewal dates looks a lot like a spreadsheet of next-invoice dates, and importing the wrong one gives you a roster that bills nothing until somebody notices a quiet nightly run.

Inviting members

Members are the patrons you bill. Invite them from the Overview tab — paste your list into the Invite members box, one person per line:

gail@bullseyecatering.com
Al's Kitchen <al@alskitchen.com>
sunny@sunnykitchen.co, Sunny Kitchen LLC

Any of those shapes works (paste straight from a spreadsheet column or your mail app), a first line like "Email, Business name" is ignored, and you can paste up to 500 at a time. Press Preview to see every row with its status:

• New — will be invited.
• Already a member — nothing to do; they're skipped.
• Already invited — their invite is refreshed (new 30-day link). They are not emailed again unless you tick Resend to people already invited.
• Invalid / Duplicate in list — skipped; fix the line and preview again.

Then Send. With "Email each person an invite link" ticked, each person gets an email sent as "Your Organization via SpaceBloom" with your logo and a personal link (replies go to your contact email); untick it to add members silently and share links yourself. Large lists go out in batches with a progress line — if your connection drops, Retry picks up exactly where it stopped without emailing anyone twice. When it finishes you see a summary and only the rows that need attention (an email that couldn't be delivered, a row that failed).

Invited members are billable right away — you can assign contracts and invoices before they sign in. They become active the moment they sign in with that email address, or use the emailed link if they sign up with a different one. From the roster you can Resend, Copy link, or Remove any open invite.

Each open invite shows what happened to its email. "Email sent" means the mail service accepted it. Email bounced means the address rejected it — check for a typo, or hand the person their link with Copy link; a temporary bounce (full mailbox) is worth a Resend later. Reported as spam means the person marked an earlier email as junk — SpaceBloom will not email that address again, so share the link another way. If invites land in spam folders, ask members to look for the email from your organization's name and to add the sender to their contacts.

Door access

If you already have an access-control system or smart locks, SpaceBloom can keep door access in step with your memberships. Go to the Access tab and choose how your doors are controlled. Three options are offered, each with a short description, and Kisi is picked to start:

• Kisi — paste an API key for your Kisi organization (see Using Kisi? below).
• Another system, through SpaceBloom — for Brivo, Salto, Avigilon Alta, Latch, Verkada, keypad locks from Schlage, Yale and August, and others. There is no key to paste: press Connect an access system, sign in to your own account with the provider in the window that opens — SpaceBloom never holds your door passwords — and come back to a list of your doors. If the page hasn't heard back yet when you return, press Check again.
• My own Seam workspace — for operators already paying Seam directly (see Already using Seam? below).

Picking another option puts away whatever you had started; nothing is sent until you press the option's Connect button.

Map each door to the location it belongs to. Two switches matter:

• Unlock from portal lets members open that door from their phone browser. It is off until you turn it on, deliberately: a web button works from anywhere, so it suits an interior door better than a street entrance. Every press is recorded with the member's name.
• Inside (exit) marks a reader on the inside of the kitchen. Without one, SpaceBloom can tell you when someone arrived but has to estimate when they left.

Using Kisi?

If your doors already run on Kisi, keep Kisi picked and paste an API key for your organization. Make the key in Kisi under My Account → API → Add API Key, signed in as an administrator of the organization — the key carries that person's permissions, and Kisi retires a key that goes unused for six months, so prefer an account that will stay. SpaceBloom stores it encrypted, shows only its last four characters, and because Kisi bills you for your places directly, doors on your Kisi organization are not added to your SpaceBloom subscription.

Three things work differently from the hosted flow:

• Groups, not codes. For every lock you map, SpaceBloom creates a Kisi group named SpaceBloom · <door> linked to that lock, and grants access by putting the member in it. You will see those groups in your Kisi console — leave them to SpaceBloom, and never add your own members to them by hand, since SpaceBloom removes anyone whose contract ends. Unmapping a door deletes its group.
• The Kisi app is the credential. Kisi has no standalone PIN. When you approve a member, SpaceBloom invites their membership email to your organization and Kisi sends the invitation — it comes from Kisi, not from you, so tell members to expect it. They sign in to the Kisi app with that email. Members who already have a Kisi card or account can be linked from the roster instead of invited again.
• One event webhook per organization. SpaceBloom registers the webhook that feeds the kitchen log. Kisi allows one per organization; if you already run one you will be asked to remove it first. Kisi switches a webhook off when deliveries keep failing — if that ever happens the Access tab says so and the log stays dark until you disconnect and connect again.

Replace API key and Check key work as for Seam. Disconnecting removes every assignment SpaceBloom made, deletes its webhook, and forgets the key; the members and the groups' locks stay yours.

Already using Seam?

If you already have your own Seam workspace — perhaps because you set up your locks or access system through Seam before SpaceBloom — choose My own Seam workspace instead of the hosted flow and paste an API key for that workspace (Seam Console → API keys). SpaceBloom then drives the access system connected there, and because Seam is billing you directly for those devices, doors on your own workspace are not added to your SpaceBloom subscription. If the workspace has more than one access system connected, you'll be asked which one belongs to this organization.

The key is stored encrypted and never shown again; the Access tab shows its last four characters. SpaceBloom registers its own webhook in your workspace so entries reach the kitchen log — you don't need to set anything up there. If you rotate the key in Seam, use Replace API key; Check key tells you whether the stored one still works, and whether the access system it was connected to is still in the workspace. If you removed and re-added that system in Seam, its id changed and every door load fails until you tell SpaceBloom which one replaced it: Check key offers the systems the workspace holds now, and Use this access system switches over while keeping your key and webhook. Members the re-added system still knows are carried over under their new ids (anyone SpaceBloom had suspended stays suspended); anyone it doesn't know is closed and needs approving again, and doors it doesn't offer are archived for you to re-map. Disconnecting revokes every credential SpaceBloom issued, removes that webhook, and forgets the key.

Who gets in

A member needs an active contract at a location they belong to, and that location needs a mapped door. Members ask for access from their portal and you approve them on the Access tab — nobody is enrolled automatically.

Access ends on its own when a contract is cancelled or runs out, and every night SpaceBloom re-checks everyone and revokes anything that no longer applies. You can revoke by hand at any time, and you must do that before removing a member — otherwise their code would keep working after they're gone.

Each member gets their own keypad code or phone key. Never hand out one shared code: it can't be traced to a person and revoking it means re-keying everyone.

Members who already have a badge

If a member already holds a badge, fob or code in your access system, don't issue them a second one. Once a system is connected, the Access tab lists Already in your access system — everyone in it who isn't linked to a member yet. Where an email matches exactly one member, press Link; where it matches several or none, pick the member yourself. Nothing is linked until you press the button. Someone you have suspended in your own system shows Link and reinstate instead — linking them opens their access again.

A linked credential works like one SpaceBloom issued: it follows the contract. When the contract ends, or you revoke by hand, the person is suspended in your access system (never deleted), and approving them again reinstates them. Every night SpaceBloom re-asserts a suspension it made, so un-suspending someone at the panel doesn't quietly reopen a door — if you want to manage that person yourself again, press Unlink, which hands them back exactly as they were. Disconnecting SpaceBloom also hands every linked person back rather than revoking them. You can't remove a member, or delete the organization, while a linked person is suspended by SpaceBloom — unlink them first, so nobody is left suspended with no way back.

The kitchen log

The Access tab shows every entry, who is in the kitchen right now, and how long each visit lasted. Where you have an inside reader those times are measured; otherwise a visit closes at the member's next entry elsewhere or after the assumed stay you set, and is marked estimated. It's an audit trail for disputes, not a billing meter.

One thing no system can see: someone holding the door for a colleague. Ask everyone to badge in individually — an inside reader is the only way to catch it after the fact.

Documents

The Documents tab is where you keep the paperwork that belongs to a member — a lease, a certificate of insurance, a health permit — and where you make new paperwork from your own templates. Every document sits on one member's profile. It is private to you until you share it, and once shared the member can open it on their member portal under Documents.

Owners and staff can both work here.

A member's details

Templates fill in what you know about a member, so it is worth a minute to record it. Open Members, click the member's name, and fill in Contact details: Full name, phones, Billing name, Tax id (EIN) and their billing address. These are your records — the member does not see or edit them — and an import from another platform fills in whatever its export carried. A detail you leave empty is simply left empty in a document.

Adding documents

On the Documents tab press + Add document (or use the same button on a member's page, where the member is already chosen):

1. Choose the Member, and a Location if the paper is about one.
2. Choose the file — PDFs, images, Word and Excel files, up to 25 MB each.
3. Give it a Name and any Internal notes (only you see those), tick Share with the member if they should see it now, and press Attach document.

To bring a member's whole folder across at once, select all of its files in the file picker — up to 50 at a time. Each document is named after its file, a progress line counts them off, and Stop after this file pauses the run; anything that did not attach stays selected, so pressing the button again picks up where it stopped.

Good to know

• Picking the same files twice adds nothing twice. The same file with the same name for the same member is recognised and skipped, so a run that was interrupted can simply be repeated.
• Several files at once are shared quietly. Sharing one document emails the member; sharing fifty in one go would be fifty emails, so SpaceBloom sends none — tell the member yourself that their archive is there.
• Files stay where they are. A document keeps the exact file you attached; every download is that same file, byte for byte.

Sharing a document

Open the document (click its name) and press Share with the member. It appears on their portal and they are emailed — once, the first time. If that email could not be delivered the page says so and offers Send the email again. Stop sharing takes it off their portal again.

A document stays on your records when a member leaves. A removed member can no longer open the portal, so they no longer see it.

What members upload

Members can upload their own documents from the portal — a PDF or a photo up to 10 MB, such as a renewed certificate of insurance. These arrive marked New from members (there is a filter for it on the Documents tab). Open one, check it, and press Mark reviewed. Until you do, the member can still remove it; after that it is part of your records.

Asking for a signature

Open a PDF document and use its Signature card:

1. Give them 7, 14, 30 or 60 days.
2. Tick I countersign after them for a lease or an agreement both sides sign.
3. Press Ask for a signature. This shares the document if it was not already, and emails the member a link.

The member opens the document on their portal, reads it, ticks that they agree to sign electronically, types their full legal name and presses Sign. If you chose to countersign, the card then offers you Countersign: open the document, agree, type your name. When everyone has signed, SpaceBloom builds the signed copy — your original pages, followed by a signature page and a certificate recording who signed, when, from where, and the fingerprint of the file they read — and both of you can download it.

While a request is open you can Send a reminder or Cancel the request. The member can also decline, with a reason you will see.

If something was signed on paper or in another system, use Mark as signed with an optional note ("Signed in person on Sep 12") instead of asking again.

Good to know

• A request expires at the end of its last day, in your organization's time zone. An expired request can simply be asked again.
• An open request freezes the document. It cannot be unshared, marked as signed by hand, or deleted until the request is signed, cancelled, declined or expired — and your organization cannot be deleted while one is open.
• Only PDFs can be signed. Turn a Word file into a PDF first, or make the document from a template, which always produces one.
• The owner or a staff member countersigns, under their own name. Only the owner can delete a signed record.
• The signed copy is a convenience, not the signature. The signatures are recorded the moment they are made; if the copy cannot be built (a password-protected PDF, for instance) they still stand, and the page says the copy is missing.

Templates

A template is a document with blanks in it — this lease is between «billingname» and… — that SpaceBloom fills in for a member and turns into a PDF on their profile. Open Documents → Templates.

There are two ways to make one:

• + Upload a Word file — a .docx you already have. This is the right choice for anything designed: a lease with your letterhead, numbered clauses, signature blocks. It comes out looking as it does in Word.
• Write one here — a simple editor with headings, lists, tables, links, your logo and an Insert field button. Good for a welcome letter or a one-page notice; it makes a clean, plain page.

Either way, give it a name and, if it only applies to one place, a Location. A template with a location is offered only for members of that location; Any location is offered for everyone. The location changes who is offered the template — not what gets filled in.

Writing the blanks

A field is just text. Open the template in Word, click where the member's name should go, and type {{member.fullName}} — two curly brackets, the field's name exactly as in the table below, two curly brackets. That is all: no Word "mail merge" setup, no special menu. When a document is made, those characters are replaced by the member's name.

This Lease is between {{member.billingName}} ("Tenant") and {{organization.name}}, starting {{contract.startDate}} at {{contract.price}} a month.

A few things that help:

• Copy the name from the table rather than retyping it. Capital letters do not matter; spelling does.
• Format the field the way the value should look. Make {{member.billingName}} bold and the name comes out bold.
• Use a field as often as you like, anywhere in the document — the body, a table, a header or a footer.
• The «name» spelling works too. Templates exported from Nexudus are written that way and need no changes. (To type the marks yourself: on Windows hold Alt and type 0171 and 0187 on the number pad; on a Mac, Option-\ and Shift-Option-\. The curly-bracket spelling is easier.)
• Writing the template in SpaceBloom instead? Don't type fields at all — put the cursor where the value goes, choose it under Field, and press Insert field.

The fields, in either spelling:

Templates that came from Nexudus work as they are. The full list, with every spelling SpaceBloom understands, is on each template's page under Fields you can use. The value takes on the formatting of the blank, so make the blank bold if the name should be bold.

When you upload a template its page shows What it fills in. A name SpaceBloom does not recognise is flagged unknown — usually a typo — and is left in the document exactly as written, so nothing is silently blanked out of a lease. Fix the Word file and use Replace the file.

Checking it

On the template's page, Preview fills it in for a real member (and one of their contracts, if the template uses contract details) and opens the PDF without saving anything. Do this once for every new template: it is where you catch a logo that moved or a clause that ran onto a fifth page.

Replace the file (or Save in the editor) makes a new version. Documents already made keep saying which version they came from. Archive retires a template without touching the documents made from it; Restore brings it back.

Making a document from a template

For one member: open the member's page, press Create from a template, choose the Template — and the Contract it is about, if it fills in contract details — and press Create document. It takes a few seconds to become a PDF and then appears in their documents. Tick Share with the member to send it now, or Ask for a signature to share it and send the signing link in the same step.

For many members: open the template and press Create for many members. Everyone the template is offered to is listed and ticked, with the contract their document will be about (you can change it where a member has several). Members with no contract cannot be included in a template that needs one, and anyone who Already has one from this template starts unticked so a second run does not make second copies. Filter by location if you like — Create acts on the members you can see — choose Share with each member or Ask for a signature, and press Create N documents, up to 100 at a time.

The documents are made a couple at a time, so a hundred takes several minutes. You can leave the page; each one lands on its member's profile, and coming back shows how the run went. Anything that needs a look — an email that could not be delivered, a contract that was cancelled meanwhile — is written beside that member.

Good to know

• A template that fills in contract details needs a contract. Give the member a contract first, even a draft one.
• Limits. An organization can make 500 documents from templates in a day (previews count); after that, making more waits until tomorrow. It can also send 500 document emails a day, shares and signature requests together; past that a document is still made and shared, but its email is not sent, and the page says so.
• Keep designed documents in Word. The built-in editor cannot reproduce a designed lease, and it does not need to — upload the Word file.
• If a field comes out as «something» in the PDF, the template uses a name SpaceBloom does not know. Its page shows which.

Moving your documents over from another platform

1. Members first. Import or invite your members (see Moving from another platform) so there is a profile to attach to, and fill in their contact details — the import does this where the export carries them.
2. Templates. Upload your Word templates as they are. If all you have is a PDF, open it in Microsoft Word (File → Open) and save it as .docx — Word rebuilds real paragraphs, where other converters produce text boxes that cannot be filled in. Then read it through: a scanned PDF comes back with misread letters, and its blanks have to be typed in again.
3. Existing files. Download each member's files from the old platform and attach them from the member's page, a folder at a time. Attach them unshared, or shared — no email goes out for a batch either way.
4. Signed paperwork. For anything already signed elsewhere, use Mark as signed with a note such as "Signed in Nexudus, 2025".

Your free trial

Your organization is free to set up — name, web address, logo, members. The 30-day free trial starts the day you add your first location (locations are what SpaceBloom charges for: $99 per location and $2 per member each month). During the trial everything works exactly as it will afterwards, including member payments through your own Stripe or Forte account.

We email you 7 days before the trial ends, the day before, and when it ends. You can start your subscription at any point from Account → Subscription. Subscribe at least two days before the end and your card is first charged on the day the trial would have ended, not when you enter it; in the final two days (or after it ends) the first charge happens when you subscribe — the page tells you which applies.

If the trial ends before you subscribe, billing pauses: no new contracts, invoices or charges until you subscribe. Nothing is deleted — your members, locations, plans and invoices stay put, members can still pay invoices you already issued, and you can export your data at any time. Subscribing picks up where you left off.

Exporting your data

You can download everything you have in SpaceBloom at any time from Account → Export your data. One click builds a single .zip covering your organization.

What's inside

• One folder for your organization (sites/<your-address>/) with:
  • members.csv, locations.csv, plans.csv, products.csv — your roster and catalog.
  • contracts.csv, invoices.csv, payments.csv — your billing history.
  • site.json, billing-settings.json — your organization and billing configuration.
  • data.json — a complete, lossless copy of all of the above.
• manifest.json, account.json, and a README.txt at the top level.

Amounts are shown in dollars in the CSVs (and in exact cents in data.json). The CSV columns line up with the import format, so an organization's catalog and members can be re-imported elsewhere.

Good to know

• It always works, even if your SpaceBloom subscription has lapsed — your data is yours to take at any time.
• No secrets are included. Payment credentials, your encrypted gateway key, and members' saved card/bank tokens are never in the export — only the safe details (like a card's brand and last four) appear.
• The download link is private and short-lived (about 15 minutes). Generate a fresh export whenever you need one; old links simply expire.