---
title: "Review an access request on the Vendor Access Portal"
slug: "domum-review-an-access-request-on-the-vendor-access-portal"
updated: 2026-11-03T14:57:58Z
published: 2026-11-03T14:57:58Z
canonical: "docs.senhasegura.io/domum-review-an-access-request-on-the-vendor-access-portal"
---

> ## 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.

# Review an access request on the Vendor Access Portal

A request from the portal does not reach your approval workflow on its own. You triage it first: you decide which credential the third party will use, when they can use it, and how many sessions they get. Only then does it follow whatever **Access policy** already applies to that vendor.

## Requirements

- The **Domum.Portal.Review** permission. The built-in **Portal Operator** role carries it, and **Domum Administrator** includes it too. To assign a role, see [How to manage user roles](/v4-2/docs/how-to-manager-user-roles).
- A pending request submitted from the portal catalog. To see what the third party submits, see [Request access on the Vendor Access Portal](/v4-2/docs/domum-request-access-on-the-vendor-access-portal).

## Steps

1. On Segura™, in the navigation bar, hover over the **Products menu** and select **Domum Remote Access**.
2. In the side menu, select **Management > Portal settings**.
3. Select the **Access requests** tab.
4. Find the request in the list and select **Review**.
5. Read what the third party asked for: the resource, the vendor organization, the requester, the justification they gave, the duration, and **Requested at**. **Requested at** shows the time in your own time zone, the same value the third party sees.
6. Under **Add**, select the credential the third party will use. You can assign more than one.
7. For each credential, select what it allows: **Start session**, **View password**, or both. The options available depend on the vendor's **Access policy**. You cannot approve the request until every credential you added carries at least one of the two.
8. Adjust **Duration**. The portal refuses a value greater than the resource's **Max duration**, exactly as it does in the third party's request form. The access window starts counting from the moment you release the request, not from when the third party submitted it.
9. Restrict when the credential works, if you need to:
  - Clear **All days**, then set **Access permission days**.
  - Clear **All times**, then set **Access permission times**.
10. Under **Sessions**, clear **Unlimited** to cap how many simultaneous sessions the credential permits.
11. Select **Approve**, or **Reject**.

Attention

An untriaged request expires 6 hours after it is submitted. An expired request is a final state. You cannot approve or reject it afterwards, and it is hidden from reports. The third party has to submit a new one.

## Verify your results

After you release a request on the portal, it follows the **Access policy** configured on the vendor:

- **If the policy needs one or more approvers**: the request enters the policy's approval flow. Once approved, Domum emails the third party.
- **If the policy needs no approvers**: the portal grants access as soon as the request is released.

The portal does not add any approval step beyond those defined in the policy.

With access granted, the third party can open the session. The configured session limit applies to the credential the same way it does for access granted outside the portal.

## Related topics

- [Publish resources to the Vendor Access Portal](/v4-2/docs/domum-publish-resources-to-the-vendor-access-portal)
- [Approve Vendor Access Portal registrations](/v4-2/docs/domum-approve-a-vendor-access-portal-registration)
- [Audit Vendor Access Portal activity](/v4-2/docs/domum-audit-vendor-access-portal-activity)