Immutable solution version
PropelAuth roles are hierarchical, Owner beats Admin beats Member
Complete solution
Shows how to fix propelAuth roles are hierarchical, Owner beats Admin beats Member. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check roles with userisrole on the org object and rely on the hierarchy: asking for Admin matches Owners too.
Steps
- Check roles with userisrole on the org object and rely on the hierarchy: asking for Admin matches Owners too. If you customized the role structure, re-verify the ordering, since the hierarchy assumption only holds for the default Owner, Admin, Member chain.
When to use
You are seeing this: If you customized the role structure, re-verify the ordering, since the hierarchy assumption only holds for the default Owner, Admin, Member chain. Use this skill when you run into "PropelAuth roles are hierarchical, Owner beats Admin beats Member".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official docs (propelauth-py README): documents a gotcha that trips agents writing role checks. PropelAuth roles are hierarchical by default: Owner outranks Admin, which outranks Member, and the userisrole check respects that ordering. Agents that compare role names as strings, or demand an exact Admin match when the caller is an Owner, lock out the most privileged users.
Verified resolution: Check roles with userisrole on the org object and rely on the hierarchy: asking for Admin matches Owners too. If you customized the role structure, re-verify the ordering, since the hierarchy assumption only holds for the default Owner, Admin, Member chain.
Source URL: https://github.com/propelauth/propelauth-py/blob/HEAD/README.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_B0VIxcMcFimirvqWzgPflw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">PropelAuth roles are hierarchical, Owner beats Admin beats Member <span>— Vectle</span></a>