Skip to main content
Every Springwinter account belongs to an organization. All members of the organization share the same projects, AWS account connection, and GitHub installation — there is no per-member resource isolation. This model is designed for teams that deploy and operate shared infrastructure together.

How Organizations Work

Shared Projects

Every project and all its resources — web servers, workers, databases, caches, and more — are visible and editable by all organization members.

Shared Connections

The AWS account connection and the GitHub installation are organization-wide. All members deploy using the same role and the same GitHub App installation.

Creating an Organization

The first person to sign up at springwinter.dev/auth?mode=signup creates the organization automatically. No additional setup is required — the organization is provisioned as part of the sign-up flow, and the founding member can immediately invite others.

Inviting Members

1

Open Settings → Team

Open Settings → Team from the dashboard.
2

Enter the new member's details

Enter the new member’s email address. Springwinter generates a password and sends an invitation email. You do not choose or share their initial password.
3

Save the invitation

Select Add person. Springwinter sends the invitation and saves the member account. If email delivery fails, the invitation reports an error. The member signs in using the password in the email.
4

Member changes their password

The new member should update their password after their first successful sign-in through the account settings page.

What Members Can See and Do

All members have equal access to the organization. The table below summarizes what is shared.

Removing a Member

1

Open Settings → Team

Navigate to the Team page in Settings.
2

Deactivate the member

Find the member in the list and click Remove. This marks the account as inactive — the person can no longer sign in.
Removing a member marks them as inactive but does not delete any resources they created. All projects and deployments they owned remain accessible to the rest of the team. Additionally, their email address cannot be reused to create a new account within the same organization.
All members currently have equal access to all organization resources. Role-based access control (RBAC) — such as read-only or project-scoped permissions — is not available at this time.