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.

Rep preview: this visit isn't counted as a customer visit.

Harborline PaymentsxCopilot

Customer success portal

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

Priya Nair

Director of Platform Engineering

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

Setup guide

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

For admins

Seats, policies, and settings.

Block suggestions that match public code

Why this matters for you: Legal will ask about IP. This setting reduces the chance of suggestions that match public code.

  1. In your Copilot policies, set suggestions matching public code to Blocked
  2. Add the setting to the summary you send AppSec and legal

Read the docs

  • Managing policies and features for GitHub Copilot in your enterprisedocs.github.com
  • Finding public code that matches GitHub Copilot suggestionsdocs.github.com

Assign seats to the four pilot teams

Why this matters for you: Keeps the pilot to 100 seats across checkout, risk, mobile, and internal tools.

  1. Create a team for each pilot group
  2. Assign Copilot seats to those teams only
  3. Send each team lead the install guide

Read the docs

  • GitHub Copilot seat assignmentdocs.github.com
  • Setting up GitHub Copilot for your organizationdocs.github.com

Set AI credit budgets

Why this matters for you: Keeps pilot spend predictable while teams try agent mode and code review.

  1. Check AI credit usage in your billing settings
  2. Decide whether to allow additional usage beyond the included credits (it's on by default)
  3. Set a monthly budget for the pilot
  4. Review it again after the agent mode workshop

Read the docs

  • Usage-based billing for organizations and enterprisesdocs.github.com
  • Budgets for usage-based billingdocs.github.com

For security

Exclusions, data handling, and audit.

Exclude PCI-scoped repositories

Why this matters for you: AppSec asked to keep PCI-scoped code out of Copilot.

  1. List the repositories and paths that are in PCI scope with AppSec
  2. Add them as content exclusions in your organization's Copilot settings
  3. Test it: open an excluded file and confirm Copilot does not offer suggestions there

Read the docs

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

For team leads

Rollout, metrics, and enablement.

Turn on usage metrics for the readout

Why this matters for you: The CTO wants hard numbers. Usage metrics plus PR cycle time make the case.

  1. Enable Copilot usage metrics for the organization
  2. Pull weekly active users every Friday
  3. Track PR cycle time on pilot teams against the baseline from week one

Read the docs

  • GitHub Copilot usage metricsdocs.github.com
  • Measuring the success of a GitHub Copilot trialdocs.github.com

Review data handling and retention with AppSec

Why this matters for you: AppSec needs a clean answer on data retention before they sign off.

  1. Send AppSec GitHub's approval resources page: terms, data protection agreement, and trust center links
  2. Walk through where models are hosted and GitHub's commitment not to train on your data
  3. Send AppSec a one-page summary and ask for written sign-off

Read the docs

  • Resources for getting approval of GitHub Copilotdocs.github.com
  • Hosting of models for GitHub Copilotdocs.github.com