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

# Member management overview

> Understanding Stytch Organizations and Members

export const member = "Represents an individual end user's account within a given Organization, uniquely identified within that Organization by their email address.";

export const organization = "Represents an instance or tenant in your application, typically mapping to each of your top-level customers.";

In your Stytch project, each **Organization** represents a tenant in your application, typically 1:1 with one of your customers.  An Organization contains one or more **Members**, which represent the users of your application.

<Columns cols={2}>
  <Card title="Organizations" icon="building" href="/api-reference/b2b/api/organizations/organization-object">
    A tenant in your app, typically 1:1 with one of your customers.
  </Card>

  <Card title="Members" icon="user" href="/api-reference/b2b/api/members/member-object">
    An individual end user within an Organization.
  </Card>
</Columns>

### Overview

```mermaid theme={null}
---
config:
  title: Relationship model between Orgs & Members
  layout: elk
  elk:
    mergeEdges: true
---
erDiagram
  p["Your Stytch project"]

  o1[Organization] {
    string id "org-001..."
    string slug "acme"
  }

  o2[Organization] {
	string id "org-002..."
	string slug "stytch"
  }

  m1[Member] {
    string id "member-583..."
    string email "ada@stytch.com"
  }

  m2[Member] {
    string id "member-9a1..."
    string email "ada@stytch.com"
  }

  m3[Member] {
    string id "member-30w..."
    string email "baker@stytch.com"
  }

  p ||--|| o1 : ""
  p ||--|| o2 : ""
  o1 ||--|| m1 : ""
  o2 ||--|| m2 : ""
  o2 ||--|| m3 : ""
```

## Organization management

Settings on the Organization object control how Members can authenticate (ie. forcing all Members to use OAuth), and how new Members can be provisioned (ie. allowing anyone with an `@example.com` email to join an Organization).

These settings are covered in more detail in the following guides:

<Columns cols={2}>
  <Card title="Configure Auth Methods" icon="key-round" href="/multi-tenant-auth/enterprise-ready/org-management/configure-auth-methods">
    Control which authentication methods can be used by Members of an Organization.
  </Card>

  <Card title="Invite Members" icon="user-plus" href="/multi-tenant-auth/enterprise-ready/org-management/invite-members">
    Invite new Members to an Organization via email invitation or JIT provisioning.
  </Card>
</Columns>

<Card title="Admin Portal" icon="table-2" horizontal href="/multi-tenant-auth/enterprise-ready/admin-portal">
  Add UI to your application to allow end-users to manage their own Organizations and Members.
</Card>