General
The General panel is the top of Team Settings. It holds two settings, in this order:- Team name — the display name for the tenant.
- Delete team — a destructive action that removes the team and everything inside it.
Team name
The team name is your tenant’s visible label: it appears in the team switcher, in invitation emails, in audit logs as the context for administrative events, and anywhere the platform has to refer to “your organization”. Use the name of the company or the business unit the team represents. To change it- Go to Team settings → General.
- Edit the Team name field.
- Click Save.
The team name is not the same as a Custom Domain. The team name is a label; the custom domain is the hostname where users reach the app. See Custom Domain.
Delete team
Deleting the team is permanent and irreversible. It removes:- The team record itself and any vanity URL / custom domain bound to it.
- All users and invitations scoped to the team (user records in other teams are not affected).
- All products provisioned on the team — TrustGate gateways, routes, API engines, endpoint integrations, browser integrations, SIEM configurations, audit log history, SSO and SCIM configuration, group mappings, password policy, feature flags.
- All traffic logs, decisions, and evidence associated with those products. Exports that have already been pushed to your SIEM remain in your SIEM.
- Any hybrid data plane previously connected to the team is unlinked from the team. Infrastructure running inside your own cloud account is not touched by NeuralTrust — you need to de-provision it yourself from AWS / GCP / Azure after the team is deleted.
- Go to Team settings → General.
- Click Delete team.
- Confirm the destructive action in the dialog.
Before deleting
If the team holds production workloads, do these first:- Export audit logs you need to retain (or confirm they’ve been forwarded to your SIEM).
- Rotate or revoke any long-lived API keys handed out to apps, so they don’t error silently after deletion.
- De-provision integrations on the client side (browser extensions, endpoint MDM profiles, PAC URLs, client certs) — once the team is gone the traffic from those clients will be refused.
- If you’re on hybrid, de-provision the data plane from your cloud account after unlinking.
Alternatives to deletion
Before deleting, consider whether one of these is what you actually want:- Remove a specific user or product access — handle in Users, not here.
- Enforce SSO-only and revoke legacy passwords — use SSO + Password Policy.
- Stop ingesting a specific data plane — unlink it from Advanced rather than deleting the whole team.
Related
- Users — manage members, invitations, and roles.
- Custom Domain — change the hostname users reach the app on.
- Audit Logs —
team.settings.updatedandteam.deletedevents are recorded here.