One project, several people. Each with their role.
Invite teammates or clients, give each the role they need, and work on the same canvas at the same time.
At a glance
- Roles
- Owner, admin, developer, viewer
- Canvas
- Shared live
- API keys
- wgk_ prefix, scopes, expiry
- Billing
- On the owner's account
Working together, each in their place.
01
Four roles.
Owner, admin, developer or viewer: from the owner who can do everything to read-only access to logs and metrics.
Changing a role is immediate, and removing a member cuts their access on the spot. Everyone only sees their own GitHub repositories.
02
The same canvas, live.
Open the project together: everyone's cursors, the deployments started and the state of services show up for everyone.
Nothing to turn on. A viewer sees everything happen, but cannot trigger anything.
03
Narrow API keys.
One key per use, with its scopes (services:write, projects:read…), a rate limit and an expiry date.
The full key is shown only once, when it is created. On a project, it never has more rights than you.
04
Your account under control.
Sign in with a password, GitHub or Discord, and see the list of active sessions with their device and IP address.
An unknown device is signed out at once. Your data export is on the same page.
What it does not do yet.
The owner role cannot be transferred from the Members tab.
A shared project's resources count against the owner's account, or the project's dedicated plan.
Live presence uses WebSockets: an extension that blocks them hides the cursors.
Questions about teamwork
The rest of the platform
Invite your team.
One project, roles, and the same canvas for everyone.