> ## Documentation Index
> Fetch the complete documentation index at: https://help.kwentra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve kwentra Support Access to Your Data

> kwentra support has no standing access to your live data. They must ask, you approve per property, and access expires on its own.

kwentra support can no longer enter your live data at will. You approve each request, per property, for a limited time.

<video autoPlay muted playsInline controls className="w-full rounded-md" src="https://mintcdn.com/kwentra/Gob2b9_MQv54BSqI/images/compliance-integrations/approve-kwentra-support-access-to-your-data/manage-access-and-support-permissions-walkthrough.mp4?fit=max&auto=format&n=Gob2b9_MQv54BSqI&q=85&s=395f59866922f004db49b5b654b7ee12" data-path="images/compliance-integrations/approve-kwentra-support-access-to-your-data/manage-access-and-support-permissions-walkthrough.mp4" />

### **Business Value**

* Removes standing kwentra access to your live hotel data.
* Requires your consent before any support session starts.
* Limits every approved session to 1–24 hours, then expires it.
* Lets you approve some properties and refuse others in one decision.
* Records every request, decision and session for audit.

### **Use Cases**

* Hotel manager approves a 4-hour support session to check a ledger mismatch.
* Group finance controller grants two of three properties and refuses the third.
* Night auditor ends an active support session early from the on-screen banner.

### **How It Works**

| **Where:** The consent pop-up and the session banner appear wherever you are working in kwentra. There is no separate screen to open. |
| - |

kwentra support staff have no standing access to any live instance. A support agent must raise a request and name you as the approver. Nothing happens until you decide.

#### **What Triggers the Request**

A kwentra support agent starts the request against a real support ticket. It only covers properties **you** belong to, inside one company. You get one consent pop-up, even when several properties are involved.

#### **Review and Decide**

The consent pop-up shows you:

* Who is asking for access, and their reason.
* The support ticket reference.
* The access window they asked for.
* The full data-access disclaimer.
* A checkbox list of every property they asked for.

To decide:

1. **Uncheck any property you do not want to grant.** The agent can only enter the properties left checked.
2. **Tick the disclaimer acknowledgement.** The grant button stays disabled until you do.
3. Choose **Grant selected access**, or **Reject all** to decline the whole request.

| **Note:** Your consent covers the live data of each property you leave checked, and nothing else. Granting one property never exposes the others. |
| - |

#### **What the Agent Can Do During the Session**

During the window, the agent is a temporary member of the properties you granted:

* Your granted properties show in their property selectors.
* Consolidated reports cover only the properties they can access. They are labelled **partial — N of M instances**.
* Import, export and consolidation tools work on the granted properties only.
* Properties you did not grant stay invisible in every picker, report and export.

Their access never changes your own users' permissions. It only adds a temporary membership.

#### **Track and End the Session**

While a session is active, a banner shows the property, the reason and a live countdown.

* Select **End session** on the banner to cut access at once.
* Ending the session ends it for **every** agent on it. That includes any helper added during the session.
* Access also ends on its own when the window expires.

Once a session ends or expires, the agent cannot resume it. More work needs a new request. It carries its own ticket, reason, window and your approval.

| **Note:** A support agent can add a helper to an active session. The helper takes the same properties you granted, for the remaining time only. Your first consent still sets the full scope. |
| - |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.