Platform
Permissions
ForkDeploy is small enough that the permission model is simple: you own your projects, and platform admins can help you when something goes wrong. Here's exactly what that means.
The roles
User
The default role. You own the projects you create, and only you (or an admin) can see or change them. There is no team or collaborator layer yet, so projects belong to one account.
Admin
Can see every project on the platform to manage capacity, debug issues, and help with support. Admin access is for running the platform, not for browsing your work out of curiosity, and every admin action is tied to their account.
Founder
Has every admin power. It's the role the platform itself runs on, not a separate tier you'd encounter.
What admins can and can't see
An admin can list, inspect, and manage every project's services on the platform, so capacity issues and support requests can be handled without waiting on you. That access is not unlimited:
- ✓ Secret values stay masked to any admin who isn't the project owner. Admins see that a secret exists, never the plain value.
- ✓ Environment variables and secrets are only ever decrypted server-side, at the moment they are injected into your running services.
- ✓ Deleting or modifying your project as an admin is the same action you could take yourself, logged the same way.
For how secret values are stored and encrypted in the first place, see Secrets & env vars.