Skip to content

Organization, sign-in and roles ​

Everything in Yi Code belongs to an organization: sessions, credit, projects, roles, knowledge, memory and GitHub connections. Your organization and your role come from the identity provider you sign in with, never from anything the browser sends.

Sign in ​

Sign in with your identity provider over OpenID Connect.

  • Cloud service (https://code.theyilabs.com): click "Sign in with your organization" and use your Yi Labs account, then choose your organization. The current hosted workspace and credit belong to that organization. See Budget and billing before funding an account.
  • Private deployment: click "Sign in with your organization" and use your company's own identity provider ("Private deployments use your internal identity provider.").

On the cloud service, an organization has to be set up for Yi Code before its members can sign in. Otherwise they see "This organization is unavailable. Please contact your administrator." Request access to get your organization set up.

How long you stay signed in ​

  • A sign-in lasts at most 8 hours. Using the app doesn't extend it.
  • Every 60 seconds by default, Yi Code asks the identity provider again whether you're still a member and what your role is. Someone removed from the organization is signed out at the next check. A changed role applies at the next check.
  • If that check can't be made, access stops until it can. You see "Organization permissions could not be checked. Please try signing in again later."
  • The browser holds only a random session handle. Your identity and the provider's token stay on the server, the token encrypted.

Sign out and switch ​

The account menu at the bottom of the sidebar shows your name, organization and role.

  • "Sign out of Preworld Code" ends your Yi Code session only. Your Yi Labs sign-in stays active. Some screens use the earlier name "Preworld Code" for the same product.
  • "Switch organization" takes you back through sign-in to choose another organization you belong to.

Members and roles ​

Members and their roles come from your organization account at the identity provider. Yi Code keeps no member list of its own, so add and remove people and change roles there.

There are three roles: owner, administrator and member. A role the identity provider doesn't send, or one Yi Code doesn't know, counts as member. Owners and administrators have the same permissions in Yi Code.

Owner, administratorMember
Start sessions in Ask and Code, follow up, cancel, archive and restore their own sessionsYesYes
Connect GitHub, and connect their own GitHub account for publishingYesYes
Publish a draft pull request from their own session on a GitHub App repository, with write access on GitHubYesYes
See the wallet and the account ledgerYesYes
Read every session in the organization (not continue or publish them)YesNo
Add projects by repository URL, and publish from their own sessions on themYesNo
Publish new role versionsYesNo
Add knowledge sources and upload documentsYesNo
Add MCP tool connectionsYesNo
Record, publish and delete project memoryYesNo
See execution poolsYesNo

On the cloud service, model endpoints, execution pools and rates are managed by Yi Labs. In a private deployment, the deployment's administrators manage them.

Changes that matter are written to the organization's audit log: starting and continuing sessions, archiving, publishing pull requests, connecting GitHub, and changes to settings, knowledge and memory.

A suspended organization ​

If an organization is suspended, the app says "This organization is suspended. History and task cancellation remain available." Members can read their sessions and cancel running turns. Nothing new can start.

Language ​

The app is in Chinese unless you choose otherwise. The language switch in the app changes it and is remembered in the browser. Without a choice there, the app follows the language of your account if it has one.