# Ash Framework: Final album policy (p155)

**URL:** <https://forum.devtalk.com/t/ash-framework-final-album-policy-p155/203274>\
**Category:** PragProg Customers\
**Tags:** book-ash-framework, question\
**Created:** [15 June 2025 15:09 UTC](https://forum.devtalk.com/t/ash-framework-final-album-policy-p155/203274 "2025-06-15T15:09:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sevenseacat](https://forum.devtalk.com/user_avatar/forum.devtalk.com/sevenseacat/32/5897_2.png) [@sevenseacat](https://forum.devtalk.com/u/sevenseacat)\
**Post date:** [19 June 2025 16:21 UTC](https://forum.devtalk.com/t/ash-framework-final-album-policy-p155/203274/2 "2025-06-19T16:21:17Z")

</div>

You can combine simple checks and filter checks as separate checks the same policy, that’s correct.

By “can’t combine built-in checks” I meant in the same policy _check_, something like:

```auto
authorize_if actor_attribute_equals(:role, :editor) && relates_to_actor_via(:created_by)

```

Which doesn’t work!

I’m pretty sure your version with two checks is equivalent, but I find it a lot harder to wrap my head around it, with the separate checks with inverted rules (which is why I can’t say with 100% confidence that they’re equivalent!)

---

_[View the full topic](https://forum.devtalk.com/t/ash-framework-final-album-policy-p155/203274)._