--- title: "Request access through Self-service" slug: "self-service-how-to-request-access" updated: 2026-11-06T17:37:17Z published: 2026-11-06T17:37:17Z canonical: "docs.senhasegura.io/self-service-how-to-request-access" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt > Use this file to discover all available pages before exploring further. # Request access through Self-service Request a role, access to an access policy, or a credential from the Self-service panel. Each request needs a justification, and most go to an approver before Segura™ grants the access. ## Requirements An administrator must enable Self-service and turn on the request type you need. More information in [Configure Self-service](/v4-2/docs/self-service-how-to-configure). ## Open the Self-service panel 1. In Segura™, go to **Desktop**. 2. In the side menu, select **Access Self-service > Panel**. You can also open the panel from the user menu, by selecting **Access Self-service**. The panel shows one card for each request type you can open. It also lists your last 5 requests in **My requests**. ## Create a request Every request follows the same steps. Only the first tab changes with the request type. 1. On the panel, select the card of the request type. 2. On the first tab, select what you are requesting. See the request type sections that follow. 3. Click **Continue**. 4. On the **Justification** tab, describe why you need the access, in up to 1024 characters. 5. Click **Continue**. 6. On the **Review** tab, check the request and click **SAVE**. To change something, click **Back**. For an access policy request, Segura may show "There are no approvers available for this request." This means no one can decide the request, so Segura does not save it. You cannot approve your own request, so this also happens when you are the only approver. Ask your administrator to add an approver. Info If you already have a pending request for the same item, the new request replaces it. ### Role request 1. On the **Roles** tab, click **Add**. 2. In the **Roles** modal, select one or more roles and click **Add**. The list shows only the roles an administrator made available for request. Global approvers decide the request. ### Access policy request Each product has its own card: **PAM Core access policy request**, **Cloud IAM access policy request**, **DevOps Secret Manager access policy request**, **Task Manager access policy request**, and **Certificate Manager access policy request**. Select the card for the product of the access policy. On the **Access policies** tab, select the access policy you want to join. The **Module** column shows the product of each access policy. The list shows only the access policies an administrator released for request. After approval, you become a member of that access policy. - **PAM Core** in the static access policy model: the administrators of the access policy decide the request. - Every other case: global approvers decide the request. ### Access policy administration request On the **Access policies** tab, select the access policy you want to administer. The list shows only PAM Core access policies you are already a member of. The administrators of the access policy decide the request. To manage the access policy afterwards, you also need a role that allows managing access policies. ### Handover of access policy administration 1. On the **Access policies** tab, select the access policy you administer. 2. In the **Administrator** column, select the user who will receive the administration rights. The list shows only access policies you administer. The selected user receives an email and decides the request. After approval, the selected user replaces you as an administrator of the access policy. Info Access policy administration requests and handovers are available only when your instance uses the static access policy model. ### Credential request 1. On the **Credentials** tab, fill in the fields: 1. **Domain**: the domain of the new credential. 2. **Credential profile**: the profile that applies to the credential. 3. **Username**: the username of the credential. 4. **Password**: click **Generate** to create the password. This request is approved automatically. Segura creates the credential in the vault as soon as you save the request. If the **Domain** list is empty, ask your administrator to register a domain with a domain controller device. ### AD Account Provisioning On the **Request provisioning in AD** form, select an **Identification** from the list. This request is approved automatically. Segura creates the Active Directory account with a name based on the identification and your username. The request shows **Pending** while Segura creates the account, then **Executed** or **Error**. If the request shows **Error**, on the panel, in **My requests**, open **Actions** and select **Restart execution**. ## Track or cancel a request 1. On the panel, in **My requests**, click **View** to open the full list. 2. Find the request and check its **Status**. 3. To see the approvers and their responses, open **Actions** and select **Details**. 4. To cancel a pending request, open **Actions** and select **Cancel**. You can cancel a request only while it is pending. **AD Account Provisioning** requests cannot be cancelled. More information about each status in [Self-service panel and request screens](/v4-2/docs/self-service-panel-and-requests). ## Related topics - [Self-service requests](/v4-2/docs/self-service-about) - [Self-service panel and request screens](/v4-2/docs/self-service-panel-and-requests) - [Approve or reject a Self-service request](/v4-2/docs/self-service-how-to-approve-or-reject-a-request)