This is your private success portal. Share it only with your team.

Powered by Okay, Now What?
Copilot assistant
Answers for your team, from official GitHub docs

Hi! Ask me anything about Copilot.

Answers are written for your team and link to the official GitHub docs they come from.

Written by Claude, an AI model. Double-check anything important in the linked docs.

Copperleaf LendingxCopilot

Customer success portal

Ask your account team for help
Your GitHub account team sees this right away.
What do you need?

Dan Okafor

VP Engineering

DO
  • Home
  • Plan
  • Learn
  • Prompts
  • Guides
  • Videos
  • Setup guide
  • Champion kit
  • Progress
  • Value

Setup guide

The admin and security steps that matter for Copperleaf Lending, built around the questions your team raised.

For admins

Seats, policies, and settings.

Set Copilot policies and the public code filter

Why this matters for you: Clear, documented settings are the base of the audit story.

  1. Review each Copilot policy in your organization settings and decide on/off
  2. Set suggestions matching public code to Blocked
  3. Record each decision for the CISO

Read the docs

  • Managing policies and features for GitHub Copilot in your organizationdocs.github.com
  • Managing policies and features for GitHub Copilot in your enterprisedocs.github.com

Manage seats for 550 developers

Why this matters for you: Every developer needs a seat to hit Dan's weekly-use goal.

  1. Assign seats by team so you can track adoption team by team
  2. Add new hires to Copilot as part of their first-day setup
  3. Review inactive seats monthly before the CFO review

Read the docs

  • GitHub Copilot seat assignmentdocs.github.com
  • Reminding inactive users to use their GitHub Copilot licensedocs.github.com

For security

Exclusions, data handling, and audit.

Exclude loan decisioning and credit model code

Why this matters for you: The CISO asked for these repositories to be kept out of Copilot.

  1. List the loan decisioning repo and every repo that touches credit models with the CISO's team
  2. Add them as content exclusions in your organization's Copilot settings
  3. Test it: open an excluded file in VS Code and JetBrains and confirm there are no suggestions

Read the docs

  • Excluding content from GitHub Copilotdocs.github.com
  • Content exclusion for GitHub Copilotdocs.github.com

For team leads

Rollout, metrics, and enablement.

Standard setup for VS Code and JetBrains

Why this matters for you: Most teams use VS Code, and some use JetBrains. One guide each keeps DevEx out of support tickets.

  1. Share the VS Code install guide with every team
  2. Share the JetBrains guide with the teams that use it
  3. Add both to the new hire onboarding checklist

Read the docs

  • Installing the GitHub Copilot extension in your environmentdocs.github.com
  • Quickstart for using GitHub Copilot in your IDEdocs.github.com

Build the audit story for regulators

Why this matters for you: State and CFPB exams came up. The CISO needs to show how AI use is governed.

  1. Write down your Copilot policies and who approved them
  2. Use the enterprise audit log to track changes to Copilot settings, policies, and licenses, plus agent activity on GitHub
  3. Keep a record of content exclusions and when they changed
  4. Export usage metrics monthly as evidence of controlled rollout

Read the docs

  • Reviewing audit logs for GitHub Copilotdocs.github.com
  • Resources for getting approval of GitHub Copilotdocs.github.com

Turn on usage metrics

Why this matters for you: Weekly active use is Dan's goal and the CFO's evidence.

  1. Enable Copilot usage metrics for the organization
  2. Review weekly active users by team every Monday
  3. Flag teams under 50% weekly active to DevEx for a follow-up session

Read the docs

  • Viewing the Copilot usage metrics dashboarddocs.github.com
  • Driving GitHub Copilot adoption in your companydocs.github.com