Overview
Interfaces now let admins define, per data element, who can export information: admins only, admins and members, or anyone with access to the Interface. This means a requester can download their own data straight from the Interface, within the visibility limits the admin has set.
What's new?
- A new export permission control per data element, with three levels: Admins only (the default behavior), Admins and members, and Anyone with access (includes requesters, based on the Interface visibility settings).
- Only the Interface admin can configure any of these settings.
- Configuration happens on each element: open the Interface, edit the data element, turn on Allow record export, and select who can export.
- New data elements come with export enabled and set to Admins only by default. This is already the current behavior today: only Interface admins can export data from their Interfaces.
- Existing elements keep their current state: no changes are applied automatically.
- Exports respect the Interface filters: only visible records and fields are included in the download.
How does this help?
- Requesters download their own data without depending on an admin: anyone with access to the Interface handles the export on their own, without opening a request to the team.
- Admins keep control over who exports each element: the permission is set element by element, inside the access rules the area has already approved.
- Exports come out clean and consistent with what the person sees: the filters applied in the Interface carry over to the file, so the download brings exactly the relevant records and fields.
- Nothing changes on what's already live without the Interface admin's decision: existing elements keep their current setup, preventing accidental data exposure.
Use cases
1. Requester in a Procurement Interface. A requester tracks their requests through a procurement Interface. With Anyone with access enabled on the requests data element, they download their own list of submitted requests straight from the screen, filtered to what they already see, without opening a ticket for the admin to pull the report.
2. Admin of a finance Interface controlling exposure. The admin of a reimbursement Interface keeps most elements on Admins only, but opens Admins and members on the element listing approved reimbursements. The finance team exports that slice for reconciliation, while elements with sensitive data stay restricted.
3. Operations manager consolidating tracking data. In an Interface that centralizes the status of several processes, the manager enables export at the Admins and members level for the tracking elements. The team exports the visible records, with filters already applied, to bring to a status meeting without requesting an extraction from the admin.
4. External vendor with Interface access. A vendor tracking their orders through an Interface downloads only the records and fields the Interface visibility grants them. The admin controls this export at the element level, ensuring the download respects exactly that profile's access scope.
Most relevant for
- Interface admins
- Operations teams
- Finance teams
- Procurement managers
- Requesters with Interface access
Documentation
For the full step-by-step, check the Help Center article.
