Access Control

Flakiness.io uses GitHub for authentication — every user signs in with their GitHub account. From there, access is managed through organizations and projects.

Organizations and Members

An organization is a group of people who share test analytics data. Each member of an organization is either an Admin or a Member, and one Admin is also the organization Owner.

Organization Admins have full control: they manage settings, add and remove users, assign roles, create or delete projects, and manage billing (the plan, billing status, and Stripe customer portal). Admins automatically get Editor access to every project in the organization.

The organization Owner is the Admin who owns the organization. On top of all Admin permissions, the Owner can transfer ownership to another user and delete the organization. There is exactly one Owner per organization.

Organization Members get Viewer access to all projects by default. They can browse test results and analytics. They can’t manage billing or change organization settings, and they can’t change project settings or upload data unless given a higher project role.

Project Roles

Within a project, there are two roles: Editor and Viewer.

Editors can do everything — change project settings, manage who has access, upload and delete test results, and work with project tokens. Viewers have read-only access to test results, history, and statistics.

Organization Admins are automatically Editors on all projects. Organization Members start as Viewers but can be promoted to Editor on specific projects.

GitHub Repository Access

When a project is connected to a GitHub repository, anyone with access to that repository automatically gets Viewer access to the project, without needing organization membership or an explicit project role. For private projects, Flakiness verifies repository collaboration against GitHub when a logged-in user opens the project.

Viewer access is read-only. A repository collaborator who needs to upload data or change project settings still has to be granted an explicit Editor role.

Project Visibility

Every project has a visibility setting that controls who can see it:

• Private — organization members and project collaborators have access.
• Public — anyone can view the project, even without logging in.