> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-users/egnyte/how-to-open-encrypted-files.md).

# How to open encrypted files

## Opening an Encrypted File

FenixPyre encrypts files to ensure their security and prevent unauthorized access. Files encrypted by FenixPyre can only be opened and viewed using the FenixPyre platform. To make the process seamless, an option to open encrypted files is integrated directly into the context menu in SharePoint, OneDrive, and Teams.

> **Note**: Ensure the end-user has a valid FenixPyre account before using the "Open" feature in our OneDrive/SharePoint/Teams integration.

## **Steps to Open an Encrypted File:**

1. **Right-click on the File**: On Egnyte, navigate to the encrypted file. Right-click on the file to open the context menu.
2. **Select "Open"**: Click on "Open Encrypted File." This will trigger FenixPyre to decrypt the file and open it.
3. **File Opens in a New Tab**: The encrypted file will be opened in a new browser tab using the configured document viewer. You can securely view and interact with the file within this protected environment.

{% hint style="info" %}
**Important**:\
Users must be logged into FenixPyre before encrypting or decrypting files. If they are not logged in, they will be redirected to the login page.

FenixPyre supports O365 as file editor.
{% endhint %}

FenixPyre ensures that only authorized users with access to the FenixPyre platform can open and view encrypted files, maintaining strong data protection throughout the process.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fenixpyre.com/fenixpyre-for-users/egnyte/how-to-open-encrypted-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
