This article is auto-synced from its in-app version in Tai.
Company admins only. This page is part of Settings, visible to users with the Company Admin role.
The Data access by Nezasa page names the Nezasa users who may reach your company's data.
When you'd use this
Nezasa staff who administer your company can manage its configuration — agents, connectors, schedules, users — but they cannot run agents or read what agents produce. Use this page when you want a specific Nezasa person to go further: to reproduce a problem you've reported, or to set something up that needs a real run. For example: you report that a scheduled report comes back empty, and the engineer helping you needs to run the agent against your data to see why.
Steps
In the Workbench sidebar, click Settings.
Under AI & Data, click Data access by Nezasa.
Click Add Nezasa user.
Type at least two characters of the person's name or email, then pick them from the list.
Tick the acknowledgement to confirm you understand what the access covers.
Click Grant access.
To take it away again, click Revoke on their row and confirm.
Granting and revoking are emailed to every company admin and to the person named, and both land in your audit log. So does every visit by Nezasa staff, whether or not they hold a data-access grant — see Using audit logs.
Tips and limits
Only you can grant it. A Nezasa user administering your company cannot add themselves or a colleague to this list, even though they can manage everything else in Settings. The grant is yours to give and yours to take back.
It covers running agents and reading results. A listed user may run agents in your company and read what they produce — including data from TripBuilder and any other connected data source. It is one switch, not a set of separate permissions.
Revoking takes effect within about a minute, across every session that person has open.
Nobody finds out later. Granting and revoking emails every company admin in your workspace and the Nezasa user concerned, and both are recorded in your audit log.
Only Nezasa administrators can be listed. The search covers active Nezasa staff accounts that can administer companies — the only people a grant changes anything for. A colleague of yours who happens to have a Nezasa address on your own workspace is an ordinary user of your company and already has their role's access.
TripBuilder access is still their own. Agents that read from TripBuilder run against your tour operator, and the person also needs their own TripBuilder access to it. TAI mirrors exactly what they hold there — if it's too narrow, those agents come back empty-handed rather than showing them your data.
Delivery settings stay yours. A listed user still cannot change which recipients your scheduled reports may be emailed to — see Report delivery.
Related