Permissions
The Export Operation is gated by team permissions on the source datastore, not by workspace role. The matrix below shows what each team permission can do.
Required team permissions
| Action | Required team permission on the source datastore |
|---|---|
| View an Export Operation's status | Reporter or higher |
| View a scheduled Export | Reporter or higher |
| Trigger an Export Operation | Editor |
| Create / update / delete a schedule | Editor |
| Re-run a completed Export Operation | Editor |
Reveal masked values (include_masked = true / Reveal Masked Values toggle) |
Editor |
The full team-permission ladder is Reporter → Viewer → Drafter → Author → Editor. Each level inherits the abilities of the levels below it.
Admin bypass
Users with the Admin workspace role bypass team-permission checks across the workspace and can run Export Operations on any datastore.
Where the button is hidden vs visible
The Export action in the container menu is hidden for users below the Editor permission threshold. It does not appear as a disabled control. A user who lacks Editor permission on a datastore will not see the export entry point at all.
Cross-references
- For the full workspace role model (Member / Manager / Admin), see User Roles.
- For the team-permission ladder, see Team Permissions.