Skip to main content
A Towbar installation has one team. The person who completes onboarding becomes its first Admin. Only Admins can open Manage → Team Settings. The sidebar groups General and Members under Account, followed by API Keys, Audit Logs, and SSH keys under Security.

General

Use General → Team details to update the team name and description. The name appears below your display name in the sidebar. The description is optional.

Members

The Members table shows each person’s name, email, role, and membership details. Use the row actions to edit a name, change a role, or remove a member. Email changes belong to the user’s Email & Password settings, where the new address must be confirmed. Members cannot deploy workloads, prepare servers, run backups or restores, manage provider authorizations, or reveal existing secret values. Hidden menu items reflect these permissions; API and MCP requests follow the same limits. Towbar keeps at least one Admin in the team. You cannot remove or demote the last Admin. Removing a member ends their sessions and revokes their personal keys. It does not erase deployment history or reactivate old keys if the person joins again.
Manage members and pending invitations from separate tables.
Manage members and pending invitations from separate tables.

Manage members and pending invitations from separate tables.

Add a user directly

Choose Add user, enter their name and email, choose a role, and set a temporary password. Share it through a secure channel outside Towbar. Towbar does not email the password. The person must replace it on first sign-in before using the dashboard. This option works without SMTP. It does not prove ownership of the email address.

Invite someone by email

Choose Create invite, enter the recipient’s email, and select a role. Invitations expire after seven days and only work for the specified email address. The Pending Invitations table lets you copy a link, resend an invitation, or revoke it. Resend and Revoke ask for confirmation. Resending replaces the old invitation, so share the new link if you had copied the previous one. A new recipient verifies their email with a one-time code before creating their account. Someone who already has an account signs in with the invited address before accepting. Opening a link alone does not accept the invitation. Configure SMTP before using invitations. A Sent to mail server status means the mail server accepted the message; check the recipient’s mailbox if it has not arrived. A revoked invitation, or one issued by an Admin who was later removed or demoted, cannot be accepted.

Team API keys

Team keys are for shared automation. They belong to the team and keep working when their creator leaves. Any Admin can review or revoke them under Team Settings → API Keys. Choose Read-only or Edit access. Administrative permissions are a separate choice available only to Admins. Use an expiry and give the key a name that identifies its consumer. Copy it when it is created; the full token is shown once. For individual scripts and MCP clients, use Personal API Keys. See keys and permissions for the access limits and rotation procedure.

Role changes and queued work

A role change takes effect on subsequent requests. Personal key permissions are capped by both their saved grants and the owner’s current role. Demotion narrows those grants; promotion does not restore them automatically. A Member’s repository sync or branch-mapping change pauses runtime automation. An Admin must review the mapping in the repository’s Auto-deploy settings before enabling deployments, previews, and scheduled backups. Towbar also checks permission before queued work starts. A removed member or revoked key can therefore cause pending work to stop. Revoking access cannot undo work that has already completed.

Audit logs

Open Security → Audit Logs to browse captured activity across the team. Each row shows the event label and stable dot-notation slug, the acting user or system, the target, and the timestamp. Select the event name for IDs, request attribution, and event-specific metadata. Filter by event type or user, or search by event label, slug, user name, email, target ID, event ID, or request ID. Filters work together and reset the table to the first page. Use Previous and Next to browse older records. The first page refreshes automatically. Only Admins can read team-wide audit history. API keys and MCP cannot access this browser-only view. Audit records retain events for former team members, while credentials, tokens, and raw provider responses are excluded from the returned metadata. This page displays events captured by Towbar; it does not retroactively reconstruct actions that were not recorded.
Last modified on September 21, 2026