> 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/sub-administrations/manage-permissions-for-sub-administrations.md).

# Manage permissions for Sub-administrations

Use permissions to control who can work with **Sub-administrations**.

Keep management rights limited to the right users.

### Common permission choices

You usually decide who can:

* view the Administrations page
* create a sub-administration
* delete a sub-administration

### Good practice

Give full management access only to administrators or key users.

Give other users only the access they need.

{% stepper %}
{% step %}

### Open Users

Go to **Settings → Users**.
{% endstep %}

{% step %}

### Open the user account

Select the user you want to change.
{% endstep %}

{% step %}

### Update the permissions

Enable the rights that match the user’s role.
{% endstep %}

{% step %}

### Save and test

Save the change.

Then confirm the user sees the right options.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Should every user manage Sub-administrations?</summary>

No.

Usually only administrators or key users need that access.

</details>

<details>

<summary>Can a user see only some administrations?</summary>

Yes.

Access depends on the rights you assign.

</details>

<details>

<summary>Why can a user not open the Administrations page?</summary>

Check whether that user has the right access.

</details>

### Related topics

* [**Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations.md)
* [**Create a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/create-a-sub-administration.md)
* [**Delete a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/delete-a-sub-administration.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/sub-administrations/manage-permissions-for-sub-administrations.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.