Roles & Permissions
Three workspace roles in FileRelay: Admin, Member, Viewer. What each can do.
Roles & Permissions
Three roles per workspace: Admin, Member, Viewer. Roles are not inherited across workspaces — an Admin in prod has no role in dev until they're invited.
At a glance
| Permission | Admin | Member | Viewer |
|---|---|---|---|
| View dashboard, documents, sources, destinations, connections, team | ✓ | ✓ | ✓ |
| Create / edit / delete sources, destinations, connections | ✓ | ✓ | |
| Retry failed documents | ✓ | ✓ | |
| Manage API keys | ✓ | ✓ | |
| Invite, remove, or re-role team members | ✓ | ||
| Edit workspace settings (retry, relay mode, SAP connection) | ✓ | ||
| Delete the workspace | ✓ |
Admin
Full control over a workspace: configuration, team management, and destructive operations.
Best for team leads, SAP Basis administrators, and project managers responsible for the FileRelay setup.
Member
Day-to-day operator. Can wire and edit sources / destinations / connections, retry failures, manage API keys — but can't change workspace-level settings or invite people.
Best for developers, SAP consultants, and operations staff configuring and monitoring document flows.
Viewer
Read-only access — dashboard, documents, source / destination / connection configs, and team list. Cannot make any changes.
Best for auditors, managers, and stakeholders who need visibility without the ability to modify configuration.
Assigning roles
- During invitation — pick the role in the invite dialog. See Inviting Members.
- After invitation — go to the Team page, open the role dropdown next to the member, pick a new role. Takes effect immediately. (Admin only.)
REPLACE: Screenshot of the role-change dropdown on the Team page
Workspace isolation
Roles do not cross workspaces — by design. A user with Admin in prod is no-role in dev until separately invited. This lets you run different permission models per environment (e.g. tight prod, looser dev).