Skip to content
Weik.ioUniversity
Try Weik.io

Projects and environments

Concept 1 · 2:57

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
  1. 0:02This video draws one picture of a Weik.io installation, with no commands typed.
  2. 0:12The picture shows the installation you try Weik.io on.
  3. 0:16It made one project, sandbox, the chip drawn on the hub.
  4. 0:20A project's integrations run in an environment.
  5. 0:24The environment is the grey band, devtest.
  6. 0:31A project groups one team's integrations and the people allowed to touch them.
  7. 0:36A second team works in its own project, finance.
  8. 0:40The platform keeps one team out of another team's projects.
  9. 0:44The platform administrator creates projects and environments once.
  10. 0:52Both projects use the same environments, in a promotion order.
  11. 0:56Tile one marks devtest.
  12. 0:59The amber band is production, and it takes order two.
  13. 1:02A write into production must name the environment.
  14. 1:06Production runs only a pinned version, never the latest.
  15. 1:10Production is set at creation and never changes.
  16. 1:18Access to a project comes through four roles: viewer, editor, deployer and admin.
  17. 1:25A viewer reads.
  18. 1:26An editor also changes integrations, variables and secrets,
  19. 1:30and starts and stops them.
  20. 1:32A deployer also deploys, promotes and rolls back.
  21. 1:37An admin also manages the project's members.
  22. 1:44A grant gives a person a role in one project, for named environments.
  23. 1:48Anna holds a deployer grant in finance, for devtest and production.
  24. 1:53Her grant gives her nothing in sandbox.
  25. 1:59Anna signs in, and the Weik.io CLI on her machine gets its own API key.
  26. 2:05The key is named after the machine and expires after 90 days.
  27. 2:10The key never holds more than Anna's grants.
  28. 2:14A pipeline gets an API key of its own, for one environment.
  29. 2:18The tag shows the grant: finance/deployer@devtest, the deployer role in finance.
  30. 2:26The grant names devtest only,
  31. 2:29so the key cannot touch production even if the workflow file is edited.
  32. 2:37A project groups one team's integrations and people,
  33. 2:41and environments follow a promotion order.
  34. 2:44Roles reach people through grants,
  35. 2:46and every API key carries no more than those grants.

Next in this track

Concept 2 · 3:41 What runs where Watched