Support
Access guide
Follow these steps to request ML System Card access or troubleshoot sign-in issues. The details below match the requirements used by this deployment of the control plane.
Request checklist
Make sure you can confirm each item before submitting an access request.
- Your GitHub account uses two-factor authentication and belongs to the correct GitHub organization.
- You have or can create a fine-grained personal access token with
repoandworkflowscopes. - The repository you want to manage already includes
docs/ml_system_card.yaml. - You know which stakeholder personas should be seeded for the repo (or explicitly state that defaults are fine).
How to request access
1. Gather the required details
Collect your GitHub username, target repository (owner/name), and the stakeholder profiles you would like to load by default.
2. Submit a request
Post a short message in your project support channel or email the automation team at maintainers@example.com. Include the details from step 1.
3. Wait for confirmation
You will receive a confirmation once your GitHub account has been granted access. The note will include instructions for creating or updating your personal access token.
Troubleshooting tips
- "Access denied" during sign in.Confirm your GitHub token includes the scopes listed above and hasn't expired. You can create a new token, then update the saved secret in the control plane.
- You only see public repositories. Ensure the GitHub app has been installed for the organization and granted access to the repository. Reconnect the app if necessary.
- Stakeholder profiles are missing. Verify that
/docs/stakeholdersexists in the repo, or request the maintainers to generate default personas for you.
Still need help?
Drop a note in your project support channel with a screenshot of the error, or email the team at maintainers@example.com. We usually respond within one business day.