Skip to main content
Privy’s user management system can be used model organizations as authenticatable entities that can own and take actions with wallets. Individuals within the organization can authenticate as the organization’s Privy user, via a shared ID for the organization included on the individual’s JWT.

​
Authentication setup

To model organizations as Privy users, you must configure your authentication service to issue JWTs to individuals that contain:
  1. Organization ID claim: an ID for the organization they belong to
  2. Individual ID claim: a unique ID for the individual
The ID in the organization ID claim should be shared across all of the users within the same organization. You must then configure JWT-based auth in the Privy Dashboard and set the following values:
  1. User ID claim: set this field to the organization ID claim on your JWTs
  2. Sub-user ID claim: set this field to the unique individual ID claim on your JWTs
In total, this maps your service’s organization IDs to Privy’s user IDs to allow each organization to be modeled as a single user.

​
Organization user

When modeling organizations as users, all organizations should have a unique organization ID. To create the organization user, simply create a Privy user with a linked_accounts array that contains a single entry: an account of type: 'custom_auth' with custom_user_id set to the organization ID. This creates a Privy user representing the organization, that can be accessed by multiple individuals with JWTs containing the organization ID.

​
Individual sub-users

When an individual intends to take action with an organization’s wallet, they may authenticate with the Privy API using the JWT issued by your authentication service. Privy will verify the JWT and associate the individual to the organization’s Privy user via the organization ID stored on the user’s JWT. If the JWT is valid, the user will be granted the ability to take action with that organization’s wallets. To maintain auditability, Privy also logs the individual’s unique sub-user ID for the request, so that the action taken by the organization’s Privy user can be traced to an individual person.