What will you learn in this guide?
- ✓ How to invite teammates to the project and manage invitations.
- ✓ Drawing permission boundaries using Role Based Access Control (RBAC).
- ✓ Best practices for secure collaboration.
- ✓ Revoking invites and tracking team activities (Audit Log).
With Skyversal Team Management, you can invite developers, clients, or agency workers to your projects and define detailed access permissions for each user. Thanks to the Role Based Access Control (RBAC) architecture, everyone can only perform operations within their authorization.
📩 1. Inviting a Teammate
Adding a new member to your project takes seconds. The invited user will receive a unique confirmation link via email, which is valid for 7 days. The invited user can be a member of multiple Skyversal projects simultaneously. Their role is managed independently for each project.
If the invited person does not have a Skyversal account, clicking the link will first redirect them to a quick registration page, after which they automatically join the project.
Invitations in "Pending" status can be revoked at any time or resent when they expire (after 7 days).
🛡️ 2. Permission Matrix (Role Based Access Control)
Managing project permissions is facilitated by 4 different roles on our platform.
| Permission | Viewer | Developer | Manager | Owner |
|---|---|---|---|---|
| View (Logs, Metrics, Settings) | ✅ | ✅ | ✅ | ✅ |
| Deploy, Re-deploy & Web IDE | ❌ | ✅ | ✅ | ✅ |
| Environment Variables (.env) * | ❌ | ✅ | ✅ | ✅ |
| Infrastructure (Domains, Storage, Backup) | ❌ | ❌ | ✅ | ✅ |
| Team Management & Billing | ❌ | ❌ | ❌ | ✅ |
| Delete & Transfer Project | ❌ | ❌ | ❌ | ✅ |
*.env Security Warning: Environment Variables may contain API keys, database passwords, and other sensitive information. Therefore, it is recommended to give the Developer or Manager role only to developers who need it. Assign only the Viewer role to clients or 3rd party stakeholders to ensure your secrets (API Keys) stay safe.
Principle of Least Privilege
It is recommended to grant team members only the minimum permissions they need. Providing Viewer role to clients and Developer role to active engineers is always the most secure enterprise standard.
- Viewer → Client, Product Manager, QA
- Developer → Software Engineers
- Manager → Lead Developer, DevOps, CTO
- Owner → Company owner or project founder
🔄 3. Member Management
Can I change roles later?
Yes. You don't need to completely remove a team member from the project. You can update the user's role anytime from the Team tab.
What happens if I remove them?
The user's access to the project is revoked instantly. Running applications are unaffected, and the deploy logs made by that person are preserved.
Transfer Ownership
The project Owner possesses all management rights. They can permanently transfer the project to another Skyversal user on their team.
📊 4. Activity Log (Audit Trail)
You can track which team member made changes via the logs in real-time. You can access the entire history through the Activity tab on the project details page. This greatly accelerates retroactive debugging processes, especially in large teams.
🤝 Get Started Now
With Skyversal's Team Management infrastructure, securely manage your team members, keep access permissions under control, and track all project activities from a single dashboard.
The same user can participate in dozens of different Skyversal projects with different roles. For example, they can be assigned as a Manager in one project and only as a Viewer in another.