Getting started
Account
Account Settings at /account covers your identity and credentials. Spend controls live separately at /budgets.
Account settings
- Public Profile
- Display name, avatar, bio, role, designation, and organization. The name is how the app addresses you: the dashboard greeting, the sidebar, the admin user list, the audit log’s actor column and the per-person spend breakdown all read it. Without one, each of those falls back to the local part of your email address.
- Account
- Your current sign-in email and provider, read-only.
- Change Password
- Set a new password. You stay signed in on the current device.
- Change Email
- Enter a new address; the change takes effect after you click the confirmation link sent to it.
- Session
- Sign out of AgentSwarms on this device.
- Delete Account
- Permanently deletes your account and all associated data — agents, swarms, knowledge bases, runs. Requires explicit confirmation and cannot be undone.
Budgets
Spend controls live at Budgets (linked from the sidebar), not on the account page:
- Monthly Hard Cap
- A workspace-wide dollar cap. Agents refuse new requests once month-to-date spend reaches it. The card shows current spend against the cap.
- Spend Alerts
- Notifications before you hit the cap, so the hard stop is never a surprise.
- Agent-Specific Limits
- Per-agent daily caps, with an optional auto-disable when an agent hits its limit.
Budget settings save automatically as you change them. Per-agent budget caps can also be set inside the Agent Builder's guardrails section.
What belongs to your account
| Owned by you | Shared with you |
|---|---|
| Agents, swarms, knowledge collections, data tables, prepared tables, dashboards, secrets, notebooks, API and embed keys | Anything an administrator granted you read-only access to — shown with a Shared badge |
Shared resources cannot be edited or deleted by the recipient; the controls are hidden and writes are blocked by the database regardless. Grants are managed in Access control.
Deletion and departure
Careful
Deleting a user cascades to the content they own. If someone leaves and their agents, collections or dashboards matter, transfer or duplicate them first — or ban the account instead, which blocks sign-in while preserving everything.
Ban is almost always the right first move when someone leaves:
| Ban | Delete | |
|---|---|---|
| Can sign in | No | No |
| Their agents, collections, dashboards | Kept | Deleted with them |
| Grants they held | Inert while banned | Removed |
| Reversible | Yes — unban | No |
The audit trail outlives the account
Deletion does not erase the record of what the person did. Audit events keep their attribution: the link to the account is cleared, and the email captured at the time of the action remains on the row — so a leaver cannot be used to launder the history of an action, and a compliance question about a departed employee is still answerable. Everything else they owned is genuinely gone.
Retention for that trail is set separately — see Analytics.