> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/lifecycle-management/access-requests-with-balkanid-for-slack.md).

# Access requests with BalkanID for Slack

## Access requests with BalkanID for Slack

{% hint style="info" %}
If **BalkanID for Slack** is not set up for your tenant, please visit [BalkanID for Slack](/getting-started/balkanid-for-slack.md) for more information.
{% endhint %}

Use `/request-access` in Slack to create a classic access request. You can request access for yourself or another person.

You can grant or revoke connections and resources. Requests can be permanent or temporary.

### Create an access request

1. Run `/request-access`.
2. Choose who needs the access change.
3. Choose **Permanent** or **Temporary** access. Enter an end date for temporary access.
4. Under **Access identical to**, choose a baseline:
   * **Access identical to user**
   * **Access identical to role** when enabled for your tenant
   * **Access identical to job title**
   * **Choose custom access**
5. Use **Browse** to select changes in the relevant categories:
   * **Connections to grant** and **Resources to grant**
   * **Connections to revoke** and **Resources to revoke**
6. Select the target identity for each integration affected by a grant. If no identity exists, complete that part in the BalkanID web app.
7. Select a reason. Choose **Other** to enter a custom reason.

   <div data-with-frame="true"><figure><img src="/files/NrimB6QX4DRUjGNG7Hav" alt="" width="563"><figcaption></figcaption></figure></div>
8. Review the **Confirm** screen and select **Submit**.

The Confirm screen summarizes every change. Select **Back** to edit before submission.

Reviewers are assigned automatically. Use **Reassign** on the review afterward to change a reviewer.

### Reasons

Select one of these reasons:

* Need to perform current job duties
* Moving roles within current team
* Moving roles outside of current team
* Other

### Subject consent

Your tenant can require the request subject's consent. The subject is the person receiving the access.

The subject must grant consent before reviewers receive the request. Denying consent closes the request permanently. Consent is skipped for self-requests.

This can apply to classic and purpose access requests.

### What happens next

After submission, you receive a confirmation in the app's **Messages** tab in Slack. Reviewers receive notifications as their approval tier becomes active.

After a classic request is approved or denied, the requester and subject receive a completion notification.


---

# 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://docs.balkan.id/lifecycle-management/access-requests-with-balkanid-for-slack.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.