[hardwaresofton]

Thanks for answering my questions Ege!

> Actually can’t, Permify doesn’t handle authentication or identity management. As I stated in the first question, you can use them only to feed/map Permify with user information (attributes, identities, etc) to provide end-to-end access control structure across your stack.

Ah OK, so regarding this, you could map your information in to Permify but Permify doesn't (yet?) have anything to reflect that information into another provider.

But Permify could help if you want to make rules that work cross-provider?

[EgeAytin]

Not 100% sure I understand what you meant with "reflection" but to give a quick overview on data management:

Permify stores authorization data as relations in a database you prefer and perform access checks (and other queries as well) according to stored relations/authz data. And since user identities exist/stored in providers, they should be mapped Permify to store necessary authorization data/relations. So providers can feed Permify but not vice versa.

For more information about how we're managing authorization, check our docs: https://docs.permify.co/docs/getting-started/sync-data