Projects and environments

Concept 1 · 3:07

A project keeps one team's integrations and people apart from another team's, and all projects share the same environments. Grants give people roles, and an API key never carries more than those grants.

Download the mp4Recorded on 2026.2

What it covers

One installation drawn as a picture, with the project sandbox and the environment devtest
A second team's project, finance, kept apart from sandbox
Environments in promotion order, and the rules that set production apart
The four project roles and what each one may do
A deployer grant for named environments, and the API key on Anna's machine
A pipeline's API key, which its grant limits to devtest

Commands in this video

This video explains with drawings and types no commands.

Transcript

0:02This video draws your Weik.io installation as one picture.
0:10The drawing starts with the installation someone tries Weik.io on.
0:15Its first setup made the project sandbox.
0:18The integrations of a project run in an environment.
0:22The grey band is the environment devtest, for developing and testing.
0:31A project holds one team's integrations, with the people who may work on them.
0:35The second team works in the project finance.
0:38Project boundaries come from the platform, so no team reaches another team's work.
0:44The platform administrator creates the projects and environments once.
0:53Both projects use the same environments, in a fixed promotion order.
0:57The tiles number the environments: devtest first, production second.
1:02A write into production must name the environment.
1:06Production runs a version you name in full, never the latest.
1:10Nothing turns an environment into production once it is created.
1:19Four roles reach a project: viewer, editor, deployer and admin.
1:25A viewer reads.
1:26An editor goes further, editing integrations, variables and secrets,
1:32and starting or stopping what runs.
1:34A deployer adds delivery: putting versions in, promoting them, rolling them back.
1:41An admin adds the people side, the member list.
1:48A grant gives one person a role in one project, for the environments it lists.
1:54Anna holds the deployer grant in finance, covering devtest and production.
1:59In sandbox that grant gives her nothing.
2:06Anna signs in from her machine with the Weik.io CLI,
2:10then the CLI ends up with an API key named after that machine.
2:15That key expires eventually.
2:17It carries nothing past the grants Anna already has.
2:23A pipeline gets an API key made for it, covering one environment only.
2:29This key carries the deployer role on finance, in devtest only.
2:34Because that grant names devtest, the key has no way into production.
2:38No edit to the pipeline's workflow file changes that.
2:46A project keeps a team's integrations and the people who work on them.
2:50The environments stay shared, in one promotion order.
2:54Roles reach people and pipelines through grants.
2:57No key carries more than its grants.

Next in this track

Concept 2 · 3:42 What runs where