# User Privileges

When installing and managing ONEWEB platform components, it is important to define **which system user account** is used to perform the installation and management tasks.

ONEWEB can be installed using either:

* an **administrator user (root)**, or
* a **non‑administrator user (non‑root)**

Once a user account is selected, the **same user must be used consistently** to install ONEWEB and all required supporting software components.

***

#### Consistent Installation User

To avoid permission and execution issues:

* ONEWEB
* Java
* Application Server (for example, IBM WebSphere Application Server)

**must be installed using the same operating system user account**.

Using different users for different components may lead to file access or runtime permission problems.

***

#### Administrator User (Root)

If ONEWEB is installed using an **administrator user (root)**:

* Ensure that installation files and directories have sufficient execution permissions
* The administrator user must be allowed to execute and manage all required platform components

This approach provides full system access but should be governed by organizational security policies.

***

#### Non‑Administrator User (Non‑Root)

If ONEWEB is installed using a **non‑administrator user**:

* Ensure that the user has **full privileges** on the installation directories
* The user must have permission to read, write, and execute files related to ONEWEB and its dependencies

For environments where multiple users are involved:

* A **user group** can be used to manage access
* All users in the group must have appropriate directory permissions
* ONEWEB may be installed using one account, while other offerings are installed using another account within the same group

This approach supports controlled access while maintaining operational flexibility.

{% hint style="info" %}
**Note:** Group‑based permission mode is **not supported on Windows** operating systems.
{% endhint %}

***

#### Best Practice Summary

* Choose either **root** or **non‑root** installation early and remain consistent
* Use the **same user account** for ONEWEB and all related software installations
* Ensure directory permissions align with the selected user or group
* Align user privilege decisions with organizational security policies

Proper user privilege planning helps prevent installation errors and simplifies long‑term platform management.


---

# Agent Instructions: 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:

```
GET https://docs.onewebstack.com/getting-started/platform-configuration/platform-components-overview-and-management/user-privileges.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.