I can only confirm part of what you're describing based on what's documented. For audit logs specifically, there are two distinct endpoints: the

elements_list_audit_logs

endpoint lists audit logs for a specific elements config, scoped to tenant(1), while

get_detailed_audit_log

retrieves a detailed audit log by its specific log ID(2). These serve different purposes — one is a scoped list view tied to an Elements config, the other is a direct detailed lookup by ID — but I don't have documentation explicitly confirming they return "the same data" as each other or explaining the architectural reasoning behind having both. For your other points (users, user_invites, and roles), I don't have information in the available sources that documents those specific Facts/Schema endpoints or confirms whether their data overlaps with Elements data endpoints. I can't verify or deny those specific claims without that documentation. If you want, I can give a general answer based on my broader understanding of Permit.io's architecture rather than strictly cited documentation — just let me know. If this relates to something not behaving as expected with your PDP or policy checks, it'd help to know: 1. Which Workspace / Project / Env you're using 2. The exact calls you're making (SDK code or CURL) 3. Your PDP version 4. Any relevant PDP logs

To learn more, see the sources I considered: [[1] GET /v2/elements/{proj_id}/{env_id}/config/{elements_config_id}/data/audit_logs](https://api.permit.io/v2/redoc#tag/Audit-Elements-Data/operation/elements_list_audit_logs) [[2] GET /v2/pdps/{proj_id}/{env_id}/audit_logs/{log_id}](https://api.permit.io/v2/redoc#tag/Audit-Logs/operation/get_detailed_audit_log)

I don't have documentation in the available sources that covers

ViewerContextType.user

, the

permit_session

cookie,

permit.elements.loginAs()

, or how to authenticate a request as a

ViewerContextType.user

versus an API key. None of the provided sources address this specific error or the Elements viewer-context authentication flow, so I can't confirm or provide a fix from what's cited here. Since this sounds like a specific request failing against your PDP/environment, it would help to know: 1. Which Workspace / Project / Env you're using 2. The exact calls you're making (SDK code or CURL) 3. Your PDP version 4. Any relevant PDP logs If you'd like, I can give a general answer based on broader understanding rather than cited documentation — just let me know. Otherwise, reaching out at help@permit.io would get you a direct answer on the viewer-context/session flow.

Feel free to tag me with additional questions. I also appreciate feedback, it helps me improve. 👍 button 👎 button

This is the curl command

It sounds like you're trying to hack something together, and not use the product as described. I suggest you avoid doing that, and instead tell us what you're trying to do and we can tell you if /how to go about it