# Parse Unix file permissions

## Description

This operation is used to interpret and analyze standard Unix file permission strings (e.g., `-rwxr-xr--`) and provide a detailed breakdown of the permissions, including their binary and octal representations. You can also enter the code formats to get the Unix file permission strings.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](https://965373739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkxZeV4nlXcIAjMGZxzLI%2Fuploads%2FEAiKqmMTtuQqEcB1ARyA%2Fimage.png?alt=media\&token=4af58dc3-64ff-4780-aaff-8e73704304ac) - Unix-style file permission strings or codes you want to analyze.

### Output data

![](https://965373739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkxZeV4nlXcIAjMGZxzLI%2Fuploads%2FwTb2oTb0LEAHXBbhwEP9%2Fimage.png?alt=media\&token=9b224990-9f87-48b5-8995-5e7e62e71a79) - Details of the provided Unix file permission strings/codes.

***

## Example

Suppose you want to analyze a series of Unix file permission strings in your input data:

1. In your Pipeline, open the required [Action](https://onum.gitbook.io/onum-docs/the-workspace/pipelines/actions) configuration and select the input **Field**.
2. In the **Operation** field, choose **Parse Unix file permissions**.
3. Give your **Output field** a name and click **Save**. The values in your input field will be decoded. 

For example, for the following  Unix file permission string:

```
-rwxr-xr--
```

you'll get the following breakdown:

{% code overflow="wrap" %}

```
Textual representation: -rwxr-xr-- Octal representation: 0754 +---------+-------+-------+-------+ | | User | Group | Other | +---------+-------+-------+-------+ | Read | X | X | X | +---------+-------+-------+-------+ | Write | X | | | +---------+-------+-------+-------+ | Execute | X | X | | +---------+-------+-------+-------+
```

{% endcode %}

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# 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.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/file-system-permissions/parse-unix-file-permissions.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.