# Infomaniak — account, profile & organization setup

> **Goal:** get a Magogi Foundation Infomaniak account ready to the point where you
> can activate **Public Cloud** ([next guide](02-activate-public-cloud.md)).
> **Audience:** a federation operator/admin doing this once. **Time:** ~15 min
> (plus any billing/ID review Infomaniak runs).

## What Infomaniak is (and why the federation uses it)

[Infomaniak](https://www.infomaniak.com) is an independent **Swiss** cloud + hosting
provider. The federation uses it because:

- Its **Public Cloud** is **standard OpenStack** (Nova/Cinder/Swift/Neutron), so we
  manage it with the normal OpenStack ecosystem — no proprietary lock-in. This is
  what [`mgf-cloud`](https://codeberg.org/magogi-admin/mgf-cloud) drives.
- **Swiss jurisdiction + data residency** (datacenters in Geneva, etc.).
- One account also covers adjacent products we use — **Swiss Backup** (S3/Swift
  offsite backup), mail, domains/DNS, kSuite collaboration.

Everything is managed from the **Manager** at <https://manager.infomaniak.com>.

## Step 1 — Create the account

1. Go to <https://manager.infomaniak.com> and **create an account** (or sign in if
   the foundation already has one — for Magogi it is the **"Magogi Community"**
   organization).
2. Use a role/shared address you control (e.g. an `infra@`-style alias), not a
   personal mailbox — this account owns billing and infrastructure.

## Step 2 — Turn on 2FA (required)

Under your **user profile → security**, enable **two-factor authentication**.
Per the foundation's security policy a **hardware security key** is preferred for
the account owner; set a **recovery contact** as well. The account guards billing
and cloud resources — treat it as Cat-A infrastructure.

## Step 3 — The Organization, users & profiles

Infomaniak groups everything under an **Organization** (the "Magogi Community"
workspace — the `MC` badge top-left of the Manager).

- **Users and profiles** (left sidebar) — invite team members, set their **roles**
  (who can see/manage which products). Keep the set small; grant the least role
  that works.
- **Settings** — organization-level details (name, address, contacts).
- Your **own profile** (top-right avatar) — language, 2FA, API tokens for the
  *general* account API (note: Public Cloud does **not** use these — it uses
  OpenStack credentials, covered in guide 02).

## Step 4 — Billing (needed before Public Cloud)

Under **Accounting** (left sidebar):

- **Payment methods** — add a card / payment source.
- **Billing parameters** — billing address, VAT/company details.

Public Cloud is **pay-as-you-go**; you can't order it without a payment method on
file. (Creating the *project* is free — you pay only for resources you provision.)

## Step 5 — Orient yourself in the Manager

The Manager home groups products into columns:

- **Collaborative tools** — kSuite, Mail, kDrive, kChat.
- **Web & Domains** — websites, hosting, domains, SSL.
- **Cloud Computing** — **Public Cloud**, Kubernetes, Databases, VPS, **Swiss
  Backup**, Jelastic, etc.

The federation's VMs + storage live under **Cloud Computing → Public Cloud** —
that's where the [next guide](02-activate-public-cloud.md) begins.

## Governance notes (Magogi)

- **2FA mandatory** for everyone with access; hardware key for the owner.
- A **recovery contact** is set and kept current.
- **Two-person approval** for production-impacting cloud actions (provisioning or
  deleting a prod VM, releasing a prod floating IP) — see the VM ops playbook.
- The account owner + billing live in the foundation's records, not a personal
  account.

## Next

→ **[02 — Activate Public Cloud + get your OpenStack credential](02-activate-public-cloud.md)**
