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
Click your organization name in the top navigation and select Settings, then choose the Team page.
2
Enter the new member's details
Type the new member’s email address and set a temporary password for their first sign-in. Springwinter does not currently send automated invitation emails, so share the credentials directly with the new member over a secure channel.
3
Save the invitation
Click Add member. The new account is created immediately and the member can sign in with the temporary password you provided.
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.
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.