Skip to content
English
Do you need help? Customer portal
neowit.io
  • There are no suggestions because the search field is empty.

Manage access

Who can see, build, and run workflows in your organization. For organization admins and IT owners.

The short version

Workflows are an admin-only feature today. Any user with the Admin role sees the Workflows section in the left navigation and can do everything inside it. Users without the Admin role don't see it at all.

Service accounts are also admin-equivalent — they can run workflows and own scheduled triggers. See Service account setup.

There is no separate "workflow editor" or "workflow viewer" role today.

What access means concretely

A user with access can:

  • See the Workflows list and open any workflow.
  • Create, rename, duplicate, and delete workflows.
  • Edit the draft of any workflow (adding/removing nodes, changing settings).
  • Save a new version (every save with DAG changes creates one) or revert to an old one via Version history.
  • Test a workflow with the Run workflow button against fake data you supply.
  • View the execution history of any workflow.
  • Cancel a running execution.
  • Change the organization's workflow policy (see Org policy).

A user without access:

  • Doesn't see the Workflows item in the left nav.
  • Can't reach any /api/workflow/v1/* endpoint — server returns 403 Forbidden.

Promoting a user to admin

If a colleague needs to build workflows, promote them to Admin:

  1. Open Settings → Users.
  2. Find the user and click their name.
  3. Change Role to Admin.
  4. Save.

They'll see Workflows on next refresh. Remember the change is org-wide — admins have full access to everything in Neowit, not just workflows.

[SCREENSHOT] User detail page in Settings → Users, with the Role dropdown showing "Admin" highlighted.

When you don't want to promote someone

If someone needs to run workflows but you can't give them admin over the whole organization, use a service account instead:

  • Service accounts are non-human identities; they have admin privileges scoped to Neowit APIs but no interactive login.
  • You can configure a workflow to run "as" the service account — useful for scheduled triggers where there's no human initiating the run.
  • See Service account setup.

API access

If you're writing scripts that talk to Neowit's workflow API (for example, to export workflow definitions to a backup), the caller must authenticate as an admin user or a service account. Non-admin API callers get 403.

The REST surface lives under /api/workflow/v1/. Contact your Neowit rep if you need the OpenAPI description.

Related