> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinba.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Organizations & Member Invitations
> The user journey from inviting a member to an organization to them joining it
## Overview
Jinba has an "Organization" layer that spans multiple products (Jinba Flow, Jinba App, and others), which centrally manages the invitation and joining of members.
* There are two roles within an organization: **MEMBER** and **OWNER**.
* Only global administrators can create new organizations. Regular users cannot create organizations.
## Inviting a member (as the owner)
From the Members section on the organization detail page, use "Invite Member" to select a role (MEMBER / OWNER) and send an invitation to an email address.
* Invitations expire after **7 days**. An invitation can only be resent after it has expired.
* To cancel an invitation, use the "Cancel Invitation" button on the pending row in the member list.
* The SSO section on the organization detail page contains sign-in links for each product (such as Jinba Flow). The link format is `{product URL}/signin?tenant={organization slug}`.
## Signing up after receiving an invitation (invitee without an existing account)
The invitation email does not contain a unique invitation link. Instead, it explains to log in and open the organization list (/organizations) to accept the invitation, and includes the URL of the signup page.
If the invitee does not have an account, they register a name, email address, and password on the signup page. At this point they are not automatically signed in, and a confirmation (verification) email is sent instead.
## Verifying email and joining the organization
Opening the link in the verification email (valid for 1 hour) automatically signs the user in and takes them to the organization list page.
The organization list shows a card for any pending invitation whose email address matches the signed-in user's email. Clicking "Accept" completes the join and navigates to the organization page.
* Accepting an invitation requires the user's email to already be verified.
* An invitation cannot be accepted if the invited email address does not match the signed-in account's email address (case-insensitive).
* Only shared organizations are shown in the organization list. The Personal Organization automatically created at signup is not shown.
This page describes the flow from the administrator's side. For the invitee's walkthrough of first access to Jinba App Neo — from the invitation email through to opening a workspace — see [First Login](/en/pages/jinba_app_neo/first-login).
When SSO is enabled for an organization, its members sign in through SSO and join without going through this individual invitation flow. Deployments without SSO (including the standard Jinba App Neo deployment) use the invitation flow described above.