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 there!

As this topic is related to Actions and Rules & Hooks are being deprecated soon in favor of Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!

Learn more here!