Ability to store Organization Metadata in JSON format like app_metadata

Feedback
1

Feature: Ability to store Organization Metadata in JSON format like app_metadata or ability to store key-value pairs beyond the current limitations.

Description: Organization Metadata has currently three limitations listed below.

  • Support only a key-value format
  • Maximum of 255 characters for KEY and VALUE
  • Maximum of 10 metadata pairs

Because of these limitations, there is a risk adopting Organization Metadata while recognizing its convenience.

Use-case:
Actions can be written simply without using if statement. The source code below is an example. Of course, it can be achieved in the current situation, but we recognize that there is a risk in using Organization Metadata and hesitate to use it because of the limitations especially maximum of 10 metadata pairs.

  // before
  const org_name = event.organization?.name
  let sender_name
  if (org_name == "org1") {
     sender_name = "org1 company"
  } else if (org_name == "org2") {
     sender_name = "org2 company"
  } else {
    ...
  }

  // after
  const sender_name = event.organization.metadata.sender_name
2

Hi @hayashi-ay,

Thanks for the feature request!

1 Like
3

+1. in our use case, we store UUIDs for customer-specific mappings in the metadata. we manually parse the 10 fields for comma-separated values.

6 Likes
4

We’re doing the same exact thing :rofl:

Please implement this Auth0!

2 Likes
5

We had to resort to storing compressed and archived text data in the metadata but it’s obviously not ideal for the complex gymnastics this required :frowning:

6

Any news on this feature ? I’m not quite sure to understand why there are such hard limits on metadata in an organization (10 is a really low number…) when the number of organization is a lot less than the number of users in any given tenant, and the users can have very extensive metadata…

1 Like
7

@dan.woda any news on this feature request?

1 Like
8

Any updates on this?