> For the complete documentation index, see [llms.txt](https://buildersupport.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://buildersupport.gitbook.io/hub/access-levels.md).

# Access Levels

**Within your Circles, you can manage multiple access levels for all created content.** This allows you to set **Parent-level access** controlling overall Circle permissions, as well as specific access rights for individual groups and pages.

### Parent Access Level <a href="#parent-access-level" id="parent-access-level"></a>

As mention you have control over where you want to change access levels, both at parent and page level. Firstly, let's cover the Parent Access Level.

To edit/change Parent level access, enter the [circle](/hub/circles/circle-settings.md#accessing-your-circle) you want to modify.

Once in your Circle, select the cog icon located at the top:

<figure><img src="https://docs.hublo.so/~gitbook/image?url=https%3A%2F%2F4195526938-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fe72ThyzkOdxFPyh3rXde%252Fuploads%252Fmz5djTd2iGsFx3UrxH3q%252Fparent%2520level%2520access.png%3Falt%3Dmedia%26token%3D48bf7df7-bbed-476e-a329-e2e79c305cbf&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=bf16ce85&#x26;sv=2" alt=""><figcaption></figcaption></figure>

Once Selected a new box will display, scroll down until you find the label 'Access Level' The current access levels are:

* **Open**: Everyone will have public access to this content and will be indexed by search engines like Google
* **Logged in members**: Only logged in members would have access to this content
* **Members of a Group**: Only members of a specific group will have access to this content
* **Payment Required**: Visitors would be required to make a purchase to access the content

{% hint style="success" %}
**Note**: Access levels can be changed within individual pages and groups when required.
{% endhint %}

### Payment Required <a href="#payment-required" id="payment-required"></a>

**The "Payment Required" access level allows you to require payment before granting members access to the entire Circle or specific pages/groups.** To create a paywall for restricted content, select the **Payment Required** option, set your price, and configure your preferred payment structure. If you'd like to offer recurring subscription payments, you can enable that option here as well.

<figure><img src="https://docs.hublo.so/~gitbook/image?url=https%3A%2F%2F4195526938-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fe72ThyzkOdxFPyh3rXde%252Fuploads%252FE3gcQider6CDT9NKrTIq%252Fcircle%2520paywall.png%3Falt%3Dmedia%26token%3D2dcab513-809f-47cb-a996-51048892b316&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=5c41645f&#x26;sv=2" alt=""><figcaption><p>Creating a recurring subscription for a circle community</p></figcaption></figure>

With the paywall now created at Parent level, ie - Main access to the Circle. When a non paying member attempts to access the Circle they will be presented with a payment screen as shown below.

{% hint style="success" %}
**Note:** You can also create products through the eCommerce store and enable payment via a website page, the store itself, or within your funnels. Alternatively, you can set up a dedicated page within your Circle as a paywall using standard checkout functions. This approach allows you to offer upsells and bump offers if needed.
{% endhint %}

<figure><img src="https://docs.hublo.so/~gitbook/image?url=https%3A%2F%2F4195526938-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fe72ThyzkOdxFPyh3rXde%252Fuploads%252Fqc76vsAStkgBF12HYGZC%252Fcommunity%2520paywall%2520screen.png%3Falt%3Dmedia%26token%3Dcd00c443-4568-43a8-8ef9-70941cd5329c&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=bf826f2d&#x26;sv=2" alt=""><figcaption></figcaption></figure>

### Page Level Access <a href="#page-level-access" id="page-level-access"></a>

**Page-level access functions similarly to Parent-level access, as explained above.** The main difference is the additional **"Inherit from Parent"** option available at the page/group level. When enabled, this setting automatically applies the Parent-level access permissions to the selected page or group, ensuring consistency with the access rules you’ve previously configured.

Where to find page/group level settings:

{% content-ref url="/pages/AxdYloDKXSdTBfw6a8iM" %}
[Editing Your Circle](/hub/circles/editing-your-circle.md)
{% endcontent-ref %}