OpenFn / OpenFn/lightning

Public Read-Only Links for Workflows

Open
#4,013 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new feature
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Summary

Let users create a public link to view a workflow, snapshot, or run in read-only mode. Anyone with the link can see how data was processed, without needing to log in or have edit access.

The Problem

Right now, if someone wants to see a workflow, they need to:

  • Be added to the project as a member, or
  • Ask someone to send screenshots

This makes it hard for users to understand how their own data was processed, and reduces transparency.

Proposed Implementation

Add a button to "Create Public Link" for:

  • Workflows
  • Workflow snapshots
  • Specific runs

When someone opens the link, they can:

  • See the workflow diagram (view only)
  • Read the job code and steps (view only)
  • See trigger settings (view only)
  • View run details if it's a run link

What they CAN'T see:

  • Passwords or credentials
  • Secret environment variables
  • Any sensitive information

Users should be able to turn off these links at any time.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the access-control entry points for workflows, workflow snapshots, and runs, along with any existing read-only or sharing tests; the issue names no files. Done means public links can be created and disabled, expose only the specified read-only data without credentials or secrets, and require no login.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
authentication, authorization, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.