> ## Documentation Index
> Fetch the complete documentation index at: https://docs.springwinter.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Your Team Members and Organization in Springwinter

> Invite members to your Springwinter organization so they can share projects, AWS account connections, GitHub installations, and deployed resources.

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

<CardGroup cols={2}>
  <Card title="Shared Projects" icon="folder-open">
    Every project and all its resources — web servers, workers, databases, caches, and more — are visible and editable by all organization members.
  </Card>

  <Card title="Shared Connections" icon="plug">
    The AWS account connection and the GitHub installation are organization-wide. All members deploy using the same role and the same GitHub App installation.
  </Card>
</CardGroup>

## Creating an Organization

The first person to sign up at [springwinter.dev/auth?mode=signup](https://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

<Steps>
  <Step title="Open Settings → Team">
    Click your organization name in the top navigation and select **Settings**, then choose the **Team** page.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Save the invitation">
    Click **Add member**. The new account is created immediately and the member can sign in with the temporary password you provided.
  </Step>

  <Step title="Member changes their password">
    The new member should update their password after their first successful sign-in through the account settings page.
  </Step>
</Steps>

## What Members Can See and Do

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

| Resource | Shared? |
| - | - |
| Projects and all their resources | ✅ Yes — all members |
| AWS account connection | ✅ Yes — all members |
| GitHub installation | ✅ Yes — all members |
| Team member names and email addresses | ✅ Yes — visible on the Team page |
| API tokens | ✅ Yes — tokens are organization-scoped and visible to all members |

## Removing a Member

<Steps>
  <Step title="Open Settings → Team">
    Navigate to the Team page in Settings.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Warning>
  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.
</Warning>

<Note>
  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.
</Note>