Actions or Organisations: user/organisation(s) relationships

We are using auth0 for authorisation and authentication within our app. The current authorisation model knows nothing about conceptual “organisations” and is purely a list of username - role.

In order to support a model where we derive roles based upon a user being attached to the relationship between two “conceptual organisations” (think supplier and consumer / provider and user) the question stands: can this be modelled in Auth0?
“Organisations” don’t feel quite like the right use-case, so I presume maybe ‘actions’? I think the requirement would be to assign the supplier/consumer relationships elsewhere (CRM, internal DB?) and try to associate the link within Auth0 against which the username then has association and roles?

Thanks in confused advanced, Al.

Hey team! :waving_hand:

Since this topic touches Auth0 Actions, quick heads-up that we’re hosting an Ask Me Anything dedicated to Actions with Gaston Danilo Asis Sanchez, Senior Technical Product Manager. We’ll cover practical usage, new capabilities like Transaction Metadata and Actions Types, plus a peek at what’s next. :sparkles:

  • Submit questions now through Aug 26 :writing_hand:
  • Get detailed written answers live on Aug 27, 9–11 AM PT :speech_balloon:

Earn community points + a badge :trophy:. If you’re exploring how Actions can streamline your auth flows, this is a great time to get direct guidance from the team.
Join the AMA & drop your questions here: August 27 Auth0 Community Ask Me Anything: Actions

Dawid