Skip to main content

​
Sign in

Open the Admin console in your browser and the sign-in screen appears.

Open the CodePilot Admin console

https://codepilot.banya.ai
Organizations running on-premises use their own internally deployed address rather than the one above. Ask your organization administrator if you don’t know it.
Admin sign-in What the sign-in screen looks like depends on the environment your organization uses.
EnvironmentSign-in method
Cloud (SaaS)Sign in with a Google, GitHub, or Microsoft account
On-premisesSign in with email and password
Use the Korean / English button in the top right to switch the console language.

​
Register an organization

If your signed-in account does not belong to an organization, the organization setup screen appears. You have two options. Organization setup options

​
Create a new organization

Choose this if you are the administrator creating the organization for the first time. When you create it, you automatically receive administrator privileges. Create organization
FieldDescription
Organization name (Required)Your company or team name
Department (Optional)Department name
Depending on the environment configuration, an organization may enter an Approval pending state after it is created. In that case, a waiting screen is shown until approval is complete.

​
Join an organization with an API key

Choose this to join an organization that already exists. Enter the API key starting with cpk_ that you received from your administrator. Join organization

​
Approval status

After you request to join an organization, a waiting screen is shown while you await administrator approval. Approval pending
StatusScreen
Approval pendingUnder administrator review. Refresh with the Check approval status button
RejectedReview the reason, then you can Apply again
Insufficient permissionsYou belong to the organization but lack administrator privileges. Ask an existing administrator to upgrade your role
Only admins and owners can access the Admin console. If a regular member signs in, an insufficient-permissions notice is shown. Members use the product by joining with the organization API key from the IDE rather than the console.

​
Distributing API keys to members

To join an organization from the IDE, members need an organization API key. Administrators issue these keys and distribute them. API Keys
1

Go to the API Keys menu

Navigate to Management → API Keys in the sidebar.
2

Create a key

Click Create key and enter a key name. Issuing separate keys per team or purpose makes them easier to manage.
e.g., Dev team key, QA team key
3

Copy the key

The full key is shown only once, right after creation. Copy it now.
4

Share it with members

Members join by entering this key under IDE Settings → Account → Organization connection.
The full key is shown only once, right after creation. After that, only a partially masked form is visible. If you lose a key, issue a new one.
If you deactivate a key, it can no longer be used to join the organization. Members who have already joined are not affected.

​
Managing members

Manage organization members under Management → Team in the sidebar. Team management
ActionDescription
Change roleSwitch between Admin and Member
Set token limitSet a per-member usage cap
Reset passwordIssue a temporary password (on-premises)
Remove memberRemove them from the organization
Transfer ownershipHand owner privileges to another admin
When you transfer ownership, your own role changes to Admin. An owner must transfer ownership before leaving the organization.

​
My Profile

Click your profile at the bottom of the sidebar to view your account details and change the console language and password. My Profile

​
Next steps

Project management

Create projects and separate their settings

Configure policies

Register AI models, security, and coding rules