Roles and permissions

Roles in the Bullfrog platform, and the pages and actions each one reaches.

Roles

Admin

Held by owners of the corresponding GitHub organization. A personal account is always an admin of itself.

Full read access plus every write action: creating and deleting API tokens, creating, editing, and deleting egress policies, and viewing the members and installation pages.

Member

Held by anyone who belongs to the GitHub organization without being an owner.

Read access to workflow runs, unauthorized connections, and egress policies. The Settings navigation item is hidden, and any write request is refused.

Demo viewer

Held by anyone who enters through Try Demo without signing in. Pinned to a single demonstration organization.

Read access to workflow runs, unauthorized connections, and egress policies. Every write is refused, and no organization switcher is shown.

Access by page

Page	Admin	Member	Demo viewer
Workflow Runs	Read	Read	Read
Unauthorized Connections	Read	Read	Read
Policies	Read and write	Read	Read
Settings → API Tokens	Read and write	No access	No access
Settings → Members	Read	No access	No access
Settings → GitHub App Installation	Read	No access	No access

Where roles come from

Roles aren't editable in Bullfrog. Each time you sign in with GitHub, Bullfrog reads your role in every organization you belong to and records it: a GitHub organization owner becomes an admin, and every other member becomes a member.

A role change in GitHub therefore takes effect at the user's next sign-in, not immediately.

Membership itself is managed in GitHub. The Members page lists only the people who have signed into Bullfrog at least once, with their name, email, role, and last sign-in.

GitHub App installation

Installing the GitHub App on an organization requires owner access on GitHub.

Which repositories the app can see is set on GitHub, under the installation's settings, not in Bullfrog. The Settings → GitHub App Installation page links to that screen.