Manual / Infrastructure / GitHub / Create the Cloudberrie GitHub Organization
Cloudberrie Business & Operations Manual

Create the Cloudberrie GitHub Organization

Create the business namespace and configure identity, membership, policies, and ownership.

Document: INF-102Type: Guide / SOPStatus: ApprovedOwner: Engineering OperationsVersion: 4.2.0Updated: 2026-07-17
Cloudberrie GitHub configuration
The legal owner is Cloudberrie Studio India LLP; the organization contact is accounts@cloudberrie.com.

Create the Organization

  1. Sign in with the secured administrative GitHub account.
  2. Open the profile menu → Your organizations.
  3. Select New organization.
  4. Choose the Free plan initially unless a paid feature has already been approved.
  5. Enter the approved organization name, preferably cloudberrie-studio.
  6. Set the contact email to accounts@cloudberrie.com.
  7. Confirm the organization belongs to a business or institution when prompted.
  8. Complete creation and open organization settings.

Organization Profile

  • Upload the approved Cloudberrie mark.
  • Name: Cloudberrie Studio.
  • Description: concise description of the company’s technology and creative work.
  • Website: https://cloudberrie.com.
  • Location: use the approved business location format.
  • Email: use a public or operational business alias, not a private address.

Critical Settings

SettingCloudberrie standard
Organization ownersKeep to the minimum required; maintain at least two authorized recovery-capable owners when the team permits
Base repository permissionNone for maximum least privilege, or Read only if specifically approved
Repository creationRestrict to owners initially; later delegate under policy
Repository visibility changesOwners only
Outside collaboratorsOwner approval required
2FA requirementRequire for members and outside collaborators after confirming all current users are enrolled

Require 2FA Safely

  1. Notify all current organization users before enforcement.
  2. Confirm each person has enabled 2FA.
  3. Open Organization → Settings → authentication/security settings.
  4. Enable the requirement for two-factor authentication.
  5. Review any users GitHub identifies as non-compliant before confirming.
Risk: enforcing 2FA can remove non-compliant members or collaborators from access. Confirm compliance before switching it on.

Optional Domain Verification

When Cloudberrie wants GitHub to show verified organizational ownership of cloudberrie.com, use GitHub’s organization domain verification workflow and add the exact TXT record GitHub supplies. Preserve all existing Google Workspace and service verification records.