Feature: Organization membership metadata
Description:
Auth0 supports metadata on users and organizations. We would like to store metadata on the membership between a user and an organization as well.
Some attributes belong specifically to that relationship. For example:
-
A membership start date and end date.
-
The department the person belongs to within that organization.
-
An employee number, customer reference, or other organization-specific identifier.
The same user can belong to multiple organizations, with different values for each membership. These attributes therefore fit naturally on the membership itself.
Why user app_metadata does not meet this requirement
Auth0 documents a 10 KB size limit for user profiles. Storing metadata for every organization membership in the user profile consumes that shared allowance and makes profile size grow with the number of memberships. This creates a scalability constraint even when each membership contains only a small amount of data. User profile size limits.
We can represent this data in a structure within app_metadata; the structure itself is not our concern. The concerns are the upper profile size limit and where the data belongs. Attributes of a user’s relationship with an organization should live on that membership, independently of the user’s global profile.
We want to keep this information in Auth0. Storing it in an external database introduces another system and synchronization work for data that belongs with the membership.
Requested functionality
Please add a custom metadata object to organization memberships, with:
-
Management API support to read, create, update, and remove metadata.
-
Access to the current membership’s metadata in Post-Login Actions.
-
Dashboard support to view and edit membership metadata.
-
Documented limits and update semantics, including how to remove individual keys.
-
A separate membership metadata allowance that does not count toward the user profile’s 10 KB limit.
For example, a membership could contain:
{
"user_id": "auth0|123",
"organization_id": "org_abc",
"metadata": {
"start_date": "2026-01-01",
"end_date": "2026-12-31",
"department": "Treasury",
"employee_id": "EMP-456",
"external_reference": "REF-789"
}
}
The initial request is for storage and retrieval. Automatic enforcement of start and end dates could be a separate enhancement, but this can also be enforced in Actions.
This would let us keep membership information alongside the relationship it describes, without consuming the user profile’s limited storage or maintaining an external metadata store.