Macha Account & Organization Settings, Explained

This is a complete, plain-English tour of every account and organization setting in Macha — what each control does, when to change it, and the handful of settings that have consequences you can't easily undo. If you're setting up a workspace for a team, or just want to know what that Delete organization button actually does before you go near it, start here.

A quick mental model first: in Macha, account settings are about you (your profile, your privacy, your data), while organization settings are about the workspace (defaults, members, billing) that everyone in it shares. A single login can belong to several organizations, so it helps to keep that distinction straight.

Every setting at a glance: who can change it, and can you undo it

Before the section-by-section tour, here's the whole settings surface on one screen. The two columns that matter most are Who can change it (Admin vs any Member) and Reversibility — because the handful of settings that are Permanent or Destructive are the ones worth slowing down for. Nothing else in this post is as load-bearing as this table.

Read this top to bottom and the pattern is clear: almost everything in Macha is a safe, reversible toggle. Only the bottom two rows are destructive, and even those run on a 30-day clock you can stop. The sections below walk each one in detail.

Profile settings: who you are

Your profile controls how you appear across the platform. There are only two fields, and the difference between them matters.

• Display name — your name as shown to other members of the organization. Change it any time.
• Email — the address you log in with. This one is not editable after account creation, because it's tied to your authentication. If you need to move to a different email, the clean path is to invite the new address as a member, hand off any admin duties, and delete the old account rather than trying to mutate the login in place.

That second point trips people up, so it's worth saying plainly: pick the email you actually want to keep when you first sign up. It's your identity in Macha, not just a contact field.

Organization settings: the defaults everyone inherits

Organization settings apply to all members and agents in the workspace. The headline control here is the one that touches every agent you'll ever build.

The default AI model

The default AI model sets which model new agents are created with. It's a default, not a lock — any individual agent can override it in its own configuration — but getting it right saves you from setting the model by hand on every agent. Macha supports models from OpenAI, Anthropic, and Groq, so you're picking from a real spread of speed-versus-capability trade-offs rather than a single vendor's ladder.

Here's the part that connects this setting to your bill: in Macha, credits are charged per complete agent response — one charge for the final answer, no matter how many tool calls the agent made to get there — and the credit cost depends on the model. Costs range from roughly 0.5 to 9 credits per response by model, with the default GPT-5.4 Mini at 1 credit. So the org default isn't just a quality decision; it's the baseline cost of every new agent until someone overrides it.

A sensible default policy: set the organization default to a cheap, fast model like GPT-5.4 Mini, then deliberately upgrade only the specific agents that genuinely need more reasoning. A high-volume triage agent and a complex multi-step resolver should not be paying the same per-response rate. We go deeper on model-to-task matching in the Macha on Zendesk playbook and the docs.

Team and billing shortcuts

The organization view also surfaces quick links into Team and Billing — both important enough that they get their own sections below, and their own pages in the docs.

Team: roles, invitations, and multi-org

Macha keeps access control deliberately simple. There are exactly two roles, and the line between them is "can use" versus "can change."

Inviting someone is a three-field action: open the Team section, enter their email, pick a role, send. They get an email, accept, log in, and land in your workspace with exactly the access the role allows. You can change a member's role or remove a member at any time from the same screen.

One reassurance worth knowing: removing a member does not delete their Macha account. They lose access to your organization, but they keep their login and any other organizations they belong to.

Multi-organization support

A single Macha account can belong to multiple organizations, and nothing is shared between them — each org has its own agents, connectors, tools, data, and billing. When you log in you choose which org to work in, and you can switch any time.

This is the feature that makes Macha workable for agencies and consultants: keep each client's workspace fully isolated under one login, with separate billing and zero data bleed between accounts. For the full breakdown of roles and invitations, see the Team docs in the documentation.

Billing: plans, credits, and alerts

Billing is admin-only and lives under Settings. From here you see your current plan, credit balance, and usage, and manage the subscription.

A few mechanics that are easy to get wrong if you don't know them:

• Upgrades check out inside Macha. Click upgrade, complete checkout, done — no external redirect to a separate billing portal.
• Downgrades take effect at the end of the current billing period, not immediately, so you don't lose paid-for capacity mid-cycle.
• Downgrading below your current usage won't delete anything. If your existing agents or connectors exceed the new plan's limits, they keep working — you just can't create new ones until you're back within the limits.
• Usage alerts go to every admin by email at 50%, 80%, and 90% of credits used, once per threshold (no duplicate spam). The 90% alert is the one that means "top up or upgrade before agents start hitting the wall."
• Enterprise bypasses credit checks entirely, so agents keep running regardless of balance — useful when uninterrupted service matters more than a hard spend cap.

