Console Guide¶
The Cloud Digit Console is the web-based portal you use to manage organizations, projects, and the resources inside them. This guide is the click-by-click companion to the service and reference docs.
Who this is for¶
Customer admin staff — people responsible for their organization's Cloud Digit account: inviting users, creating projects, assigning roles, watching spend, attending audits. If you're a developer just deploying workloads, you'll want it open while you work, but the API & CLI reference is probably your closer companion.
What's covered¶
-
Sign in, console layout, browser support, sessions.
-
Organizations, users, projects, roles, API tokens, SSO.
-
Servers, Volumes, Images, Networking, Kubernetes, Object Storage, Orchestration, Key Manager, Access.
-
Financial portal, spend alerts, tagging, audit logs, notifications.
-
Login & MFA, browser & cache, performance & latency.
How each component page is structured¶
Every per-component page follows the same template, so you can scan them quickly:
- Overview — what the component is, who uses it
- Administration — admin-only tasks (create, configure, delete, policies)
- Operation — day-to-day workflows for builders and operators
- Troubleshooting — symptom → likely cause → fix
Screenshots sit inline at every multi-step flow.
What this guide is not¶
- Not a service reference — those live under Compute, Storage, Networking, etc.
- Not internal platform-operator docs — Cloud Digit ops engineering has its own runbook set.
- Not end-user marketing material — for that, see the main site.
Section 1: Console basics¶
-
Email, SSO (Google / GitHub / Microsoft), MFA, registration.
-
Top bar, organization landing, project sidebar, user menu, theme toggle, help bubble.
-
Browsers, sessions & SPA quirks
Supported browsers, hard-reload fix, session expiration, signing out, multi-org switching.
Section 2: Identity & access¶
-
The top-level tenant. Settings, billing identity, switching between orgs.
-
Invite, suspend, remove. Per-user profile, MFA, sessions.
-
Create, configure, archive, delete. Tagging conventions and quota.
-
Built-in org and project roles + custom roles + the full permission matrix.
-
Issuing, scoping, rotation, revocation. Personal tokens vs service accounts.
-
Federate with Azure AD, Okta, Google Workspace, Keycloak. Group → role mapping, SCIM, JIT provisioning.
Section 3: Per-component guides¶
Each page follows the same template: Overview → Administration → Operation → Troubleshooting.
-
Virtual Machines: list, create, resize, snapshot, console access, placement groups, troubleshooting.
-
Block storage: NVMe HCI vs Provisioned IOPS, attach/detach, hot-grow, snapshot, multi-attach.
-
Stock images, custom images, snapshots, sharing across projects, Packer integration.
-
VPCs, subnets, routers, security groups, floating IPs, load balancers, VPN gateways.
-
Managed K8s clusters, node pools, kubeconfig, upgrades, autoscaling.
-
S3-compatible buckets, lifecycle rules, cross-region replication, Object Lock, ACL.
-
Heat stacks, autoscaling groups, software configs.
-
Secrets, certificates, KMS keys, SSH keys.
-
Project-scoped members, roles, tokens, activity feed.
Section 4: Operational basics¶
-
Invoices, BDT balance, top-ups (MFS / bank / cheque), payment methods, AIT certificates, Mushak documents.
-
Tag-grouped drill-down, time-range comparison, anomaly detection, scheduled reports, CSV/JSON exports.
-
What's logged, retention tiers, tamper resistance, push to SIEM / external sinks, audit-pack generation.
-
Email · Webhook · Slack / Teams · PagerDuty / Opsgenie · ServiceNow · routing matrix · quiet hours · per-user preferences.
Section 5: Cross-cutting troubleshooting¶
The deeper-dive companions to the per-section troubleshooting tables — decision trees, diagnostic flows, when-to-escalate guidance.
-
Invalid-password decision tree, account lockouts, MFA code rejection, lost-device recovery, SSO redirect loops.
-
Hard-reload technique, extension interference, CORS / CSP errors in DevTools, clearing local state, cookie / SameSite issues.
-
Latency budgets per network hop, slow-API triage, S3 upload tuning, K8s networking quirks, "fast in BD slow elsewhere".