> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/customer-portal/access-control.md).

# Access Control

There are three default access levels that can be granted to your customers' users.

### No Access

End users with no access will not be able to login to the portal. You or customer admins can revoke access for a user at any time.

### Member

Members are able to see and manage just tickets they have submitted in the portal - not tickets submitted by their coworkers. 

Members also cannot change the roles of their teammates and cannot invite additional teammates into the portal.

### Admin

Admins can see and manage tickets submitted across their organization.

Admins can also change the role of their teammates and invite additional users into the customer portal.

<figure><img src="/files/jZUu0gxFVDC8sbs3tGq8" alt=""><figcaption></figcaption></figure>

## Custom Contact Roles

Custom Contact Roles allow you to define granular permissions for different types of portal users. Each contact can be assigned a role that determines their level of access to issues, other contacts, and tasks within the portal.

<figure><img src="/files/pCEVxy6n2BubAc99xKwj" alt=""><figcaption></figcaption></figure>

Navigate to the [**Contacts**](https://app.usepylon.com/settings/contacts) section and select **Manage Portal Roles** to view and configure both default and custom roles for your portal.

#### Permissions <a href="#permissions" id="permissions"></a>

Each role has four main permission areas:

* **Issues** - Control access to support issues
* **Contacts** - Manage visibility of other portal users
* **Tasks** - Define task viewing and interaction permissions
* **Feature Requests -** View shared feature requests

#### Access <a href="#access" id="access"></a>

Each permission area supports different access levels:

* **Editor** - Full read and write access
* **View Only** - Read access without editing capabilities
* **No Access** - No visibility or interaction


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.usepylon.com/pylon-docs/customer-portal/access-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.