Understand your organization's context
How to connect an SCM account so Tessl scans your repositories and shows your Organization's Context and Findings.
Connect an SCM account and Tessl scans your repositories, indexes the skills and configuration it finds as Context, and surfaces Findings you can act on. This is the primary way to see what exists across your Organization.
SCM connections are managed at the Organization level. Connecting one needs the Organization admin role. Organization members and admins can view Context and Findings. See Roles for the full breakdown.
Connect an SCM account
Tessl supports these source-control providers:
GitHub (GitHub App)
GitLab (access token)
Bitbucket
To connect:
Open the Tessl web app.
Select your Organization from the dropdown at the top of the sidebar, then go to Settings, then Integrations.
Under Source control, select Add next to your provider and follow the prompts to authorize Tessl.
Connecting authorizes Tessl to read from the provider. Depending on provisioning availability, Tessl may then start a first scan of the repositories in scope. Scan provisioning is best-effort and separate from creating the connection, so a successful connection does not guarantee that a scan has started or finished. The connection page shows scan status. An Organization admin can retry a failed scan or set the Scan scope there.
See your Context and Findings
Once a scan has run:
Open Context in the sidebar to see the skills and configuration Tessl found across your connected repositories, including which repository each item lives in.
Open Findings to see the issues Tessl surfaced, ranked by severity.
Home gives you an overview across your Organization.
To control which repositories Tessl scans, open the connection under Settings, then Integrations, and set the Scan scope. For GitHub-specific setup, see Connect Tessl to GitHub.
Last updated