Connections and integrations
Find GitHub connections, workspace single sign-on, and AI provider settings in Sorena AI.
Sorena AI has separate settings for GitHub evidence, team sign-in, and AI processing. Start with the connection you want to manage, then check the selected workspace and your role.
| Connection or setting | What it does | Where to open it | Who can change it | Required workspace licenses |
|---|---|---|---|---|
| GitHub | Connects a GitHub organization and captures the information available to the installed GitHub App. | Workspace > Integrations | Workspace Admin or Owner; GitHub may also require an organization owner to approve installation or access changes. | Platform |
| Single sign-on (SSO) | Lets invited members sign in through the organization's identity provider using SAML or OpenID Connect. | Workspace > Authentication | Workspace Admin or Owner can configure providers; removing a provider requires Owner. | Platform and Enterprise SSO |
| OpenAI service settings | Sets the processing tier and data residency preference for eligible OpenAI requests, including requests using Sorena-managed credentials. | Workspace > Integrations | Workspace Admin or Owner; other workspace members can read the saved settings. | Platform |
| Workspace AI provider credentials | Lets a workspace supply its own OpenAI or Cloudflare credentials and choose whether Sorena-managed credentials may be used as fallback. | Workspace > Integrations | Workspace Admin or Owner; other workspace members can read the available provider status. | Platform and Enterprise BYOAI |
Your role in a project does not give you permission to manage workspace connections. See roles, access, and licenses if a setting or action is missing.
Connect GitHub for evidence
Follow Connect GitHub to install the app, choose repository access, and connect the organization to the intended workspace. Then review the capture time and evidence status before using a result. Sorena shows captured evidence; changes to GitHub-owned settings take place on GitHub.
Use GitHub permissions for access changes and sync operations for refresh and recovery steps.
Set up team sign-in
Follow Workspace sign-in and SSO with the person who manages your identity provider. That guide covers provider configuration, domain policies, directory synchronization options, and magic-link availability.
An SSO connection verifies identity. Members still need the appropriate workspace, project, team, or resource access to do their work. Invite people through workspace membership, and review member lifecycle when someone leaves.
Choose AI processing and credentials
Follow AI service and provider settings to choose a service tier, review eligible residency regions, or configure workspace credentials. Service preferences and provider credentials have different license requirements, as shown above.
To describe your own role, preferred answers, or working context, update your profile. Profile instructions are separate from workspace-wide provider settings.
Check a change
After saving, review the connection's status in its own settings page. For GitHub, also check the capture time; a queued refresh has not finished yet. For SSO, verify a working sign-in path before restricting another method. For AI providers, check whether the card says it is using workspace configuration or system defaults.
Use workspace activity to review the connection and configuration changes available to you. If a connection cannot load or recover, contact support with the affected setting and time. Keep credentials and sign-in setup values out of screenshots and messages.