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 organization has two kinds of members: Admins and Members.

Organization Admins have full control — they manage settings, add and remove users, assign roles, and create or delete projects. Admins automatically get Editor access to every project in the organization.

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

Keep in mind that every user in an organization — whether they’re a full member or just given access to a single project — consumes a license seat.

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.

Project Visibility

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

• Public — anyone can view the project, even without logging in.
• Repository — GitHub collaborators on the connected repository automatically get Viewer access. You can still grant access to additional users manually.
• Private — only organization members can see the project. Everyone else gets a 404 unless they’ve been explicitly granted access.