Syensqo IS - Customer Support

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

How to request Github / Copilot access



  • User creation request for GitHub & GitHub Copilot


    Request format

    User email list

    Organization you have access approval  (approval email from existing organization owner)

    New organization request with justification

    License required (Github or Github copilot)



Organization Creation & Naming Conventions

We avoid "Org Sprawl." New Organizations are only created for distinct Business Units or large-scale Projects.


  • Naming Convention (Org): SQO-<business-unit> (e.g., SQO-INFRASTRUCTURE,  SQO-INTEGRATION , SQO-SYENSQOAI).



  • Naming Convention (Repo):  Syensqo-[platform]-[app name/project name]   
     

    • platform:   (Azure), (GCP), (AWS), (Multi-cloud), (on-prem).

    • Example: Syensqo-Azure-infra-Subscription-Mgmt



Team & Permission Management



  • Team Structure: Always nest teams under the Parent Org.


  • Permissions:


    • Maintainer: For dev/ops lead (manage settings, no billing)

    • Write: For Developers (standard CI/CD access).

    • Triage/Read: For Stakeholders and Auditors.

    Info

    Rule: Never grant individual permissions







The best way to get IT support is to use the new Service One Platform.