> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/customer-portal/configure-user-settings-and-permissions.md).

# Configure user settings and permissions

The **User settings** section controls what portal users are allowed to do.

Use it to keep the portal aligned with your customer process.

{% stepper %}
{% step %}

### Open the portal

Open the portal you want to edit.
{% endstep %}

{% step %}

### Open User settings

Select **User settings** in the left menu.
{% endstep %}

{% step %}

### Review the allowed actions

Choose which actions portal users can perform.
{% endstep %}

{% step %}

### Limit fields and request behavior

Restrict changes where customers should only view data.
{% endstep %}

{% step %}

### Save the settings

Click **Save**.
{% endstep %}
{% endstepper %}

### Typical restrictions

* limit which work types can be requested
* block customer or contact changes
* keep request creation more controlled

### Frequently asked questions

<details>

<summary>Do these settings apply per user?</summary>

No.

They apply per portal.

</details>

<details>

<summary>Can I create a separate portal for another permission model?</summary>

Yes.

That is the usual approach.

</details>

<details>

<summary>Can I limit which work types users can request?</summary>

Yes.

That depends on your portal setup.

</details>

### Related topics

* [**Customer Portal**](/marketplace-packages-and-power-ups/power-ups/customer-portal.md)
* [**Manage portal users**](/marketplace-packages-and-power-ups/power-ups/customer-portal/manage-portal-users.md)
* [**Configure items per work type**](/marketplace-packages-and-power-ups/power-ups/customer-portal/configure-items-per-work-type.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/customer-portal/configure-user-settings-and-permissions.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.