Roles and Permissions

Access in FluidGrids is role-based and enforced at the API gateway on every request. Roles are assigned per workspace under Permissions in the Workspace Modules group. FluidGrids ships six product roles; workspace owners and admins have everything by default. The full resource-by-role table is in Permissions and Access Control.

The six FluidGrids roles

Role	What it is for	Default home
FluidGrids Automation Owner	Full control of FluidGrids in the workspace, including the connector registry, execution usage, and automation settings.	Dashboard
FluidGrids Automation Lead	Approves, activates, and retires workflow versions, arms triggers and schedules, and governs day-to-day automation change.	Dashboard
FluidGrids Workflow Designer	Builds workflows on the canvas, configures nodes and triggers, and test-runs drafts, without deleting published automations.	My Workflows
FluidGrids Integration Engineer	Curates the connector catalog, registers custom node endpoints and operations, and works the submitted node-package queue.	Credentials
FluidGrids Run Operator	Triages failed runs, retries nodes and webhook deliveries, cancels runaway executions, and pauses schedules.	Runs
FluidGrids Automation Auditor	Reviews workflow designs, trigger configuration, and execution history as read-only evidence, changing nothing.	History

A user with several roles gets the most privileged view.

What each role sees

The sidebar is filtered in two layers:

1. Permission filtering hides items the role cannot use at all. My Workflows needs workflow:read; Runs and History need workflow-run:read. There is no toggle for these.
2. Persona defaults decide which of the remaining items are prominent. Everything else is folded behind N more…. The selector at the bottom of the sidebar (Everything) switches views and the customize icon beside it pins items.

Role	Prominent by default
Automation Owner	All six FluidGrids items (My Workflows, Runs, History, Credentials, Templates, Runners) plus Collaboration, Groups, Tags, Auth, Files, Permissions, Security, Connected Systems, Feature Previews, Administration, Billing, Communication
Automation Lead	All six FluidGrids items plus Collaboration, Tags, Connected Systems, Communication
Workflow Designer	All FluidGrids items except Runners, plus Connected Systems
Integration Engineer	Credentials, My Workflows, Runs, Connected Systems
Run Operator	Runs, History
Automation Auditor	My Workflows, History

Search, Security Settings, Notifications, and Support are visible to every role.

Getting started by role

Automation Owner

1. Invite the team under Administration › Invite People and give each person the narrowest role that fits (see Permissions and Access Control).
2. Check Billing › Plans and Billing › Usage and Quota so the workspace's limits match the automations you plan to run (Plans and Quotas).
3. Set the workspace's execution defaults on the workflow module's Settings screen.

Automation Lead

1. Review new versions in the builder's Versions panel and Activate the ones that are ready. Only the Active version answers webhooks, schedules, forms and error triggers (Workflows).
2. Watch Runs and History for the workflows you govern (Runs, History).
3. Deactivate or archive versions that should stop running.

Workflow Designer

1. Start in My Workflows, your home screen, and create a workflow or import one from Templates (My Workflows, Templates).
2. Build it on the canvas and test-run the draft (Visual Builder).
3. When it is ready, click Activate so its automatic triggers run it. Your role can build, test and activate workflows, but cannot delete them.

Integration Engineer

1. Start in Credentials, your home screen, to review the connections that workflows use (Credentials).
2. Install and update store nodes, and register custom node endpoints (Custom Nodes).
3. Check Runs for failures caused by an expired or wrong credential.

Run Operator

1. Start in Runs, your home screen, and filter for failed runs (Runs).
2. Retry failed nodes and webhook deliveries, and cancel runs that are stuck or runaway.
3. Pause a workflow's schedules while an incident is open, and resume them afterwards.

Automation Auditor

1. Start in History, your home screen, to see each workflow's versions and when they changed (History).
2. Open My Workflows to inspect designs and trigger configuration. Everything is read-only for your role.
3. Use Runs to review execution evidence for a period.

Permission messages you may see

Message	Meaning
You don't have permission to create workflows (tooltip on Create Workflow)	Your role lacks workflow:create. Ask an Automation Owner or workspace admin.
You don't have permission to save workflows	Your role lacks workflow:update.
You don't have permission to install nodes	Installing store nodes is reserved for roles with node-registry rights (Owner, Integration Engineer).
You don't have permission to do that. (toast)	A request on the page was denied by the gateway. If it appears on a screen you can otherwise use, one widget on that screen needs a permission your role lacks; the rest of the screen still works.
Access Denied on Integrations Settings	Integrations settings are admin-only.

Assigning roles

1. Open Permissions in the sidebar.
2. Pick the member and add one or more of the FluidGrids roles.
3. Changes apply on the member's next request; they may need to reload the app.

Workspace membership itself is managed under Administration (Invite People, Workspaces) and Groups.

Next steps

• Permissions and Access Control
• Navigating the App
• Security