<p>When you mention new user group, is that a new group of admins/back end users or just people browsing on the front end?</p>

<p>If it's on the front end, just checking the logged in user's group in twig against a new restricted entry type could give you want you want.</p>

<pre><code>{% if entry.type == "restrictedEntryType" and currentUser and currentUser.isInGroup('newUserGroup') %}

   {# let them through #}
   {% include "whatever/restricted_content.html" %}

{% else %}
   &lt;p&gt;Thou shall not pass! You need to log in to see this content.&lt;/p&gt;
{%endif%}
</code></pre>

<p>If it's the back end, like you said, you'd have to do a serious refactor to manage it properly. Put all the restricted content in one structure and only give access to admins/users you want to have edit the content.  You may end up doing that anyway just to keep everything sane, depending on how siphoned off your content is.</p>

<p>To move a structure from one section to another, check out <a href="https://craftcms.stackexchange.com/a/4467/1016">Brandon Kelly's canonical answer</a>.</p>

CC BY-SA 3.0
2015-09-08T07:20:00.383Z
Sorry, backend. Having a single structure is a great solution for the client at present as they can control the complete content architecture of the site and navigation is dynamic. Moving to individual structures places some limitations on that, so I was hoping to avoid it.
Russ Back
CC BY-SA 3.0
2015-09-08T00:23:56.113Z
2015-09-08T00:23:56.113Z
2017-04-13T12:50:59.930Z
RitterKnight
<p>I have a structure section that is driving the majority of a site, which works great with multiple entry types letting us handle different needs across different areas of the site.</p>

<p>The client now wants a new user group that can only access pages in one particular area of the site. as user group access is tied to sections without granular control of entry types within each section, that means we need a wholesale refactor of the way the site is built and managed, which is going to be a real headache at this point.</p>

<p>Does anybody have any approaches for this?</p>

<users><sections><entry-type><permissions>
Can Section access be restricted at Entry Type level?
# Can Section access be restricted at Entry Type level?

(Asked by: username_0 on 2015-09-07)

I have a structure section that is driving the majority of a site, which works great with multiple entry types letting us handle different needs across different areas of the site.

The client now wants a new user group that can only access pages in one particular area of the site. as user group access is tied to sections without granular control of entry types within each section, that means we need a wholesale refactor of the way the site is built and managed, which is going to be a real headache at this point.

Does anybody have any approaches for this?

**Tags:** users, sections, entry-type, permissions

---

## 1 answers

### Answer by username_1 on 2015-09-08. Score: 2

When you mention new user group, is that a new group of admins/back end users or just people browsing on the front end?
If it's on the front end, just checking the logged in user's group in twig against a new restricted entry type could give you want you want.
{% if entry.type == "restrictedEntryType" and currentUser and currentUser.isInGroup('newUserGroup') %}

   {# let them through #}
   {% include "whatever/restricted_content.html" %}

{% else %}
   Thou shall not pass! You need to log in to see this content.
{%endif%}

If it's the back end, like you said, you'd have to do a serious refactor to manage it properly. Put all the restricted content in one structure and only give access to admins/users you want to have edit the content.  You may end up doing that anyway just to keep everything sane, depending on how siphoned off your content is.
To move a structure from one section to another, check out Brandon Kelly's canonical answer.

> **Comments:**
> **username_0**: Sorry, backend. Having a single structure is a great solution for the client at present as they can control the complete content architecture of the site and navigation is dynamic. Moving to individual structures places some limitations on that, so I was hoping to avoid it.  

---

