Organizations¶

An organization is the top-level unit of multi-tenancy in Cloud Digit. Everything else — users, projects, resources, billing — lives inside an organization. One Cloud Digit account can belong to multiple orgs (typical for MSPs, partners, and Cloud Digit staff); most customers have one.

Concept¶

graph TB
    Org[Organization<br/>'test']
    Org --> P1[Project<br/>'arctic']
    Org --> P2[Project<br/>'polar']
    Org --> P3[Project<br/>'tundra']
    P1 --> R1[Servers · Volumes · Networking · K8s · ...]
    P2 --> R2[Servers · Volumes · ...]
    P3 --> R3[...]
    Org -.-> B[Billing identity<br/>BDT invoices]
    Org -.-> U[Org users<br/>roles per org]

Organization landing page¶

When you sign in (and you belong to one or more orgs), you arrive at the organization landing page at /. It shows one card per organization.

The organization landing page. Each card represents one org; project tiles within.

Each card surfaces:

• Org name (top-left, bold)
• Your role badge — OWNER, ADMIN, MEMBER, or READ-ONLY (small orange tag next to the name)
• Project tiles in the card body — one per project
• Settings cog (top-right of the card) — opens org-level settings (admins only)

Switching organizations¶

If you belong to more than one org:

Switching orgs is instant — no re-auth required. You stay signed in as the same identity; only the active org context changes.

Organization settings (Admins / Owners only)¶

Open from the settings cog on the org card (landing page) or directly at /organizations/<org-id>/settings.

Organization settings — the admin's main control surface.

The settings page is grouped into:

General¶

• Organization name — display name; doesn't affect IDs or billing
• Organization ID — opaque ULID, read-only (this is what API calls reference)
• Created at — registration timestamp
• Default region — applied to new projects unless overridden (bd-dha-1 / bd-ctg-1 / bd-syl-1)
• Time zone — display preference for invoices and logs (default Asia/Dhaka)

Billing identity¶

This is the entity that owns the BDT-denominated invoices for this org:

• Legal name (as registered with RJSC)
• Trade Licence number
• TIN certificate number
• BIN / VAT registration number
• RJSC certificate of incorporation reference
• Registered address
• AIT-deduction-at-source contact email
• Billing contact (separate from technical admin)

See Account & onboarding for the documents required at registration. Changes to billing identity require uploading updated supporting documents and a short KYC re-verification (typically ≤ 2 business days).

Members & roles¶

Covered in detail on the Users and Roles & permissions pages.

Compliance & sovereignty¶

• Sovereignty tier — display of your contractual sovereignty class (see Compliance & sovereignty)
• Audit log retention — configurable from 18 months (default) up to 84 months
• Audit log export — push destinations (Cloud Digit Object Storage bucket / external SIEM via webhook)
• Right-to-audit window — annual schedule, with audit-pack generation button

Integrations (coming next)¶

SSO / SAML / OIDC federation with your enterprise IdP. See SSO.

Notifications¶

Default email recipients for billing, security, and operational events. Per-user preferences override these — full coverage in the upcoming Operational basics → Notifications section.

Danger zone¶

• Suspend organization — temporarily disables resource creation and access (existing resources keep running, invoices keep coming). Reversible.
• Close organization — schedules deletion. All projects, resources, and snapshots are wiped after a 30-day grace window. Billing records are retained 7 years per NBR. Irreversible after the 30-day window.

Creating a new organization¶

From the User menu (top-right) → Create → Organization (or use the + Create button on the org-picker page).

sequenceDiagram
    participant You
    participant Console
    participant KYC
    participant Cloud
    You->>Console: Click + Create → Organization
    Console->>You: Org details form (name, country, billing entity)
    You->>Console: Submit + upload documents
    Console->>KYC: Open KYC case
    KYC->>You: KYC outcome (≤ 2 BWD for SME, ≤ 10 BWD for Enterprise)
    KYC->>Cloud: Provision org tenant
    Cloud->>You: Welcome email, org ID, first-login URL

You become the Owner of the org you created. Owners can invite others and reassign Owner role if needed (a Cloud Digit account must always have at least one Owner).

Multi-organization users¶

Some accounts belong to multiple orgs. For those:

• Each org's role is independent — you might be Owner of one and Read-only of another
• MFA, password, and SSO settings live with your identity, not the org
• Per-org defaults (preferred region, time zone) don't carry over when you switch orgs
• Billing is always per-org — you can't pay one org's invoice from another's balance

Related¶

• Users
• Projects
• Roles & permissions
• Account & onboarding
• Compliance & sovereignty