GigakubeWikigigakube.ch →Menu ↓

Projects and people

What projects are for, which roles exist, and how to invite someone to work with you.

What a project is

A project is the container for everything you use in the cloud: servers, private network, public addresses, Kubernetes clusters, DNS zones. Two projects cannot see each other: they have separate networks and separate quotas.

Use them to keep apart what should be kept apart: one customer from another, production from testing, one product from another. You can have up to 25 projects.

Every account has a default project (marked default): it is the one used when you do not choose one, and it cannot be deleted.

Your account (credit, usage, invoices) stays yours and there is only one: usage from all your projects goes to the same account. People you invite to a project work inside it, but they cannot see your account or your other projects.

Managing projects

From the Projects menu:

On the Cloud page, when you have more than one project, there is a menu at the top to choose which one you are working on. The panel remembers the last one you chose.

Roles

Every person (and every API key) has one of these roles in a project. In the panel they have plain names:

In the panel In the API What it can do
Can view viewer Sees everything in the project (servers, firewall, addresses, usage, DNS, change requests) and changes nothing
Can edit operator In addition creates, changes, stops and deletes servers, clusters, networks and DNS records; opens ports 80 and 443 to everyone and other ports to specific sources; approves or rejects change requests
Can manage admin In addition switches on the cloud, opens server consoles, downloads cluster kubeconfigs, opens ports other than 80 and 443 to the whole internet, connects Cloudflare accounts, moves DNS zones between projects, invites people with the Can view or Can edit role
owner owner Whoever created the project: everything, and in addition renames or deletes the project and appoints other Can manage people

Inviting someone

From Projects, open the project's people (People):

  1. type the email address (Email address);
  2. choose the role;
  3. press Invite.

The person receives an email. If they already have an account with that address, they will find the project among theirs the next time they log in. If they do not, the invitation stays pending (no account with this address yet) until they sign up with that same address.

Rules:

Who did what

Every project has an activity log, which all its members can see: in Projects, under the project's people, in Recent activity. For each entry: when, who, from where (the panel, an API key, an agent via MCP, the assistant) and with what outcome. It records changes, console openings, kubeconfig reads, decisions on change requests, and keys created and revoked.

For developers

Method With an API key What it does
Tenants/getList yes (sees only the key's project) The projects, with your role
Tenants/getActivity yes (limit up to 500, default 50) The project's log
Tenants/create, update, delete no Panel only
Tenants/getMembers, inviteMember, updateMemberRole, removeMember, leave no Panel only

In the cloud methods the project is given with tenant (the project's uuid); without it, the default project is used. With an API key the project is always and only the key's own: see API keys.