> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/access-requests-and-approvals/slack/access-a-resource-from-slack.md).

# Access a resource from Slack

After your access request is approved, you can use **Connect** to launch a session automatically when available, or use **Access Details** to retrieve credentials and access instructions for manual login.

{% hint style="info" %}
If your credentials were rotated since your previous session, Apono displays a **Credentials rotated** tag. When this appears, previously saved credentials or client profiles may no longer work.

Use **Connect** again or retrieve the current credentials from **Access Details**.
{% endhint %}

<details>

<summary><strong>Connect</strong></summary>

Connect opens the available connection options for the resource, so you can log in without manually copying credentials.

{% hint style="warning" %}
To use the **Connect** option, the following requirements must be met:

* Apono CLI [installed](https://docs.apono.io/docs/access-requests-and-approvals/cli/install-and-manage-the-apono-cli.md#install-the-apono-cli), [updated](https://docs.apono.io/docs/access-requests-and-approvals/cli/install-and-manage-the-apono-cli.md#update-the-apono-cli), and [logged in](https://docs.apono.io/docs/access-requests-and-approvals/cli/requesting-access-with-cli.md#log-in-to-apono)
* Credentials not previously viewed

Currently, the **Connect** option is only supported on MacOS / Linux.
{% endhint %}

Follow these steps to access the resource:

1. Either from the message or under **My Sessions** (**Home > My Access > My Sessions**), click **Connect** to see the connection options for the resource.

{% hint style="info" %}
Available connection options depend on the resource and may include **Open in my Terminal**, **Open in Browser**, or **Open in App**.

If your preferred connection option or the Connect button is not available, you can [retrieve your credentials](#access-details) to manually log in to the resource.
{% endhint %}

2. Click an option.
3. Click **Open**. You are logged in to the resource and your session launches.

</details>

<details>

<summary><strong>Access Details</strong></summary>

Access Details lets you view the credentials and instructions needed to access a resource manually.

Use this method when:

* The **Connect** button is not available for the resource or your preferred connection method.
* You need to set up multifactor authentication for the account.
* You prefer to log in using your own client or workflow.

{% hint style="danger" %}
Be sure to copy and securely store your credentials. **Apono only displays the secret once.**
{% endhint %}

Follow these steps to access the resource:

1. Either from the message or under **My Sessions** (**Home > My Access > My Sessions**), click **Access Details** for the resource. A pop-up window appears.
2. Follow the instructions to access the resource.

{% hint style="success" icon="lightbulb" %}
If you previously viewed your credentials, you can click **Reset Credentials**. Resetting your credentials enables you to use the [Connect](#connect) approach.
{% endhint %}

</details>


---

# 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.apono.io/docs/access-requests-and-approvals/slack/access-a-resource-from-slack.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.