We deliberately don't quote prices here because they change; the live numbers and what each tier includes are on the pricing page. The one framing to hold onto is that credits are consumed per AI action (a completed agent response), which is why the org default model from earlier has such a direct line to this screen.

Privacy: your data, export, and the delete buttons

This is the section to read slowly, because two of its actions are destructive and one of them is irreversible after a grace period. Macha's privacy controls are built to satisfy real data-subject rights, not just to look compliant.

Download your data

Request a full export of your data in JSON — your profile information, conversations, and everything else associated with your account. The export is generated and made available for you to download. This maps directly to the GDPR Article 20 right to data portability, which entitles a data subject to a copy of their personal data in a "structured, commonly used and machine-readable format" (gdpr-info.eu). JSON qualifies. Use it for compliance requests, migrations, or just your own audit trail.

Delete your account

If you decide to leave, account deletion runs on a 30-day scheduled process:

1. Deletion is scheduled for 30 days out from your request.
2. During that window you can cancel and restore the account.
3. After 30 days, your account and all associated data are permanently removed.

That grace period is a deliberate safety net over the GDPR Article 17 right to erasure (the "right to be forgotten"), which generally requires erasure to be honored within a month of a valid request (gdpr-info.eu). The 30-day soft-delete window is the recoverable-by-design version of that.

If you belong to multiple organizations, deleting your account removes your access to all of them. Transfer any admin responsibilities before you request deletion — otherwise you could leave an org with no admin.

Delete organization

Organization deletion is admins only and follows the same 30-day scheduled, cancellable pattern. When it completes, all organization data is permanently removed — agents, connectors, conversations, documents, triggers, and custom tools — and every member loses access. This is the single most consequential button in the product. Treat it accordingly: export anything you might want first, and confirm no one else is mid-project in that workspace.

Policies

The privacy panel also links out to how Macha actually handles data: the Privacy Policy, Terms of Service, Cookie Policy, Data Processing Agreement, and Refund Policy. The DPA in particular is the document your own compliance or procurement team will ask for.

Watch-outs: the settings with consequences

Most settings are forgiving. A few are not — here's the honest list:

• Your login email is permanent. Choose it carefully at signup; you can't edit it later.
• The org default model silently sets cost. Change it to an expensive model and every new agent inherits that per-response price until overridden. Default low, upgrade deliberately.
• Deleting your account ≠ deleting an org's data. If you're the sole admin and you delete your account, the organization can be left stranded. Hand off admin first.
• Org deletion is total and shared. It wipes the workspace for everyone, not just you. It's recoverable for 30 days, then it's gone for good.
• Downgrades are end-of-period, not instant. Plan the timing if you're trying to cut spend before a renewal.

None of these are traps — they're just the settings where "undo" either doesn't exist or runs on a clock.

FAQ

Can I change my login email in Macha? No. Your email is tied to authentication and is fixed after account creation. To switch, invite the new email as a member, transfer admin duties, and delete the old account.

What does the default AI model setting actually do? It sets the model new agents are created with. Each agent can still override it in its own config. Because credits are charged per agent response and cost varies by model, this default also sets the baseline cost for new agents.

What's the difference between an Admin and a Member? Admins can change everything — agents, connectors, tools, triggers, team, billing, and settings. Members can use agents and chat and view configuration read-only, but can't change anything or touch billing.

What format is the data export, and is it GDPR-compliant? It's a full JSON export of your profile, conversations, and account data — a machine-readable format that satisfies the GDPR Article 20 right to data portability.

Can I recover a deleted account or organization? Yes, within the 30-day grace period — both account and organization deletion are scheduled 30 days out and can be cancelled in that window. After 30 days, removal is permanent.

Who gets billing and usage alerts? All organization admins, by email, at 50%, 80%, and 90% of credit usage — once per threshold.

Get set up right

The settings screens are a five-minute job that saves you weeks of cleanup: pick the right login email, set a sensible default model, invite your team with the correct roles, and know where the privacy controls live before you need them. Start a 7-day free trial, no credit card required, or read the full Account docs for the step-by-step on Team, Billing, and Settings. More walkthroughs like this live on the blog.

Written by Abbas (Customer Support & AI, Macha) · Reviewed by Ankeet Guha (Co-founder & CTO) · Published 2026-06-24 · Last updated 2026-06-24.