Authentication

GitHub authorization connects your repository to your Neuroline organization. You do not need an auth.yaml file or an API key in the repository. This connection is separate from API authentication.

Permissions

You must be an owner or admin of the Neuroline organization and have write or admin access to the GitHub repository. The Neuroline GitHub App must be installed with access to that repository. The app reads repository contents; it does not need permission to write files.

An organization can connect one repository. The same repository can connect to multiple Neuroline organizations. Each organization has its own assistants, integration credentials, phone assignments, and sync status. Pushes to the default branch update every connected organization.

Connect a repository

1. Open Organization → Infrastructure-as-code and select Connect GitHub.
2. Authorize GitHub. This works regardless of how you signed into Neuroline.
3. Install the Neuroline GitHub App if needed. For GitHub organizations, an administrator may need to approve installation or repository access.
4. Choose an account and repository, then select Connect & sync.

The picker shows active repositories accessible to both you and the app, where you have write or admin permissions. Manage GitHub access lets you install the app or add repositories. Refresh the list after access is approved. If your organization uses SAML SSO, start an SSO session on GitHub before authorizing.

Neuroline checks your permissions again when you connect. An installation ID in a redirect URL or a repository name alone cannot establish the connection. The GitHub authorization session expires after 30 minutes; reconnect GitHub if you need more time to choose a repository.

After connection

Neuroline remembers the repository's numeric GitHub identity. Background syncs use the app installation, independently of your temporary selection session. Pushes to the default branch update your assistants. An empty repository can be connected before adding your first assistant.

Previously verified connections continue to work. Existing auth.yaml files are ignored and can be removed. A connection that was never verified must be completed using Connect GitHub.

Integration credentials stay in the dashboard. Connect services such as Cal.com or Google Calendar on the assistant's integrations page; see Integration functions.

Resolve connection problems

Use Disconnect and delete assistants to stop GitHub management and permanently delete the repository's assistants in the current organization. Linked phone numbers are unassigned. Other organizations using the repository are unaffected. Further pushes cannot reconnect the disconnected organization. Reconnecting requires an explicit selection by an authorized user and creates new assistants; see Disconnecting.