The organization is the top of your Aggrandize hierarchy — everything else (members, teams, pipelines, deals) lives under it. Most of the time you set it up once and never touch it again. But two lifecycle actions are owner-controlled and live in their own places under Settings: renaming the org, and requesting permanent deletion. Both are reserved for the Owner role — not even Admins can perform them.

Renaming your organization

Open Settings → Organization. The card only appears in Settings for the Owner; Admins and Members don't see it.

The page has a single field: the organization's current name, pre-filled. Edit it and click Save.

• The name can be up to 100 characters. As you type, the counter on the right tracks how many you've used — it flips red if you exceed the limit, and Save won't fire until you trim back.
• The new name applies everywhere immediately: the sidebar header, the org switcher, the Members page, billing receipts, exported file headers, and admin views.
• A small green "Saved" indicator appears next to the Save button on success. There's no email, no confirmation step — renames are low-stakes.

What renaming doesn't change

Renaming the org changes the display name only. A few things it does not change:

• Your members or roles. Everyone keeps their access exactly as it was.
• Existing data. Contacts, companies, deals, emails, pipelines — all untouched.
• Stripe subscription details. Your billing email, payment method, and invoice history all live on the Stripe customer record and aren't tied to the display name. Future invoices will still come from the same Stripe customer.
• Your URL. Aggrandize URLs don't bake the org name in; you log into crm.aggrandizelabs.com regardless of org name.

If a non-owner navigates directly to /settings/organization, they don't get an empty form — they get an explicit gate:

Requesting permanent deletion

Deleting an organization is a separate flow that lives at the bottom of the main Settings page in the owner-only Danger Zone card. (It's intentionally one click away from the rename form, since the two are very different commitments.)

Click Delete Organization and a confirmation dialog asks you to retype the organization's name and optionally note a reason. The Request Deletion button stays disabled until the typed name matches exactly:

When you confirm, three things happen:

1. Your Stripe subscription is canceled. No further invoices are issued.
2. A 30-day grace clock starts. During this window the org keeps working at full capacity — you can still log in, run Data Export, and recover any soft-deleted records from Trash. This is your evacuation window.
3. A deletion is scheduled. At the end of the 30 days, the organization and all of its data are permanently removed. The deletion is irreversible.

While a deletion is pending, the Danger Zone card switches to a status state showing the scheduled date and days remaining, with a single primary action to Cancel Deletion:

Clicking Cancel Deletion at any time before the scheduled date reverses the request. Your subscription does not auto-restart — you'll need to reactivate it from Settings → Billing to resume using paid features, but your data, members, and pipelines all stay intact.

Before requesting deletion — checklist

A few things to walk through before you click the button:

• Run a full Data Export. Pull a ZIP of every table — contacts, companies, deals, tasks, activities — for your records. Once the 30-day window closes, this data is gone permanently.
• Check Trash. If you've been hovering between deleting and not deleting, make sure no important soft-deleted record gets caught in the purge.
• Confirm your Stripe invoice history is downloaded. Open the Billing Portal and download PDFs of every invoice you may need for accounting. After the org is gone, the Stripe customer record is too.
• Tell your team. Members will lose access the moment deletion completes. If anyone needs to keep their personal contact list or emails, they should pull those into a private export now.

What deletion deletes — and what it doesn't

• CRM data — contacts, companies, deals, tasks, activities, pipelines, stages, teams, classifications, custom fields. All permanently removed.
• Email links — the links between CRM records and email threads are deleted. The emails themselves continue to live in your mailbox provider (Outlook or Gmail).
• The Stripe customer record — canceled at request time, scrubbed at the 30-day mark.
• Your individual Aggrandize login — survives. You can still log in afterwards; you just won't belong to this org any more. If you belong to another org, you'll see only that one in the org switcher. If you don't, you'll see the onboarding gate and can spin up a fresh org.

Who can do what

Both lifecycle actions are deliberately scoped to a single human: the Owner. If you need to hand the org to a new Owner (e.g., founder departure), open the Members page and change roles there before attempting either action.