Projects, environments and access

Admin 2 · 3:40

An admin sets up a second team's project on the hub, with a production environment after devtest. A developer and a pipeline then get access through a grant and their own API keys.

Download the mp4Recorded on 2026.2

What it covers

The project finance with weikio project create, and a production environment after devtest in promotion order
The four seeded roles, listed with weikio get roles
A user for Anna, with a one-time link to set a password
A deployer grant in finance, shown on the Project access page
Anna's own API key from weikio login
A pipeline's user with deployer in devtest, and its key from weikio apikey create

Commands in this video

Terminal

$ weikio project create finance
$ weikio env create production --display-name Production --order 2 --production --entity-store-bytes 2GiB
$ weikio get roles
$ weikio user create anna@example.com --display-name "Anna"
$ weikio member add finance anna@example.com --role deployer --env devtest,production
$ weikio user create ci@example.com --display-name "CI"
$ weikio member add finance ci@example.com --role deployer --env devtest
$ weikio apikey create --name ci --user ci@example.com --grant finance/deployer@devtest

Transcript

0:02An admin sets up a second team's space on the hub, with the access it needs.
0:10The installation made this hub, the platform's central server.
0:15It also made the project sandbox and the environment devtest.
0:19The agent dev runs integrations at this site. It is online.
0:23The platform admin is signed in with the client. The context holds both.
0:32Sandbox is the first project.
0:34Finance is the second project, made by hand.
0:37weikio project create finance makes it.
0:41The output names the server, and the next line says the project is created.
0:46The project name is fixed once it is made.
0:53The production flag sets it at creation. The setting cannot change later.
0:58It takes order 2, so it sits after devtest in the promotion order.
1:03The environment gets two gigabytes of room for its entity store.
1:11The page for Environments lists them in promotion order.
1:14The shield marks production, and the Allows column shows what is on.
1:23weikio get roles lists the roles the installation seeds.
1:28A role is a set of verbs,
1:30and the four seeded roles are viewer, editor, deployer and admin.
1:40A user is a record for one person, made with an address and a display name.
1:45The command prints a one-time set-password link, valid for three days.
1:50The admin sends the link to Anna, and Anna chooses her own password.
1:59A grant gives a role in one project for named environments.
2:04The command grants deployer in finance to Anna for devtest and production.
2:12The Project access page in Settings shows the row with the role and the environments.
2:22Anna signs in as the developer with weikio login.
2:26The browser opens an approval page, and it shows the machine name and the rights.
2:31The approval mints her own API key, named after the machine, valid for 90 days.
2:42A pipeline needs its own API key, with its own user and its grant.
2:48The pipeline's user is made first and given deployer in devtest the way Anna was,
2:54because a key's grant cannot go beyond what its user holds.
2:58weikio apikey create names the key, the user and the grant,
3:05and prints the value once.
3:08The API keys page lists the key with its user, its grant and its expiry.
3:19The installation made the project sandbox and the environment devtest,
3:24and an admin made finance and production.
3:27A grant gives a user a role in finance,
3:29and a developer and a pipeline get an API key.

Next in this track

Admin 3 · 3:49 Sites and agents