Projects and access
Weik.io 2026.2A project groups related integrations and APIs with their values. A grant gives a person a role in it, down to single environments or to single integrations and APIs. Product page · Video
Watch: Projects, environments and access, 3:59
The video creates a project and an environment and grants a person access to them.
This part of the video couldn't be loaded.
On this page
Group related integrations and APIs into a project, such as finance or hr, and give the people who work on them access to that project. Every project deploys into the same environments, such as devtest and production, which are defined once for the whole installation.
Each member has a role in the project. You can narrow their grant to some environments and to single integrations or APIs. See How memberships work.
Create a project#
A platform administrator creates projects:
$ weikio project create finance --display-name "Finance" --label team=financeTarget: https://hub.example
project finance created (revision 4102)weikio describe project finance shows the project in full, including its ID and its members.
Creating a project also creates a store for the built versions of its integrations, which is 1 GiB unless you give another size with --store-bytes. An agent can read code and jars only from the stores of the projects it serves.
Create the environments#
A platform administrator creates the environments once for the whole installation, usually as kind: environment documents in Git:
$ weikio apply -f platform/environments.yamlTarget: https://hub.example
environment devtest created
environment production created$ weikio get environmentsNAME ORDER PRODUCTION EVENTS BUDGET ENTITY EVENTS ENTITY STORE GATEWAYS AGENTS
devtest 1 no 2 GiB 1 GiB 512 MiB devtest (default) 2/2 online
production 2 yes 8 GiB 4 GiB 2 GiB internal (default), partner 1/2 onlineA command that changes something in an environment marked as production needs --env. You can also turn off revealing secrets in such an environment. Environments and promotion shows how a version moves from one environment to the next.
Give a person access#
To give a person a role in a project, run weikio member add with their e-mail address:
$ weikio member add finance anna@example.com --role deployer --env devtest,productionTarget: https://hub.example, project finance (argument), user anna@example.com
member finance/anna@example.com created (role deployer; environments devtest, production; revision 4104)A grant can be as narrow as one integration. With this one, a helpdesk person sees only erp-invoice-export and nightly-payroll in production:
$ weikio member add finance ville@example.com --role helpdesk --env production --integrations erp-invoice-export,nightly-payrollTarget: https://hub.example, project finance (argument), user ville@example.com
member finance/ville@example.com created (role helpdesk; environments production; integrations erp-invoice-export, nightly-payroll; revision 4105)Without --env, a new member’s grant covers every environment. Without --integrations and --apis, it covers the whole project. Limiting a membership describes what a limited grant covers.
On an existing member, member add replaces the role and changes only the limits you give, and it prints a line for each limit it kept. To remove a limit, give it '*', as in --env '*' for every environment or --integrations '*' --apis '*' for the whole project.
weikio get members finance lists the members. weikio member remove finance ville@example.com removes a person from the project from their next request on.
A person who signs in with no grant sees a No access yet page until you add them to a project.
In the admin UI#
Give access with Grant project access in Settings › Access › Project access, or with Grant access on a user’s row in Settings › Users, where you can filter for the users with no membership.
To change the access of someone who is already a member, use Edit access.




weikio member add line.The Platform admins tab in Settings › Users lists the users set as platform administrators on their account. It leaves out the platform administrators a claim mapping makes. They keep the platform administrator setting for 30 days after their last sign-in through the provider, unless you change the number of days with weikio provider set --roles-count-for.
In Git#
Roles and members are documents too, so you review a change of access in a pull request like any other change:
apiVersion: weik.io/v1
kind: role
metadata: { name: helpdesk }
spec: { verbs: [read] }
---
apiVersion: weik.io/v1
kind: member
metadata: { name: ville@example.com, project: finance }
spec:
role: helpdesk
environments: [production]
integrations: [erp-invoice-export, nightly-payroll]$ weikio apply -f platform/access/finance-helpdesk.yamlRoles and grants lists the roles that come with Weik.io and the verbs you build a custom role from.
Rename or delete a project#
Renaming a project with weikio rename project finance finance-ops keeps its ID and everything in it. Deleting a project deletes everything in it in every environment, after you type the project’s name to confirm.