| SharePoint lists | The lists you name, such as a risk register, incident log or exception register. Nothing else on the site. | Read-only, through an app registration you create in your own Microsoft tenant. We recommend Sites.Selected, which limits it to the sites you grant. | Every hour, or less often if you choose |
| Jira issues | The issues a JQL query you write selects, such as your incidents in Jira Service Management or a risk or exception register kept as issues, and only the fields you tell Frank to read. Nothing else on the site. | Read-only, through an API token scoped to reading Jira work, issued to a service account you create in your own Atlassian organisation and let see only the projects your query reads. Frank sends the token to Atlassian and nowhere else. | Every hour, or less often if you choose. Add a webhook in Jira and a change prompts an earlier read, unless Jira has asked Frank to wait or reads have been failing. The hourly read still runs. |
| SharePoint or OneDrive library | One library: your Statement of Applicability, the file that tells Frank how to read it, and the register files that file names. | Read-only, through the same kind of app registration as SharePoint lists. One registration can serve both. | Every hour, or less often if you choose |
| GitHub repository | One repository: your Statement of Applicability, the file that tells Frank how to read it, and the register files that file names. | Read-only, through a fine-grained access token you create, limited to that one repository and its contents. | Every hour, or less often if you choose. Add a webhook in GitHub and a push prompts an earlier read, unless GitHub has asked Frank to wait or reads have been failing. The hourly read still runs. |
| GitHub security alerts | The repositories you name, which need not hold your statement: the Dependabot, code scanning and secret scanning alerts GitHub holds open on them, and whether each default branch requires an approved pull request, each only where you name the controls it bears on. Where GitHub produces none of a kind for a repository, or its plan cannot enforce branch rules, Frank shows it as a gap for you to decide on. | Read-only, through a separate fine-grained access token you create, limited to those repositories and to the permission for each kind it reads: Dependabot alerts, Code scanning alerts, Secret scanning alerts, and Administration for branch rules, which also lets the token read the repository’s settings. A committed secret is recorded by its type, never its value. | Every hour, or less often if you choose |