Can I override cumulative level access?

[raamdev]

---

KB Article Creation Checklist

• [ ] Write initial draft for this KB Article; label this issue draft and either questions or tutorials
• [ ] Add required YAML configuration
• [ ] Add Tags for this KB Article to the YAML config (see YAML Keys (Explained))
• [ ] Edit and finalize draft for publishing (remove draft label, add draft-finalized label)
• [ ] Assign Issue to yourself and create Markdown file (remove draft-finalized label, add pending)
• [ ] Project Lead: Review and Publish KB Article (remove pending label, add published label)

  Additional TODOs

Additional TODO list items go here.

title: Can I override cumulative Level access?
categories: questions
tags: 
author: raamdev
github-issue: 

---

Yes, you can do this with Custom Capabilities. While all s2Member Level access is cumulative (higher levels have access to everything granted to lower levels) you can override this behavior using Custom Capabilities.

For example, create a Custom Capability called level1 and give all your Level 1 members that Custom Capability. Then restrict all Level 1 content to both the Level 1 Membership Access and the level1 Custom Capability.

Now, if a Level 2 member comes along and does not have the level1 Custom Capability, they will not be able to access any content that requires the level1 Custom Capability. In this way, we can prevent Level 2 members from gaining access to content meant for Level 1 members.

[jaswrks]

This looks great like it is. However, before you publish here are some suggestions.

• Add a couple of links that give readers some way to learn more about Custom Capabilities and the [s2If /] shortcode that is generally used to test for CCAPs.
• Add some tags in the YAML.