> 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/jitpbac/purposes.md).

# Purposes

Understand the creation, assignment, and management of Purposes for secure access control.

### **Overview of Purposes**

In JITPBAC (Just-in-Time Purpose-Based Access Control), a Purpose is a core construct used to define and manage access permissions for identities within Cloud and SaaS applications. A Purpose acts as a structured grouping of access rights, aligning them with specific tasks, responsibilities, or roles within an organization.

### Purpose Lifecycle

1. **Creation:** A Purpose is created by defining the connections, resources required for access by an administrator.
2. **Assignment:** Identity owners request access to a Purpose and provide details such as the reason, expected usage period, and any extensions needed. Access requests are reviewed and approved by first-line manager, app-owners or risk-managers.
3. **Provisioning:** Once assigned, access is automatically provisioned at the start of the defined time window. The user can also choose to manually start and stop the purpose as per their convenience.
4. **Usage: I**dentity owners can access resources as specified by the Purpose during the active period.
5. **De-provisioning:** Access is revoked automatically when the time window ends, ensuring no lingering permissions. Notifications alert identity owners of impending de-provisioning, allowing them to request extensions if permitted.
6. **Revocation and Updates:** Administrators can revoke access or update Purpose parameters at any time to address security risks or changing requirements.

**Relevant Links:**

* [Create purpose](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/create-purpose.md)
* [Edit purpose](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/edit-purpose.md)
* [Delete purpose](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/delete-purpose.md)
* [Filtering purposes](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/filtering-purposes.md)
* [Create user-purpose access request](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/create-user-purpose-access-request.md)
* [Starting & stopping assigned purposes](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/starting-and-stopping-assigned-purposes.md)


---

# 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.balkan.id/lifecycle-management/jitpbac/purposes.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.
