Say what you're trying to do
In one sentence: “an agent should only see tickets of the products they are granted”.
Ask. Suggest. Help each other.
Stuck on a policy, unsure which role goes where, or think wardn should work differently? Post it. Other developers who use wardn, and its maintainers, answer here, and every answer stays searchable for the next person.
Where to post
Section titled “Where to post”Q&AHow do I…? Why does wardn…? Answers are voted on, and the asker marks the one that worked.
IdeasA feature, an API change, a guide that's missing. Discuss it here before writing code.
GeneralConcerns, feedback, and anything else about wardn.
Show and tellHow your team uses wardn: your policy, your admin screens, what you learned.
A question about one page of the docs? Use the Questions and comments box at the bottom of that page. A bug you can reproduce? Open an issue.
Asking a good question
Section titled “Asking a good question”Show the policy and the code
The roles and scopes involved, trimmed, and the check or change that surprised you.
Expected versus what happened
The error, or the Explain output for a decision you didn’t expect.
Versions
wardn, the store you use, and your database.
Never paste real user IDs, customer data, connection strings or secrets: replace them with made-up values. Reading needs no account; to post, sign in with GitHub.
Ground rules
Section titled “Ground rules”Be kind and assume good intent: everyone was new to authorization once. Keep each discussion to one topic, and search before you post. Disagree with ideas, not people. If an answer solved your problem, mark it as the answer and vote it up. When a question shows the docs are unclear, the maintainers fix the docs too.