Projects, environments and access

Admin 2 · 3:59

An admin sets up a second team's project in Weik.io, 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 project, a production environment,
0:06and access for a person and a pipeline.
0:12Your Weik.io installation keeps the records.
0:16The installation created its first project, sandbox.
0:20The environment devtest is first in the order, and not a production environment.
0:24Integrations run on agent dev, online at the site,
0:28and the platform admin is signed in with the Weik.io CLI.
0:36Sandbox holds one team's work. The second team gets a project.
0:41weikio project create finance makes the second project.
0:45The CLI reports the project created. Finance holds the second team's work.
0:53weikio env create production adds the environment, with flags for the display name,
0:59the production flag, and entity store size.
1:03The production flag is set at creation and can never change.
1:07The new environment takes the second slot, behind devtest.
1:15The Environments page under Settings numbers them in promotion order.
1:20The shield marks production,
1:22and the allows column names what each environment allows.
1:30weikio get roles shows the seeded roles.
1:35A role gathers verbs under a name.
1:37Each adds to the last: viewer reads,
1:41editor writes and operates, deployer deploys, admin manages members.
1:50weikio user create makes Anna a user, from her mail address and a display name.
1:56She appears in the people column.
1:59The command prints a single-use set-password link, valid three days,
2:04for you to pass to Anna, who sets her password.
2:11weikio member add finance gives her deployer in devtest and production.
2:17A grant ties that role to one project and to the environments it names.
2:25The Project access page under Settings gives one row per grant,
2:30with the person, role and environments.
2:35Anna signs the CLI in with weikio login, opening this approval page.
2:41The rights card names the grants the key would hold.
2:44Approving mints an API key named for her machine, and nobody mints one by hand.
2:51It works until the expiry the page shows.
2:56A pipeline has no browser, so it needs an API key.
3:01The key belongs to its user, and holds only its grant.
3:05First weikio user create makes that user.
3:08weikio member add gives that user deployer in finance, for devtest only.
3:15weikio apikey create names the key, its owner and its grant.
3:21A key never holds more than its owner was given.
3:24The value prints once, so store it where the pipeline can read it.
3:29The API keys page carries each key, its owner, access and expiry.
3:39Sandbox came with the installation, and production came after devtest.
3:44A grant gave Anna deployer in finance,
3:47and a developer and a pipeline each hold a key made for them.

Next in this track

Admin 3 · 4:25 Sites and agents